Public bug reported: NOTE: This issue will apply to all armel kernels except for dove (where the hardware doesn't have NEON support). However, for now imx51 is the only such kernel, so I've raised the bug here.
The issue was discussed on the ARM Linux mailing list; there's a link to the thread and a partial patch here: http://thread.gmane.org/gmane.linux.ports.arm.kernel/58722/focus=58724 State corruption observed in pixman-0.16.x (resulting on various screen rendering artifacts) is believed to be due to this (this is the conclusion Siarhei Siamashka of Nokia — see the above link). Note that the patch is disupted on the list and hasn't been merged: it may cause issues with userspace code which makes assumptions about the layout and contents of the signal frame... though it could be interesting to see whether it has any effect. Note: we may revert to CONFIG_NEON=n by default in the iMX51 kernels due to a separate issue. This may mean that the pixman behaviour appears fixed even if it hasn't been fixed: caution should be applied before assuming that this bug has gone away. (See https://bugs.launchpad.net/bugs/507416 — subscribers only, though) ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Undecided Status: New ** Tags: armel -- VFP/NEON state is not preserved around signal handlers, causing state corruption between user processes https://bugs.launchpad.net/bugs/507503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
