From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: egberts@yahoo.com (S W)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?)
Date: Sat, 16 Mar 2002 20:50:09 +0000 (GMT) [thread overview]
Message-ID: <E16mL7x-00077q-00@the-village.bc.nu> (raw)
In-Reply-To: <20020316180705.34916.qmail@web10506.mail.yahoo.com> from "S W" at Mar 16, 2002 10:07:05 AM
> But I recalled Linux 2.2 having a bug fix for broken
> L2 cache in Cyrix II. So, it got me thinking again...
> (did Cyrix fix this L2 cache in certain subsequential
> core?)
Certain obscure early 6x86 cpus
> cache bug fix in the kernelso that I can experiement
> them toward the Cyrix III?
The Cyrix III is not even derived from the Cyrix processor line. VIA bought
both Cyrix and IDT's Winchip folks. The Cyrix III is the winchip sequel
(newer versions branded as VIA C3 as VIA dumped the cyrix name completely)
> Assuming no else sees VM bugs, I'll assume that this
> is Cyrix-specific. I've seen various VM BUGs for each
> patch releases since 2.4.17 particularly when
> compiling.
I suspect hardware problems. A considerable number of people run Cyrix III
C3 and now also Eden systems on Linux. It works very well.
Alan
next prev parent reply other threads:[~2002-03-16 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 18:07 S W
2002-03-16 19:42 ` Dave Jones
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 ` Alan Cox [this message]
2002-03-19 11:46 ` 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?) 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=E16mL7x-00077q-00@the-village.bc.nu \
--to=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
all inboxes | Powered by JetHome®