** Description changed: Observed for example running ffplay to decode H.264 video on Babbage 2.0 This needs to be worked around by a separate kernel image for the affected platforms, or the ability to enable or disable CONFIG_NEON at boot. Note that the principal problem here is the reporting of neon in the auxv AT_HWCAP word and /proc/cpuinfo which may mislead userspace apps into using NEON. The NEON context-switching code enabled by CONFIG_NEON should not itself cause problems. + + TEST CASE + ======= + + 1) Download the neon-checker.tar.gz attachment + 2) Build this with the following: + $ gcc -g -march=armv7 -mfpu=neon -o neon-check neon-check.s + $ gcc -g -march=armv7 -mfpu=neon -o neon-probe neon-probe.s + 3) Run each of neon-check and neon-probe + $ ./neon-check & + $ ./neon-probe & + + Result if bug is present: + neon-check will exit immediately with SIGILL or print error messages + + Result if bug is addressed: + both programs run without error endlessly + (this can be considered satisfied aftern an hour or so for SRU verification purposes)
-- CONFIG_NEON=y causes platform lockups with certain application/platform combinations https://bugs.launchpad.net/bugs/507416 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
