From: Jose Luis Domingo Lopez <jdomingo@internautas.org>
To: Tony Glader <Tony.Glader@blueberrysolutions.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: F00F-bug workaround working?
Date: Sat, 12 Jan 2002 23:11:45 +0100 [thread overview]
Message-ID: <20020112221144.GC1406@localhost> (raw)
In-Reply-To: <Pine.LNX.4.33.0201122347270.16871-100000@blueberrysolutions.com>
In-Reply-To: <Pine.LNX.4.33.0201122347270.16871-100000@blueberrysolutions.com>
On Saturday, 12 January 2002, at 23:49:06 +0200,
Tony Glader wrote:
> I have had problems with 2.4.17 running in a Classic Pentium (lot of
> oopses). I'm sure that there's no problem with hardware. Is F00F'bug
> workaround work still?
>
No problems here with any 2.4.x kernel, both with old and new
workarounds for the mentioned bug.
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 2
model name : Pentium 75 - 200
stepping : 12
cpu MHz : 165.792
fdiv_bug : no
hlt_bug : no
f00f_bug : yes
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8
bogomips : 330.95
Jan 12 12:30:21 dardhal kernel: Intel Pentium with F0 0F bug -
workaround enabled
--
José Luis Domingo López
Linux Registered User #189436 Debian Linux Woody (P166 64 MB RAM)
jdomingo AT internautas DOT org => Spam at your own risk
next prev parent reply other threads:[~2002-01-12 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 21:49 F00F-bug workaround working? Tony Glader
2002-01-12 22:03 ` Joseph Pingenot
2002-01-13 20:20 ` H. Peter Anvin
2002-01-12 22:11 ` Jose Luis Domingo Lopez [this message]
2002-01-13 23:11 ` James Stevenson
2002-01-26 0:55 ` Stevie O
-- strict thread matches above, loose matches on Subject: below --
2002-01-13 9:50 Zwane Mwaikambo
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=20020112221144.GC1406@localhost \
--to=jdomingo@internautas.org \
--cc=Tony.Glader@blueberrysolutions.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.