public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: S W <egberts@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?)
Date: Sat, 16 Mar 2002 20:42:28 +0100	[thread overview]
Message-ID: <20020316204228.B15296@suse.de> (raw)
In-Reply-To: <20020316180705.34916.qmail@web10506.mail.yahoo.com>
In-Reply-To: <20020316180705.34916.qmail@web10506.mail.yahoo.com>

On Sat, Mar 16, 2002 at 10:07:05AM -0800, S W wrote:
 > But I recalled Linux 2.2 having a bug fix for broken
 > L2 cache in Cyrix II.
 
 The cache itself isn't broken. Reporting of the size of it is.
 
 > So, it got me thinking again...
 > (did Cyrix fix this L2 cache in certain subsequential
 > core?)

 The bug is potentially in all cores with cpuid 670->68F
 If you have it, and you're not running a kernel with the
 fix you'll see you have a 16MB cache. If you run a kernel
 with the fix, you'll have the correct size (64KB)
 
 > Does anyone recall where exactly are the Cyrix II L2
 > cache bug fix in the kernelso that I can experiement
 > them toward the Cyrix III?

 arch/i386/kernel/setup.c display_cacheinfo()

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-03-16 19:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16 18:07 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?) S W
2002-03-16 19:42 ` Dave Jones [this message]
2002-03-16 21:01   ` Alan Cox
2002-03-16 20:50     ` Dave Jones
2002-03-17  4:22     ` 2.4.19-pre2 CentaurHauls VIA Samuel 2 stepping 2 SEGFAULT (RESOLVED) S W
2002-03-17 13:37       ` Dave Jones
2002-03-16 20:50 ` 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?) Alan Cox
2002-03-19 11:46 ` Padraig Brady

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=20020316204228.B15296@suse.de \
    --to=davej@suse.de \
    --cc=egberts@yahoo.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