public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Adam McKenna" <adam-dated-1006079431.a988a6@flounder.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: Tue, 13 Nov 2001 02:30:29 -0800	[thread overview]
Message-ID: <20011113023029.A15075@flounder.net> (raw)
In-Reply-To: <20011112234604.C29675@flounder.net> <E163aDx-0000aQ-00@the-village.bc.nu>
In-Reply-To: <E163aDx-0000aQ-00@the-village.bc.nu>

On Tue, Nov 13, 2001 at 09:51:21AM +0000, Alan Cox wrote:
> > I ask because I'm still having major problems with the OSB4 chipset on
> > 2.4.14.  I've had to disable DMA completely on my boxes to avoid IDE errors
> > and fs corruption.  Does anyone know of a patch that addresses the issues
> > with this chipset?
> 
> No. I spent some time digging into this problem with both Serverworks and
> Red Hat customers. With certain disks, certain OSB4 revisions and UDMA 
> the controller occasionally gets "stuck", the next DMA it issues starts
> by reissuing the last 4 bytes of the previous request and the entire thing
> goes totally to crap.
> 
> The -ac tree will detect this case and panic and hang the machine solid to
> avoid actual disk corruption. The real fix appears to be "dont do UDMA on
> the OSB4". The CSB5 seems fine.

I am having problems with both UDMA and Multiword DMA.  The problem doesn't
go away unless I disable CONFIG_IDEDMA_PCI_AUTO.

I don't know if there is actual FS corruption with MWord DMA, but there is
definitely a "hang" for a few seconds accompanied by a DMA error.

--Adam

-- 
Adam McKenna <adam@flounder.net>   | GPG: 17A4 11F7 5E7E C2E7 08AA
http://flounder.net/publickey.html |      38B0 05D0 8BF7 2C6D 110A

  reply	other threads:[~2001-11-13 10:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
2001-07-25  3:08 ` Rico Tudor
2001-07-26 16:11   ` Facing problem Dipak Biswas
2001-07-26 17:28     ` Fwd: " Dipak Biswas
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
2001-11-13  7:46   ` Adam McKenna
2001-11-13  9:51     ` Alan Cox
2001-11-13 10:30       ` Adam McKenna [this message]
2001-11-13 11:04         ` Alan Cox
2001-11-27  8:25           ` Adam McKenna
2001-07-25 15:46 ` Larry Sendlosky
  -- strict thread matches above, loose matches on Subject: below --
2001-07-29 21:50 Marvin Justice
2001-07-29 22:29 ` Ignacio Vazquez-Abrams
2001-07-29 22:37 ` 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=20011113023029.A15075@flounder.net \
    --to=adam-dated-1006079431.a988a6@flounder.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