From: Mark Lord <liml@rtr.ca>
To: Christoph Burger-Scheidlin <andersin@freenet.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: ide dma bug?
Date: Mon, 05 Sep 2005 12:00:58 -0400 [thread overview]
Message-ID: <431C6BBA.2070105@rtr.ca> (raw)
In-Reply-To: <200509051239.14713.andersin@freenet.de>
Christoph Burger-Scheidlin wrote:
>
> I had a similar problem with a SiI680 (and since lspci states that Silicon
> Image was formerly CMD Tech. I thought it might be related). In my case, I
> got lost interrupts and dma errors when I used both channels of the SiI680
> simultaneously. I serialized both channels (kernel parameters ide2=serialize
> ide3=serialize) and the problems went away (I am not sure though how much of
> a performance impact it has).
Note for others:
Using the ideX=serialize parameter simply causes the IDE driver
to never allow simultaneous activity on the "serialized" channels.
A small performance tradeoff in exchange for reliable operation.
The drives can still seek independently and all that, just without
any overlap in operation.
Cheers
prev parent reply other threads:[~2005-09-05 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 20:18 ide dma bug? Trevor Cordes
2005-09-05 11:39 ` Christoph Burger-Scheidlin
2005-09-05 16:00 ` Mark Lord [this message]
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=431C6BBA.2070105@rtr.ca \
--to=liml@rtr.ca \
--cc=andersin@freenet.de \
--cc=linux-ide@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 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.