mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "Dave Woods" <dwoods@fastclick.com>, <linux-kernel@vger.kernel.org>
Cc: "Stephanie Marasciullo" <smarasciullo@fastclick.com>
Subject: Re: Problems with DMA on IDE/ServerWorks/Seagate.
Date: Thu, 15 Jul 2004 12:24:45 +0200	[thread overview]
Message-ID: <200407151224.45341.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <7632915A8F000C4FAEFCF272A880344105095A@Ehost067.exch005intermedia.net>

On Thursday 15 of July 2004 02:16, Dave Woods wrote:
> Please CC me on all replies, as I am not subscribed to the list.
>
> We have diagnosed a problem (file corruption) using Ultra DMA & IDE with
>
> ServerWorks OSB4 Chipset and Seagate drives under heavy disk I/O.
> We were able to find a thread that discusses this problem in detail,
> but dates back to 2001. We have nearly 100 boxes using this
> configuration
> with kernal 2.4.20, and we can reproduce the problem easily with a perl
> script using md5 checksums.
>
> The applicable thread is given below:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0109.3/1006.html
>
> We've disabled DMA on several machines, and that appears to fix
> the problem. However, despite seeing this workaround mentioned
> several times, we have not had any luck downshifting to mdma2.
> Every time I attempt it, all disk accesses freeze up, and the box
> has to be rebooted.
>
> Our question: short of disabling DMA on all of our machines, what
> other alternatives are there? I've played with using the hdparm -p
> parameter prior to issuing hdparm -X34 and hdparm -d1, but it
> doesn't like it. Is there a simple fix to this problem out there?

Upgrade to 2.4.26 and see if it fixes your problem.


  reply	other threads:[~2004-07-15 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15  0:16 Dave Woods
2004-07-15 10:24 ` Bartlomiej Zolnierkiewicz [this message]
2004-07-15 13:11 ` Jeff Garzik
2004-07-15  8:15 Rico Tudor

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=200407151224.45341.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=dwoods@fastclick.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smarasciullo@fastclick.com \
    /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®