From: Jussi Laako <jlaako@pp.htv.fi>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA 686B/Data Corruption
Date: Fri, 29 Jun 2001 00:27:49 +0300 [thread overview]
Message-ID: <3B3BA155.98D3B636@pp.htv.fi> (raw)
In-Reply-To: <E15FYeP-0006Yq-00@the-village.bc.nu>
A little test report follows...
Just tested RedHat's 2.4.3-12 and 2.4.5-ac19 on A7V133 mobo. RedHat's kernel
seems to work without lockups, but 2.4.5-ac19 doesn't (locks up at boot,
compiled w/o athlon optimization and ACPI), so no changes on that.
2.4.3-12 also correctly detects cable connected to VIA controller as 40-w
while 2.4.5-ac19 still detects it as 80-w.
2.4.3-12 although seems to have the reiserfs unmount lock race, so I can't
use it... :(
- Jussi Laako
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
next prev parent reply other threads:[~2001-06-28 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 1:57 VIA 686B/Data Corruption FAQ Gareth Hughes
2001-06-28 10:03 ` Alan Cox
2001-06-28 21:27 ` Jussi Laako [this message]
2001-06-28 21:29 ` VIA 686B/Data Corruption Alan Cox
2001-06-28 21:41 ` Ryan W. Maple
2001-06-28 21:48 ` Alan Cox
2001-06-28 22:15 ` Jussi Laako
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=3B3BA155.98D3B636@pp.htv.fi \
--to=jlaako@pp.htv.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--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