Control: retitle -1 please add CPU detection at runtime
Control: severity wishilist
On Tue, Aug 09, 2011 at 12:57:06AM +0200, Robert Waldner wrote:
>Package: cpuburn
>Version: 1.4a-1
>Severity: normal
>
>
>Aloha,
>
>I have here a "QNAP TS-410", which boasts an ARM CPU:
>~# cat /proc/cpuinfo
>Processor : Feroceon 88FR131 rev 1 (v5l)
>BogoMIPS : 799.53
>Features : swp half thumb fastmult edsp
>CPU implementer : 0x56
>CPU architecture: 5TE
>CPU variant : 0x2
>CPU part : 0x131
>CPU revision : 1
>Hardware : QNAP TS-41x
>
>~# /usr/bin/burnCortexA8
>Segmentation fault
>
>Through strace:
>
>root@haviland:~# strace -v -F -f -s 20000 /usr/bin/burnCortexA9
>execve("/usr/bin/burnCortexA9", ["/usr/bin/burnCortexA9"], ["SHELL=/bin/bash",
>"TERM=Eterm", "USER=root", "MAIL=/var/mail/root",
>"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
>"PWD=/root", "LANG=en_US.UTF-8", "SHLVL=1", "HOME=/root", "LANGUAGE=en_US:en",
>"LOGNAME=root", "_=/usr/bin/strace"]) = 0
>--- SIGSEGV (Segmentation fault) @ 0 (0) ---
>+++ killed by SIGSEGV +++
>Segmentation fault
>
>IMHO it should not be installable, or throw a dire warning through debconf,
>on systems it can't run on.
That's difficult to know reliably at the packaging level,
unfortunately. You might have installed armel on a Panda board or
similar, and then things would work just fine.
In your case, you have a Feroceon CPU, which is a Marvell ARMv5 (ish)
core. burnCortexA9 is written in ASM to target the ARM Cortex-A9 CPU,
which is ARMv7. It's the equivalent of trying to run hand-optimised
Intel SSE code on an old 486.
A better thing to do would be to add CPU detection directly to the
burnCortexA9 code and have it abort if it detects a CPU that's too
old.
--
Steve McIntyre, Cambridge, UK. st...@einval.com
Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
