From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ASUS KT266A/VT8233 board and UDMA setting
Date: Fri, 4 Jan 2002 08:48:07 -0800 [thread overview]
Message-ID: <20020104084807.A16446@greenhydrant.com> (raw)
In-Reply-To: <20020104112834.A20724@suse.cz> <E16MSOG-0003ch-00@the-village.bc.nu> <20020104153721.E1331@niksula.cs.hut.fi>
In-Reply-To: <20020104153721.E1331@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Fri, Jan 04, 2002 at 03:37:21PM +0200
On Fri, Jan 04, 2002 at 03:37:21PM +0200, Ville Herva wrote:
>
> We are still seeing what seems to be Via PCI corruption when using HPT370 on
> Abit-KT7-RAID. This is pretty high load (stream read/write two disks in
> parallel.) It appears as 90-160 byte disk corruption.
>
> It has been reproduced on 2.2.18pre19 + ide, 2.2.20+ide and 2.4.15.
>
> We now seem to have found a BIOS setting that cures this for 2.2.20+ide.
> The weird thing is that if we boot 2.2.21pre2+ide (pre2 includes the 2.4
> backported VIA fixes), the corruption occurs.
>
> We'll try to diff lspci -vvxxx outputs and post a more detailed report
> shortly.
What's the BIOS setting?
-Dave
next prev parent reply other threads:[~2002-01-04 16:48 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 22:34 Two hdds on one channel - why so slow? Krzysztof Oledzki
2002-01-01 23:07 ` Brian
2002-01-01 23:32 ` Andre Hedrick
2002-01-02 0:52 ` H. Peter Anvin
2002-01-02 1:19 ` Benjamin LaHaise
2002-01-02 1:24 ` H. Peter Anvin
2002-01-02 2:03 ` Benjamin LaHaise
2002-01-02 4:13 ` Andre Hedrick
2002-01-02 17:21 ` Krzysztof Oledzki
2002-01-02 18:41 ` Vojtech Pavlik
2002-01-02 19:31 ` Andre Hedrick
2002-01-02 20:23 ` Brian
2002-01-02 23:30 ` Ricky Beam
2002-01-03 1:52 ` Mark Hahn
2002-01-03 5:57 ` Ricky Beam
2002-01-04 2:54 ` Petro
2002-01-04 3:04 ` Arnaldo Carvalho de Melo
2002-01-04 4:29 ` ASUS KT266A/VT8233 board and UDMA setting Dmitri Pogosyan
2002-01-04 9:25 ` Vojtech Pavlik
2002-01-04 10:35 ` Alan Cox
2002-01-04 10:28 ` Vojtech Pavlik
2002-01-04 11:20 ` Alan Cox
2002-01-04 13:37 ` Ville Herva
2002-01-04 16:48 ` David Rees [this message]
2002-01-04 17:00 ` Alan Cox
2002-01-05 19:20 ` Dmitri Pogosyan
2002-01-05 7:20 ` Dmitri Pogosyan
2002-01-04 18:19 ` Two hdds on one channel - why so slow? Stephan von Krawczynski
2002-01-04 18:38 ` Alan Cox
2002-01-04 18:30 ` Stephan von Krawczynski
2002-01-05 0:52 ` J.A. Magallon
2002-01-05 9:41 ` Nick Holloway
2002-01-05 12:04 ` Henning P. Schmiedehausen
2002-01-05 1:28 ` Andre Hedrick
2002-01-08 23:59 ` Ricky Beam
2002-01-09 0:10 ` Mark Hahn
2002-01-09 15:27 ` Andre Hedrick
2002-01-09 16:25 ` MTBF Was: " Richard B. Johnson
2002-01-08 23:46 ` Ricky Beam
2002-01-07 8:11 ` Stevie O
2002-01-07 15:57 ` Thomas Molina
2002-01-07 16:14 ` Ricky Beam
2002-01-07 16:40 ` Thomas Molina
2002-01-07 22:23 ` Ancient Memories [was: Two hdds on one channel - why so slow?] Edesio Costa e Silva
2002-01-07 23:18 ` M. Edward (Ed) Borasky
2002-01-07 18:48 ` Two hdds on one channel - why so slow? Andre Hedrick
2002-01-07 20:19 ` Petro
2002-01-07 22:31 ` Dmitri Pogosyan
2002-01-08 13:50 ` Alan Cox
2002-01-08 14:45 ` Mike Dresser
2002-01-08 14:57 ` James A Sutherland
2002-01-08 17:15 ` Wakko Warner
2002-01-02 21:23 ` Jeffrey W. Baker
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=20020104084807.A16446@greenhydrant.com \
--to=dbr@greenhydrant.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