public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: F00F-bug workaround working?
Date: 13 Jan 2002 12:20:10 -0800	[thread overview]
Message-ID: <a1sq5q$nb7$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201122347270.16871-100000@blueberrysolutions.com> <20020112160308.B4926@ksu.edu>

Followup to:  <20020112160308.B4926@ksu.edu>
By author:    Joseph Pingenot <jap3003@ksu.edu>
In newsgroup: linux.dev.kernel
>
> From Tony Glader on Saturday, 12 January, 2002:
> >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?
> 
> I'm running a P100 on 2.4.17 without any errors.  I see
> "Intel Pentium with F0 0F bug - workaround enabled."
> in the dmesg logs.
> 
> How about posting your oopses (after running them through ksymoops)
> 

F00F wouldn't oops the machine anyway, it would lock it up solid.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-01-13 20:20 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 [this message]
2002-01-12 22:11 ` Jose Luis Domingo Lopez
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='a1sq5q$nb7$1@cesium.transmeta.com' \
    --to=hpa@zytor.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