From: S W <egberts@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?)
Date: Sat, 16 Mar 2002 10:07:05 -0800 (PST) [thread overview]
Message-ID: <20020316180705.34916.qmail@web10506.mail.yahoo.com> (raw)
In compiling the kernel, I've been experiencing the
same gcc-2.96 (and gcc-3.0+) SEGFAULT again on Cyrix
III GigaPro (733Mhz, Samuel II core chipset).
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?)
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?
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.
MOBO DETAILS:
Soyo 7VEM motherboard (686A PL133, despite having an
ALL VIA-chipsets (Cyrix III-733Mhz, VIA-VT82C596A
multifunctional audio/AGPvideo/modem, Rhine Ethernet,
Trident APG), no drivers are loaded into the kernel
except for EXT2, Trident Video (no framebuffer
support) and IDE (via82cxxx.c). BARE KERNEL. (BTW,
it was a $250 Fry's special running a barebone
multimedia Linux, so no snickering please.).
Passed memtest86.
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/
next reply other threads:[~2002-03-16 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 18:07 S W [this message]
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 ` 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=20020316180705.34916.qmail@web10506.mail.yahoo.com \
--to=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®