public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: S W <egberts@yahoo.com>
Cc: linux-kernel@vger.kernel.org, davej@suse.de, alan@lxorguk.ukuu.org.uk
Subject: Re: 2.4.19-pre2 Cyrix III SEGFAULT (Cyrix II redux?)
Date: Tue, 19 Mar 2002 11:46:13 +0000	[thread overview]
Message-ID: <3C972505.4080001@antefacto.com> (raw)
In-Reply-To: <20020316180705.34916.qmail@web10506.mail.yahoo.com>

We're noticing weirdness here also.
Certain apps are SEGFAULTing. Some apps much
more than others. An important point is that
the apps SEGFAULTed in the exact same place
each time. Doing a trace of the core didn't
show anything weird being executed, it just
SEGFAULTed. Does this suggest a cache issue?
A power cycle changed things (made the faults
more/less frequent). The particular app we were
having trouble with was snmpd (net-snmp). Also
much less frequent was vim and bash. When these
crashed, it was also in the same place. An
important note is that snmpd would crash in
exactly the same place across power cycles.
Recompiling a later version of snmpd "fixed"
the problem. I.E. SEGFAULTs are now very infrequent.
We saved the particular snmpd binary that was
causing trouble, for testing.

We tested with Samuel II & Ezra & Celeron CPUs on
both Advantech PCM9576 & Ibase M700 motherboards.
Celeron was OK, Samuel II was OK, ezra caused segfaults.

We also passed memtest86 (RAM is also ECC) and
multiple kernel compiles worked OK also.

Kernel 2.4.16
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
glibc 2.2.4

Padraig.

S W wrote:
> 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.


      parent reply	other threads:[~2002-03-19 11:47 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
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 [this message]

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=3C972505.4080001@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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