From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: S W <egberts@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?)
Date: Sat, 16 Mar 2002 21:50:23 +0100 [thread overview]
Message-ID: <20020316215023.D15296@suse.de> (raw)
In-Reply-To: <20020316204228.B15296@suse.de> <E16mLIY-00079l-00@the-village.bc.nu>
In-Reply-To: <E16mLIY-00079l-00@the-village.bc.nu>
On Sat, Mar 16, 2002 at 09:01:06PM +0000, Alan Cox 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.
> He's talking about a different bug. Some early 6x86 processors had weird
> problems with cache behaviour that would sometimes break stuff.
Ah, my bad. So much errata, so little memory..
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-16 20:50 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
2002-03-16 21:01 ` Alan Cox
2002-03-16 20:50 ` Dave Jones [this message]
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=20020316215023.D15296@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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