Message-ID: <email address hidden>
Date: Fri, 6 Aug 2004 17:33:56 +0200 (CEST)
From: boud <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: published patch works fine by hand on 2.4.18-14.3
On my kernel compiled from 2.4.18-2.4.18-14.3 source code,
plus the patch:
As an ordinary user, i compiled the proof-of-bug code with gcc 2.95.4
and it did not crash the box, but instead it output a non-stop string
of "." to the screen and used 99% of CPU until i killed it.
Message-ID: <email address hidden>
Date: Fri, 6 Aug 2004 17:33:56 +0200 (CEST)
From: boud <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: published patch works fine by hand on 2.4.18-14.3
On my kernel compiled from 2.4.18-2.4.18-14.3 source code,
plus the patch:
http:// linuxreviews. org/news/ 2004/06/ 11_kernel_ crash/24_ kernel_ ia32-and- x86_64- fix-fpu- state.patch. txt
which is just adding one command in one header file:
include/ asm-i386/ i387.h
- asm volatile("fwait"); \
+ asm volatile("fnclex ; fwait"); \
this compiled and installed OK.
As an ordinary user, i compiled the proof-of-bug code with gcc 2.95.4
and it did not crash the box, but instead it output a non-stop string
of "." to the screen and used 99% of CPU until i killed it.
hope this helps
boud