When the kernel is built with CONFIG_ARCH_OMAP2 it will select
CPU_V6 and other dependencies which causes issues in user space.
For example when clients try to connect to PulseAudio they will
crash with:
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
Remove support for OMAP2 for now.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi(a)ti.com>
---
Hi Andrey,
Can you take a look at this patch?
In the latest hwpack for panda (with 3.9 kernel) PulseAudio clients all asserts
with the following error:
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
The same userspace works fine (well, mostly) with 3.8 based hwpacks.
It turns out that this is cased by the CONFIG_ARCH_OMAP2, if we disable it PA
clients no longer assert.
Since the config in question is for OMAP4, I see no issue removing the OMAP2
support since in this way we can get PA working.
One issue still remain with PA:
None of float resample method works:
speex-float-[0-10]
However speex-fixed-[0-10] and ffmpeg seams to be working, but it is not perfect.
I'll try to figure out why we have this failure since on my Gentoo FS all resample
method works fine with the same kernel.
Regards,
Peter
linaro/configs/omap4.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/linaro/configs/omap4.conf b/linaro/configs/omap4.conf
index 59e9f23..82c9365 100644
--- a/linaro/configs/omap4.conf
+++ b/linaro/configs/omap4.conf
@@ -11,6 +11,7 @@ CONFIG_OMAP_RESET_CLOCKS=y
CONFIG_OMAP_MUX_DEBUG=y
CONFIG_ARCH_OMAP2PLUS=y
CONFIG_SOC_OMAP5=y
+CONFIG_ARCH_OMAP2=n
CONFIG_ARCH_VEXPRESS_CA9X4=y
CONFIG_ARM_THUMBEE=y
CONFIG_ARM_ERRATA_411920=y
--
1.7.10.4
Linaro Virtualization Team's Weekly Report - Weeks 13/14 2013
=============================================================
During the last 2 weeks (27 March - 10 April 2013) the team has been
working on the following areas. More detailed information can be found
on the meeting reports wiki page [0].
Ongoing work
------------
* BOOTLOADER HYP MODE SUPPORT FOR ARMv7 [1]
by Andre Przywara
* rebase existing Versatile Express patches against upstream u-boot [2]
Done:
- Reworked patch for Versatile Express to be more reusable
for other boards.
- U-Boot patch sent as RFC, waiting for reaction.
* implement HYP command to let u-boot switch into HYP mode [3]
Done:
- HYP mode switch works reliably.
- SMP is working too.
- VExpress patches sent upstream (V3 of the patch set).
- discovered a bug in Linux 3.9-rc:
- DMA refactoring broke Versatile Express: NULL pointer
exception.
- Patches already are on ML, but not yet in HEAD
(3.9rc5-77)
- discovered related issue with DMA PL330 on Highbank
(Rob@Calxeda seems to care about this)
* ARMv7 KVM GUEST MIGRATION [4]
by Peter Maydell and Andre Przywara
* QEMU: audit the vexpress model for devices we use which do not
currently have migration support [5]
by Peter Maydell
Done:
- task completed.
- patches now preliminarily queued in arm-devs.next, though
if there is a late-breaking issue with one of them it will
have to be fixed and patches updated.
* QEMU: implement full cp15 sync with kernel [6]
by Peter Maydell
Done:
- Some work that was assumed to be already committed last
year appeared to be still pending - hew sub-task created:
QEMU: move CPU migration to vmstate [7]
Working on:
- pending for [7] to complete.
* QEMU: move CPU migration to vmstate [7]
Done:
- updated patches from Juan Quintela from last year which
are updating the migration state for the CPU itself to use
VMState structures.
Working on:
- testing and tweaking of the updated patches.
* kernel: agree on a data structure to describe timer state [8]
by Andre Przywara
Working on:
- reading documentation.
- thinking about code structure.
- timer migration prototype.
* ARMv8 KVM QEMU prototype [9]
* Add skeleton ARM64 build patches to local tree [10]
Done:
- completed this sub-task.
* Add arm64 mach-virt system model skeleton [11]
Working on:
- only has serial, can add virtio stuff later.
- in progress.
* Add creating FDT from scratch to mach-virt system model [12]
Working on:
- in progress, nearly done.
* Add kvm guest creation and launching of armv8/mach-virt [13]
Working on:
- in progress, just started.
* IN KERNEL SUPPORT FOR KVM ARMv8 [14]
by Anup Patel and Pranavkumar Sawargaonkar, Geoff Levand
Done:
- KVM ARMv8 patch set review, fixes suggested (by Geoff).
- Initial patch set for APM board bring up is reviewed
internally in APM and is queued for upstreaming in near
future.
- real AMRv8 hardware is accessible to Anup and Pranav -
switched to it for further work.
- ARMv8 kernel is bootable on the board now.
- U-Boot is starting the kernel in HYP mode on the board now.
Working on:
- Debugging the guest part now (on the board). Currently it is
not booting (still in early debug).
- Hacky early printk support in kvmtool is to be properly
submitted to the ML as an RFC.
* CI BRING UP: KVM ARMv7 [15]
by Riku Voipio
Done:
- Find out howto include guest image in host image.
- Create ci.linaro.org jobs for submitting validation tests to
LAVA for VE TC2.
Working on:
- Create ci.linaro.org jobs for submitting validation tests to
LAVA for Arndale.
Links
-----
[0] https://wiki.linaro.org/LEG/Engineering/Virtualization/TeamMeetingReports
[1] http://cards.linaro.org/browse/CARD-361
[2] http://cards.linaro.org/browse/VIRT-70
[3] http://cards.linaro.org/browse/VIRT-71
[4] http://cards.linaro.org/browse/CARD-363
[5] http://cards.linaro.org/browse/VIRT-51
[6] http://cards.linaro.org/browse/VIRT-49
[7] http://cards.linaro.org/browse/VIRT-73
[8] http://cards.linaro.org/browse/VIRT-42
[9] http://cards.linaro.org/browse/CARD-221
[10] http://cards.linaro.org/browse/VIRT-52
[11] http://cards.linaro.org/browse/VIRT-53
[12] http://cards.linaro.org/browse/VIRT-54
[13] http://cards.linaro.org/browse/VIRT-56
[14] http://cards.linaro.org/browse/CARD-362
[15] http://cards.linaro.org/browse/CARD-233
--
Best Regards,
Serge Broslavsky <serge.broslavsky(a)linaro.org>
Project Manager, Linaro
M: +37129426328 IRC: ototo Skype: serge.broslavsky
http://linaro.org | Open source software for ARM SoCs
Calendar Week 15, 2013: Here is test result summary for Linux Linaro ubuntu
Quantal image on following boards:
1) ARM Versatile Express A9;
2) Samsung Arndale;
3) TI Panda 4430;
4) TI Panda 4460;
5) ST Ericsson Snowball.
Synopsis: Gator version mismatch happens on all images; HDMI on Samsung
Arndale board works well.
1. ARM Versatile Express A9 + Linux Linaro Quantal (Column Q):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
Gator version mismatch happens again. Except "Halt" and "Device Tree", all
other features work well.
2. Samsung Arndale + Linux Linaro Quantal (Column K):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJS…
HDMI works well without manually configuration on boot argument; DS-5 data
streaming failed due to Gator version mismatch; kernel panic is occurred
during power management test. All other features work well.
3. TI Panda 4430 + Linux Linaro Quantal (Column Q):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Status is remained as same as last week except Gator version issue. WiFi
and display output are unavailable, several test cases failed in power
management, all other features work well.
4. TI Panda 4460 + Linux Linaro Quantal (Column Q):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Kernel panic happens during power management test, WiFi & Display are
unavailable. DS-5 test failed due to Gator version issue, all other
features work well.
5. ST Ericsson Snowball + Linux Linaro Quantal (Column R):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFJ4X…
HDMI display and Reboot are unavailable; "thermal_03.1" test failed in
power management; some I/O errors got observed in SD MMC test and Gator
version mismatch issue occurred. All other features work well.
For the previous week test summary (Calendar Week 14), please refer to
attachment.
Thank you.
Best Regards
Botao Sun
Hi All,
Greetings from Linaro QA services.
We have setup the process of validating Linux on ARM Kernel builds.
One of those ARM targets is Snowball. Snowball build broken log can be
found here
Build Error:
--------------
04:48:08 CC drivers/mfd/ab8500-debugfs.o
04:48:09 /mnt/ci_build/workspace/linux-next/hwpack/snowball/label/precise_hwpack_cloud/drivers/mfd/ab8500-debugfs.c:95:23:
fatal error: mach/irqs.h: No such file or directory
04:48:09 compilation terminated.
04:48:09 make[3]: *** [drivers/mfd/ab8500-debugfs.o] Error 1
04:48:09 make[2]: *** [drivers/mfd] Error 2
04:48:09 make[1]: *** [drivers] Error 2
Code snippet:
------------------
File: drivers/mfd/ab8500-debugfs.c
89 #ifdef CONFIG_DEBUG_FS
90 #include <linux/string.h>
91 #include <linux/ctype.h>
92 #endif
93
94 /* TODO: this file should not reference IRQ_DB8500_AB8500! */
95 #include <mach/irqs.h>
96
97 static u32 debug_bank;
98 static u32 debug_address;
99
Kernel Commit id:
----------------------
484eecb3dc4d7173015feeb41e2995bbcb724523
Please let me know if you need more info.
Best regards
Naresh Kamboju
---------- Forwarded message ----------
From: Zongwei Zhou
Date: 11 April 2013 04:47
Subject: Ubuntu (USE_INITRD) on FastModels VE Cortex A15 RTSM
Dear Linaro maintainers,
My name is Zongwei Zhou. I am a Ph.D. student at Carnegie Mellon.
These days I came across one problem when booting Linaro Ubuntu on
FastModels VE Cortex A15 RTSM. I would greatly appreciate it if you
could offer some guidelines and suggestions. Thanks very much!
By following the guidelines in
https://releases.linaro.org/13.02/ubuntu/vexpress "RTSM" tab, I have
successfully booted Ubuntu. However, the booting process is quite slow
in FastModels simulator. When looking at the booting log, I found out
that it stuck quite a long time in loading file system from RTSM MMC.
Thus I am looking for using initrd to speed up the booting process.
I downloaded the linaro boot-wrapper source code and found out that it
supports USE_INITRD configuration. USE_INITRD allows me to combine the
boot-wrapper, kernel image and filesystem.cpio.gz into a
linux-system.axf. I did that, but it seems that the boot-wrapper runs
correctly, but linux kernel later stuck in an infinite loop at address
0xC0253970, and even the FastModels terminal is not invoked. The
kernel image I am using is the uImage from
hwpack_linaro-vexpress_20130224-256_armhf_supported.tar.gz. The way I
created the filesystem.cpio.gz is I decompressed the
linaro-quantal-nano-20130224-286.tar.gz tar ball, and repacked it as
compressed cpio archive using "find . | cpio --quiet -H newc -o | gzip
-9 -n > filesystem.cpio.gz".
Could you please kindly give me some hints about booting Ubuntu with
initrd? Or are there other alternatives that could speed up the
booting process? I am trying the NFS boot now.
Thanks very much for your patience about this long email. Looking
forward to hearing back from you.
Best wishes,
Zongwei Zhou
--
Zongwei (Stephen) Zhou (周宗伟 in Chinese)
Electrical and Computer Engineering Department,
Carnegie Mellon University, Pittsburgh, PA 15213
Email: zongweiz(a)andrew.cmu.edu
Postmortem and lessons learned for Linaro's release 2013.03
https://wiki.linaro.org/Cycles/1303/Release/Review
Highlights and Key Successes
============================
http://www.linaro.org/downloads/1303http://wiki.linaro.org/Cycles/1303/Release#Release_Information
Blueprints
=========
The number of high or essential priority blueprints that missed the cycle:
Android 4 out of 12
Developer Platform 4 out of 5
Infrastructure 1 out of 5
Lava 4 out of 7
Total 13 out of 29
45% of high or essential priority blueprints scheduled for this cycle
were not delivered.
Total blueprints: 22 out of 45 missed the cycle.
* Not included is data from the QA team
High priority missed blueprints recap:
12.05: 19 out of 48, 39%
12.06: 13 out of 31, 42%
12.07: 14 out of 31, 45%
12.08: 6 out of 26, 23%
12.09: 9 out of 28, 32%
12.10: 15 out of 38, 39%
12.11: 7 out of 19, 37%
12.12: not available
13.01: 9 out of 28, 33%
13.02: 35 out of 69, 48%
* Not included is data from working groups and landing teams
Source:
https://docs.google.com/spreadsheet/ccc?key=0AjEaTwrvj1bidExFWUpKTm1iOURjdk…
--
David Zinman, Project Manager
Linaro.org | Open source software for ARM SoCs
I tried using the method of find the kernel source suggested to me on a somewhat similar question.
I want to do two things
(1) find the source to "3.9.0-1-linaro-arndale #1ubuntu1~ci+130404024430 SMP PREEMPT"
(2) figure out how to build the kernel so that is labeled "3.9.0-1-linaro-arndale #1ubuntu1~ci+130404024430 SMP PREEMPT" and not "3.x.x-x-generic" which is what it usually says when I compile a kernel source.
Can someone point me in the direction of these answers?
Thanks
Chad