From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Richard Wohlstadter <rwohlsta@watson.wustl.edu>
Cc: linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: dma problems with Serverworks CSB5 chipset
Date: Tue, 3 Aug 2004 15:08:21 -0300 [thread overview]
Message-ID: <20040803180821.GB6265@logos.cnet> (raw)
In-Reply-To: <4107E4B3.6070904@watson.wustl.edu>
On Wed, Jul 28, 2004 at 12:38:59PM -0500, Richard Wohlstadter wrote:
> Hello,
>
> I have 200 servers in a cluster running vanilla kernel 2.4.26(not
> tainted). Under heavy I/O activity I have various servers completely
> lose access to their IDE bus. Logs show the same error every time:
>
> hda: dma_timer_expiry: dma status == 0x61
>
> The kernel resets the IDE bus at this point. Sometimes things start
> working again but mostly all ide access is lost and I have to reboot the
> server. The chipset is:
>
> 00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
>
> I have searched archives for problems with this chipset and I have seen
> other users with this same issue, but no resolution to the problem. Is
> there a known problem with this chipset version or could there be some
> issues still with the serverworks driver? Any help would be much
> appreciated. Thanks.
Richard,
ServerWorks OSB4/5 chipsets are known to not work reliably with the Linux
IDE code. AFAIK its a hardware problem which we dont correctly work around.
Have you tried disabling DMA?
Bart and Alan are IDE experts, they can probably give you more useful
information.
next prev parent reply other threads:[~2004-08-03 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 17:38 dma problems with Serverworks CSB5 chipset Richard Wohlstadter
2004-08-03 18:08 ` Marcelo Tosatti [this message]
2004-08-03 17:31 ` Alan Cox
2004-08-03 18:47 ` Rich Wohlstadter
2004-08-08 18:09 ` Torbjörn Olander
2004-08-23 18:59 ` Torbjörn Olander
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=20040803180821.GB6265@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rwohlsta@watson.wustl.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.