From: "Nicolae P. Costescu" <nick@strongholdtech.com>
To: r.ems@gmx.net, Andre Hedrick <andre@linux-ide.org>,
linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
Date: Sat, 20 Apr 2002 13:32:11 -0400 [thread overview]
Message-ID: <4.3.2.7.2.20020420132907.03c59cd0@mail.strongholdtech.com> (raw)
In-Reply-To: <3CC1A228.2B9C72F6@gmx.net>
We gave up using kt266A chipset motherboards with anything faster than ATA100.
I can reproduce disk corruption within 30 seconds on any of the KT266A
motheroards we've tried that have a highpoint 370/372/372a either onboard
or on the RocketRaid133 controller.
Did not get the corruption when using ATA100 or slower (e.g. promise
fastrak 100 tx2).
Simple program that writes 1.2 gig to a file and reads them back (checking
the value) will find corruption every time on these boards, and I tried 5
motherboards (2 asus, 3 abit).
We switched to Intel I845 chipset and to AMD MPX chipset and haven't seen
the problem.
I thought this problem was linked with the VIA chipset PCI latency issue as
people were having the problem with high speed framegrabbers as well.
****************************************************
Nicolae P. Costescu, Ph.D. / Senior Developer
Stronghold Technologies
46040 Center Oak Plaza, Suite 160 / Sterling, Va 20166
Tel: 571-434-1472 / Fax: 571-434-1478
next prev parent reply other threads:[~2002-04-20 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 17:15 Richard Ems
2002-04-20 17:32 ` Nicolae P. Costescu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-16 13:28 E M Recio
2002-04-16 21:12 ` Martin Eriksson
2002-04-16 23:44 ` Michael Obster
2002-04-16 22:50 ` Rene Rebe
2002-04-16 22:55 ` Martin Eriksson
2002-04-17 3:14 ` Emilio Recio
2002-04-16 23:45 ` Denis Vlasenko
2002-04-17 1:55 ` Josh McKinney
2002-04-17 3:47 ` Andre Hedrick
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=4.3.2.7.2.20020420132907.03c59cd0@mail.strongholdtech.com \
--to=nick@strongholdtech.com \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.ems@gmx.net \
/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®