public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: whither patch that fixed K6 32M bug on 2.1.56?
Date: Fri, 30 May 2003 00:12:26 -0400	[thread overview]
Message-ID: <8765ntyswl.fsf@cs.uga.edu> (raw)

Hi.  I just bought a computer (cheap!) that appears to have a K6
processor with the bug this website is dedicated to:

  http://membres.lycos.fr/poulot/k6bug.html

The problem appears to be a hardware glitch in the K6 where it gets
overly paranoid about self-modifying code.  There is a patch at the
above website that changes the 2.1.56 kernel thusly:

  Description : If page A is a code page, and A+32MB is a data page,
  then the bug can occur. If the memory allocation is modified to
  prevent these collisions, the failure rate should decrease
  dramatically.

Has anyone done anything with this patch since 2.1.56?  I see some
stuff in 2.4.20 that appears to test for the bug and print a warning
that the system may be unstable on detection.

-- 
--Ed L Cashin     PGP public key: http://noserose.net/e/pgp/


                 reply	other threads:[~2003-05-30  3:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8765ntyswl.fsf@cs.uga.edu \
    --to=ecashin@uga.edu \
    --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