From: Chuck Berg <chuck@encinc.com>
To: linux-kernel@vger.kernel.org
Subject: HPT372 DMA corruption
Date: Fri, 9 Jan 2004 15:05:01 -0500 [thread overview]
Message-ID: <20040109150501.A5891@timetrax.localdomain> (raw)
I have an HPT372 onboard a Soyo Dragon KT400 board. I get corruption when
reading from drives on this controller. (I don't dare write, so I don't
know if writes are affected as well). I'm using 2.6.1, but have experienced
this problem with older kernels (at least it's not crashing anymore).
Disabling DMA on these drives stops the corruption.
It only happens when I heavily exercise certain other devices on the system
at the same time. This includes both a network and a SCSI PCI card that
share an irq with the HPT372, but also a firewire card that does not. Load
on the other onboard IDE interfaces (which do not demonstrate the
corruption) does not trigger it.
I have four identical drives in the system. I've switched cables around to
verify that the problem follows the HPT372. I have no problems when I move
the drives to a Promise card. I have run memtest86 for over 24 hours with
no errors.
It happens whether I read the /dev/hd* devices, a file on the filesystem,
or using /dev/raw.
Here's an example of the corruption. (cmp -l output, left is bad right is
good). It always consists of bytes being replaced with 0. It's usually 4,
but sometimes 64 bytes at a time. On average, about 256 bytes per gigabyte
read are corrupt.
51642365 0 211
51642366 0 154
51642367 0 163
51642368 0 120
63700989 0 100
63700990 0 153
63700991 0 216
63700992 0 2
89260029 0 31
89260030 0 327
89260031 0 200
89260032 0 13
More information (.config, /proc/{interrupts,cpuinfo,ioports,iomem,ide}, bootup
messages, lspci -vvv) is at:
http://www.encinc.com/~chuck/kt400/2.6.1/
Thanks for any help.
next reply other threads:[~2004-01-09 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 20:05 Chuck Berg [this message]
2004-01-09 20:24 ` Richard B. Johnson
2004-01-13 23:30 ` Chuck Berg
2004-01-14 0:05 ` Måns Rullgård
2004-01-23 2:27 ` 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=20040109150501.A5891@timetrax.localdomain \
--to=chuck@encinc.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
all inboxes | Powered by JetHome®