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@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