From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: Victor Zandy <zandy@cs.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: Global FPU corruption in 2.2
Date: Tue, 24 Apr 2001 18:47:21 +0200 [thread overview]
Message-ID: <20010424164721.3598.qmail@theseus.mathematik.uni-ulm.de> (raw)
In-Reply-To: <cpxu23etpmc.fsf@goat.cs.wisc.edu>
In-Reply-To: <cpxu23etpmc.fsf@goat.cs.wisc.edu>; from zandy@cs.wisc.edu on Tue, Apr 24, 2001 at 08:05:15AM -0500
On Tue, Apr 24, 2001 at 08:05:15AM -0500, Victor Zandy wrote:
>
> He found that PF_USEDFPU was always set before the machine was broken.
> After he found that it was set about 70% of the time.
If I'm not mistaken this actully can cause GLOBAL FPU corruption.
Here's why:
Assyme for a moment that we lose either the PF_USEDFPU flag of one
process. This not only means that the current process won't have its
state saved, it also means that the next process won't have the TS bit
set. This in turn means that this new process won't get PF_USEDFPU set
and suddenly we have a second process with a corrupted FPU state.
Victor: Could you try to reproduce the system wide corruption if you
add an explicit call to stts(); at the very end of __switch_to?
This should prevent the FPU corruption from spreading.
NOTE: This is just to prove my theory, it is not and isn't meant
to be a fix for the actual problem.
regards Christian Ehrhardt
--
THAT'S ALL FOLKS!
next prev parent reply other threads:[~2001-04-24 16:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 13:05 BUG: Global FPU corruption in 2.2 Victor Zandy
2001-04-24 16:24 ` Linus Torvalds
2001-04-24 16:47 ` Christian Ehrhardt [this message]
2001-04-24 18:09 ` Victor Zandy
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 18:21 Victor Zandy
2001-04-24 18:37 ` Alan Cox
2001-04-24 19:17 ` Victor Zandy
2001-04-24 19:51 ` Alan Cox
2001-04-24 8:56 alad
2001-04-24 7:56 alad
2001-04-24 5:33 alad
2001-04-19 16:05 Victor Zandy
2001-04-19 20:18 ` Michal Jaegermann
2001-04-20 18:50 ` Victor Zandy
2001-04-20 19:07 ` Richard B. Johnson
2001-04-20 19:20 ` Victor Zandy
2001-04-20 19:44 ` Richard B. Johnson
2001-04-20 19:23 ` Ulrich Drepper
2001-04-20 19:37 ` Richard B. Johnson
2001-04-20 20:20 ` Victor Zandy
2001-04-20 21:44 ` Ulrich Drepper
2001-04-22 1:46 ` Richard B. Johnson
2001-04-22 2:18 ` Alan Cox
2001-04-22 2:30 ` Richard B. Johnson
2001-04-22 18:39 ` David Konerding
2001-04-22 18:59 ` Alan Cox
2001-04-22 20:59 ` kees
2001-04-23 16:11 ` Christian Ehrhardt
2001-04-24 16:10 ` Linus Torvalds
2001-04-24 16:25 ` Alan Cox
2001-04-24 16:56 ` Christian Ehrhardt
2001-04-24 20:15 ` Michal Jaegermann
2001-04-23 18:44 ` Erik Paulson
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=20010424164721.3598.qmail@theseus.mathematik.uni-ulm.de \
--to=ehrhardt@mathematik.uni-ulm.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zandy@cs.wisc.edu \
/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;
as well as URLs for NNTP newsgroup(s).