From: "Daniel J Blueman" <daniel.blueman@btinternet.com>
To: "'Martin Josefsson'" <gandalf@wlug.westbo.se>,
"'Ville Herva'" <vherva@niksula.hut.fi>
Cc: "'Andrew Morton'" <akpm@zip.com.au>,
<linux-kernel@vger.kernel.org>,
"'Jani Forssell'" <jani.forssell@viasys.com>
Subject: RE: Via KT133 pci corruption: stock 2.4.18pre2 oopses as well
Date: Thu, 10 Jan 2002 00:19:38 -0000 [thread overview]
Message-ID: <001401c1996c$7d8dd790$0100a8c0@icarus> (raw)
In-Reply-To: <Pine.LNX.4.21.0201100025440.14057-100000@tux.rsn.bth.se>
> I havn't followed this thread but I have a machine with an
> Asus A7V motherboard with KT133 chipset and we had massive
> corruption before christmas, both ide and network had
> corrupted packets. and now after christmas we ran memtest86
> on it and a 256MB module was very very broken. and we got
> alot of Oopses and all kinds of strange stuff happened.
>
> We've replaved that memory module now and now it's better but
> I have to say that the KT133 or atleast the Asus A7V
> motherboard seems to be quite broken. we have a lot of
> spurious irq's and the ide controllers freak when but under
> some load and start getting irq timeouts and resets the ide
> channels over and over again with some delay in between when
> it kind of works, slow as hell but works.
There are known issues with the VIA 82C686A/B chipset south-bridge and
IDE in particular. Make sure you have the latest BIOS and latest VIA
4in1 drivers to workaround the IDE corruption and other known issues
(sound problems with certain soundcards).
Dan
___________________
Daniel J Blueman
next prev parent reply other threads:[~2002-01-10 0:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 19:58 2.2.21pre2 oops Ville Herva
2002-01-08 20:16 ` Alan Cox
2002-01-08 20:13 ` Ville Herva
2002-01-09 12:45 ` Ville Herva
2002-01-09 15:26 ` Via KT133 pci corruption: stock 2.4.18pre2 oopses as well Ville Herva
2002-01-09 21:00 ` Andrew Morton
2002-01-09 21:57 ` Ville Herva
2002-01-09 23:30 ` Martin Josefsson
2002-01-10 0:19 ` Daniel J Blueman [this message]
2002-01-10 0:41 ` Martin Josefsson
2002-01-10 1:04 ` Daniel J Blueman
2002-01-10 5:34 ` Ville Herva
2002-01-10 12:01 ` Henrique de Moraes Holschuh
2002-01-10 12:56 ` Martin Josefsson
2002-01-10 13:37 ` Ville Herva
2002-01-09 23:33 ` Daniel J Blueman
2002-01-10 6:34 ` Ville Herva
2002-01-10 6:40 ` Andrew Morton
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='001401c1996c$7d8dd790$0100a8c0@icarus' \
--to=daniel.blueman@btinternet.com \
--cc=akpm@zip.com.au \
--cc=gandalf@wlug.westbo.se \
--cc=jani.forssell@viasys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@niksula.hut.fi \
/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