From: Mark Lord <liml@rtr.ca>
To: Roger Heflin <rheflin@atipa.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: What determines which interrupts are shared under Linux?
Date: Wed, 16 Aug 2006 18:54:39 -0400 [thread overview]
Message-ID: <44E3A22F.20400@rtr.ca> (raw)
In-Reply-To: <44E208AD.8060505@atipa.com>
Roger Heflin wrote:
>
> It looks like the older DMA recovery code never works on this chipset,
> once it goes into DMA recovery it never comes out of it. I am looking
> at that to see if anything can be done about it.
You could try booting with ide2=serialize as a kernel parameter.
That should ensure the two channels are never in use simultaneously.
Trades off a bit of performance for a bit of reliability.
Cheers
next prev parent reply other threads:[~2006-08-16 22:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 14:17 What determines which interrupts are shared under Linux? Roger Heflin
2006-08-15 14:30 ` Sergei Shtylyov
2006-08-15 14:38 ` Roger Heflin
2006-08-15 14:47 ` Len Brown
2006-08-15 15:06 ` Alan Cox
2006-08-15 15:24 ` Roger Heflin
2006-08-15 15:55 ` Alan Cox
2006-08-15 17:47 ` Roger Heflin
2006-08-15 18:13 ` Alan Cox
2006-08-16 22:54 ` Mark Lord [this message]
2006-08-17 0:39 ` Alan Cox
2006-08-17 13:18 ` Roger Heflin
2006-08-15 15:19 ` linux-os (Dick Johnson)
2006-08-15 15:19 ` linux-os (Dick Johnson)
2006-08-15 17:31 ` Terence Ripperda
2006-08-15 17:42 ` Sergei Shtylyov
2006-08-15 17:43 ` Terence Ripperda
[not found] <fa.xiop2gho7OdOydmzXzpUsR5ksXM@ifi.uio.no>
2006-08-15 14:29 ` Robert Hancock
[not found] ` <fa.1abHK6YDIfV51f77xhbkgnQpLwk@ifi.uio.no>
[not found] ` <fa.UkMpPU+vkXMkIeBVGEpBG9C87M4@ifi.uio.no>
[not found] ` <fa.9EHh5X478LQIXFY79H/n57rBfRE@ifi.uio.no>
[not found] ` <fa.OQ0aZlfKc9NmI+ugRx8PT515Nks@ifi.uio.no>
2006-08-15 23:04 ` Robert Hancock
2006-08-15 23:11 ` Roger Heflin
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=44E3A22F.20400@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rheflin@atipa.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 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.