From: Ville Herva <vherva@niksula.hut.fi>
To: Martin Josefsson <gandalf@wlug.westbo.se>
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 07:34:41 +0200 [thread overview]
Message-ID: <20020110073441.P1200@niksula.cs.hut.fi> (raw)
In-Reply-To: <20020109235722.L1200@niksula.cs.hut.fi> <Pine.LNX.4.21.0201100025440.14057-100000@tux.rsn.bth.se>
In-Reply-To: <Pine.LNX.4.21.0201100025440.14057-100000@tux.rsn.bth.se>; from gandalf@wlug.westbo.se on Thu, Jan 10, 2002 at 12:30:37AM +0100
On Thu, Jan 10, 2002 at 12:30:37AM +0100, you [Martin Josefsson] claimed:
>
> 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 ran memtest86 at one point but it showed nothing. We changed the memory
modules, and it didn't help. (I did seem like the order and placement of the
modules on the mobo made difference, but that turned out to be false
positive. Trying harder made the corruption happen again.)
Also, we only begun to see oopses when we stress tested hpt370 ide AND
network (so far we did only stress hpt370 and run "normal" stuff). The board
never oopsed or behaved strangely other than the hpt370 corruption and the
hpt370+3c905 stress test oopses.
> We are going to replace the motherboard with one with VIA KT266A chipset,
> hope that works better.
If we get around to replace the bugger, the one thing I'll make sure is that
the replacement is not Via. Even if 1000 people told me KT266A was stable.
-- v --
v@iki.fi
next prev parent reply other threads:[~2002-01-10 5:35 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
2002-01-10 0:41 ` Martin Josefsson
2002-01-10 1:04 ` Daniel J Blueman
2002-01-10 5:34 ` Ville Herva [this message]
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=20020110073441.P1200@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=akpm@zip.com.au \
--cc=gandalf@wlug.westbo.se \
--cc=jani.forssell@viasys.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®