archive mirror
 help / color / mirror / Atom feed
From: David Monniaux <>
Subject: more on VIA 686B (trials)
Date: Thu, 14 Jun 2001 19:44:02 +0200	[thread overview]
Message-ID: <20010614194402.A19960@picsou.chatons> (raw)

Due to a catastrophic fan short-circuit, I was forced to exchange my
686A-based motherboard for a 686B. Bad idea!

The 686A MB (MSI-6330 aka K7T-Pro) worked perfectly well: no crashes,
UDMA 66. It accepted Athlon-optimized kernels.

The 686B MB (K7T-Lite) crashed if used with DMA (any kind - mdma0 to UDMA100),
whatever version of the "VIA fixes" was in place.
Furthermore, upgrading to BIOS 2.7 (instead of 2.5), including a so-called
"SB Live fix", made the system permanently unstable.
On top of that, running an Athlon-optimized kernel (whether or not it
was compile with =march=i686 (egcs-1.1.2) or -march=athlon (gcc 2.96)
immediately oops and crash during /etc/rc!

I replaced this mobo+Duron with an ASUS A7V133+Athlon, which
work perfectly well.
Athlon-optimized kernel, UDMA100, no problem whatsoever.

So we have two kinds of problems:
- *certain* 686B motherboards crash if used with an Athlon kernel
  (and it does not depend on the compiler options, rather on hand-made
  Athlon optimizations)
- *certain* 686B motherboards will crash if used with any kind of DMA
  under heavy disk access
- some 686B motherboards have absolutely no problem.

Crash test:
for i in `seq 1 30` ; do echo $i; tar xfz X410src-1.tgz ; rm -rf xc; done

All the above is valid for kernel version 2.4.2-RedHat to 2.4.5ac9...

Another lesson: the MSI K7T-Lite is absolute crap. The manual sucks,
and the BIOS upgrades supposed to make the machine stabler actually
make it randomly hiccup (EVEN under Windows, which is what I suppose
those mobos are supposed to run).

David Monniaux  
Laboratoire d'informatique de l'École Normale Supérieure,
Paris, France

             reply	other threads:[~2001-06-14 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-14 17:44 David Monniaux [this message]
2001-06-14 18:11 ` Cory Watson
2001-06-14 18:10   ` Alan Cox
2001-06-14 18:29     ` Cory Watson
2001-06-14 18:11 ` Rachel Greenham

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010614194402.A19960@picsou.chatons \ \ \
    --subject='Re: more on VIA 686B (trials)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).