From: Mikael Pettersson <mikpe@it.uu.se>
To: 76306.1226@compuserve.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.17-rc3 broke FP exceptions on x86
Date: Sat, 29 Apr 2006 12:03:00 +0200 (MEST) [thread overview]
Message-ID: <200604291003.k3TA30oP025481@harpo.it.uu.se> (raw)
On Sat, 29 Apr 2006 04:00:49 -0400, Chuck Ebbert <76306.1226@compuserve.com> wrote:
>On Fri, 28 Apr 2006 14:54:40 +0200, Mikael Pettersson wrote:
>
>> Running an FP exception using user-space application
>> (the runtime system for the Erlang programming language
>> in my case) on an Athlon64 with a 32-bit 2.6.17-rc3 kernel
>> quickly results in a complete system hang: mouse is dead,
>> keyboard is dead, the network doesn't reply to pings.
>> Had to reboot via the power switch to get the machine back.
>>
>> This happended twice in a row. With 2.6.17-rc2 things
>> work fine like they always have before.
>
>This should fix it... please test.
>
>Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
>
>--- 2.6.17-rc3-d4.orig/include/asm-i386/i387.h
>+++ 2.6.17-rc3-d4/include/asm-i386/i387.h
>@@ -58,13 +58,13 @@ static inline void __save_init_fpu( stru
> alternative_input(
> "fnsave %[fx] ;fwait;" GENERIC_NOP8 GENERIC_NOP4,
> "fxsave %[fx]\n"
>- "bt $7,%[fsw] ; jc 1f ; fnclex\n1:",
>+ "bt $7,%[fsw] ; jnc 1f ; fnclex\n1:",
> X86_FEATURE_FXSR,
> [fx] "m" (tsk->thread.i387.fxsave),
> [fsw] "m" (tsk->thread.i387.fxsave.swd) : "memory");
> /* AMD K7/K8 CPUs don't save/restore FDP/FIP/FOP unless an exception
> is pending. Clear the x87 state here by setting it to fixed
>- values. __per_cpu_offset[0] is a random variable that should be in L1 */
>+ values. safe_address is a random variable that should be in L1 */
> alternative_input(
> GENERIC_NOP8 GENERIC_NOP2,
> "emms\n\t" /* clear stack tags */
This fixed the problem. Thanks.
Acked-by: Mikael Pettersson <mikpe@it.uu.se>
next reply other threads:[~2006-04-29 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 10:03 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-29 8:00 Chuck Ebbert
2006-04-28 12:54 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200604291003.k3TA30oP025481@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®