Hi!
On Sun, 29 Nov 2009 02:04:12 +, Ben Hutchings b...@decadent.org.uk wrote:
You must either change the detection code to set %0 to 0 if the
condition is not met, or change =r to +r so that %0 will be
initialised to the previous value of has_cpuid (i.e. 0).
Thanks for this hint. It is
On Thu, 2009-03-12 at 11:20 +0100, Werner Koch wrote:
On Thu, 12 Mar 2009 09:32, dex...@debian.org said:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb7b9c6e0 (LWP 2196)]
0xb7bae10e in _gcry_detect_hw_features () at hwfeatures.c:78
That seems to be the
On 2009-05-18 Piotr Roszatycki dex...@debian.org wrote:
2009/5/17 Andreas Metzler ametz...@downhill.at.eu.org:
There is a second, slightly diffeent instance of the same code in
boot/cpucheck.c. Does this one also prodecue the Illegal instruction
error?
cu and- doesn't speak ASM -reas
2009/5/18 Andreas Metzler ametz...@downhill.at.eu.org:
Perhaps you could send me binary to run?
Strange, it builds for me on i486, but fails to build on amd64.
Extrapolationg from that I would assume building in i386 should work.
Ah, thanks. I've forgot this is i386-only code.
I'm afraid
Hi. Sorry for delay.
I can't compile this code:
$ gcc -o cpuid2 cpuid2.c
cpuid2.c: Assembler messages:
cpuid2.c:16: Error: suffix or operands invalid for `pushf'
cpuid2.c:16: Error: suffix or operands invalid for `pushf'
cpuid2.c:16: Error: suffix or operands invalid for `pop'
cpuid2.c:16:
On 2009-05-02 Andreas Metzler ametz...@downhill.at.eu.org wrote:
On 2009-03-12 Piotr Roszatycki dex...@debian.org wrote:
I read the source for kernel 2.6.24 and found that it uses similar
technic for CPUID detection. I've copied to one simple test program
(attached) and I worried why it
On 2009-03-12 Piotr Roszatycki dex...@debian.org wrote:
I read the source for kernel 2.6.24 and found that it uses similar
technic for CPUID detection. I've copied to one simple test program
(attached) and I worried why it doesn't work on Vortex correcty:
$ ./cpuid
This CPU has CPUID opcode
Package: libgcrypt11
Version: 1.4.4-2
Severity: grave
I've found this bug calling lpstat from cupsys:
$ gdb lpstat
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb7b9c6e0 (LWP 2196)]
0xb7bae10e in _gcry_detect_hw_features () at hwfeatures.c:78
78 hwfeatures.c:
On Thu, 12 Mar 2009 09:32, dex...@debian.org said:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb7b9c6e0 (LWP 2196)]
0xb7bae10e in _gcry_detect_hw_features () at hwfeatures.c:78
That seems to be the cpuid opcode which is not available, Linux knows
about it:
I read the source for kernel 2.6.24 and found that it uses similar
technic for CPUID detection. I've copied to one simple test program
(attached) and I worried why it doesn't work on Vortex correcty:
$ ./cpuid
This CPU has CPUID opcode
Illegal instruction
Any ideas? Would anyone be so kind
10 matches
Mail list logo
