From: "Dale Farnsworth" <dale@farnsworth.org>
To: linux-kernel@vger.kernel.org
Subject: Re: VIA silent disk corruption - patch
Date: Tue, 6 Feb 2001 08:52:23 -0700 [thread overview]
Message-ID: <20010206085223.A28894@zenos.local.farnsworth.org> (raw)
In article <20010205190527.A314@colonel-panic.com>,
Peter Horton <pdh@colonel-panic.com> wrote:
> + * VIA VT8363 host bridge has broken feature 'PCI Master Read
> + * Caching'. It caches more than is good for it, sometimes
> + * serving the bus master with stale data. Some BIOSes enable
> + * it by default, so we disable it.
Another data point:
I have an ASUS A7V motherboard with via vt82c686a and Promise pdc20265
IDE controllers. I noticed disk data corruption when I enabled DMA.
The corrupted data was 4K bytes long on 4K byte boundaries and occurred
about once for every couple of gigabytes copied via cpio.
I saw this corruption when the disks were connected to the pdc20265
as well as to the 686a.
I also noticed that turning off read caching eliminated the corruption.
However, if I enable the BIOS parameter "I/O Recovery Time", I can still
enable read caching without seeing any data corruption.
The lastest BIOS revision (1005C) enables "I/O Recovery Time" by default
where the previous revision I had (1004D) did not.
-Dale
--
Dale Farnsworth dale@farnsworth.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-06 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 15:52 Dale Farnsworth [this message]
2001-02-06 16:01 ` Udo A. Steinberg
2001-02-07 23:19 ` Peter Horton
2001-02-06 18:17 ` Peter Horton
-- strict thread matches above, loose matches on Subject: below --
2001-02-06 19:57 Jonathan Morton
2001-02-06 20:09 ` Jonathan Morton
2001-02-05 20:20 Petr Vandrovec
2001-02-05 19:05 Peter Horton
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=20010206085223.A28894@zenos.local.farnsworth.org \
--to=dale@farnsworth.org \
--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®