From: Mikael Hedin <mikael.hedin@irf.se>
To: linux-kernel@vger.kernel.org
Subject: Disk corruption with VIA KT266 chipset
Date: Mon, 05 Nov 2001 15:16:58 +0100 [thread overview]
Message-ID: <E160kYc-0004Ol-00@zodiac.debian.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
[Please cc me on replies, I only read the list archives]
Hi,
I have a Soltek KT75DRV motherboard, with the VIA KT266 chipset, and
in particular the VIA 8233 southbridge. I use two IDE disks (one
ATA100, one ATA33) with UDMA enabled and stock linux-2.4.13.
With heavy disk use, I get random corruptions. E.g. "cp -a /usr /mnt;
diff -ruq /usr /mnt" shows a couple of files that differ. OTOH, "cp
-a linux linux2; diff -ruq linux linux2" use to run fine as many times
as you like. Thus I suspect the error is prone to show up on large
files transfers over DMA.
I talked to Vojtech Pavlik, and we concluded the problem is the
transfer between the VIA8233 and the memory (memtest86 show no
errors.)
I've replaced the motherboard once, without much difference, so it's
probably not plain broken.
Not using DMA solves the problem, but of course it's not what I want,
I get hdparm -t reading around 2 MB/s :-(
I'd be happy to try out any solution, I already had to reinstall the
system a couple of times due to this.
Regards,
Micce
BTW The sound (ALSA driver) of this board is horrible, but that might
be as intended by Soltek;)
--
Mikael Hedin, MSc +46 (0)980 79176
Swedish Institute of Space Physics +46 (0)8 344979 (home)
Box 812, S-981 28 KIRUNA, Sweden +46 (0)70 5891533 (mobile)
[gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22]
Nu lubbar vi på fjället hela dan och trivs med det
Jesse James '71
militia explosion World Trade Center assassination Mossad $400 million
in gold bullion COSCO FSF domestic disruption Monica Lewinsky genetic
security jihad terrorist Area 51
reply other threads:[~2001-11-05 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E160kYc-0004Ol-00@zodiac.debian.net \
--to=mikael.hedin@irf.se \
--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®