From: "Benjamin S. Scarlet" <lk-receive@greynode.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA problem (?) w/2.4.6-xfs and ServerWorks OSB4 Chipset
Date: Thu, 4 Oct 2001 11:20:12 -0400 [thread overview]
Message-ID: <200110041520.f94FKCn01275@greynode.net> (raw)
In-Reply-To: <E15mk45-0005Li-00@the-village.bc.nu>
In-Reply-To: <E15mk45-0005Li-00@the-village.bc.nu>
On Thursday 27 September 2001 06:55 pm, Alan Cox wrote:
> Long answer "I have been chasing a specific problem with OSB4, seagate
> drives and UDMA corruption. We can reliably reproduce it and see it on one
> set of machines. Serverworks cannot reproduce it elsewhere"
> I would thus be very interested if the current -ac "hardware just did
> something impossibly stupid" trap is hit.
Are you otherwise interested in machines seeing this problem? I have a
candidate. I'm running a SuperMicro 370DL3 with a Seagate ST320423A. For the
sake of simplicity I turned off DMA and filled the whole drive full of
zeroes. I see data corruption (non-zero data) on an otherwise inactive
machine just reading the drive back with "od", if I have DMA on with some
settings (udma2 in particular fails). Currently I'm using just kernel 2.4.9,
but if it would be useful I could run tests with kernels of your choosing.
Ben Scarlet
next prev parent reply other threads:[~2001-10-04 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 21:34 DMA problem (?) w/2.4.6-xfs and ServerWorks OSB4 Chipset Steven Timm
2001-09-27 22:55 ` Alan Cox
2001-09-28 14:53 ` Steven Timm
2001-09-28 15:04 ` Alan Cox
2001-10-04 15:20 ` Benjamin S. Scarlet [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-30 20:37 Marvin Justice
2001-09-30 20:50 ` Alan Cox
2001-09-30 21:08 ` Marvin Justice
2001-09-30 21:45 ` Alan Cox
2001-10-01 15:04 ` Steven Timm
2001-10-01 15:10 ` Mark Hahn
2001-10-01 15:23 ` Steven Timm
2001-10-01 14:59 ` Steven Timm
2001-10-12 20:31 DMA problem (?) w/2.4.6-xfs and Serverworks " Steven Timm
2001-10-12 21:12 ` Alan Cox
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=200110041520.f94FKCn01275@greynode.net \
--to=lk-receive@greynode.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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