From: Tejun Heo <tj@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: jeanseb <jeanseb.valette@free.fr>,
585556@bugs.debian.org, linux-ide@vger.kernel.org
Subject: Re: More ata_piix spurious IRQs
Date: Sat, 12 Jun 2010 19:33:09 +0200 [thread overview]
Message-ID: <4C13C4D5.5080300@kernel.org> (raw)
In-Reply-To: <1276298006.14011.149.camel@localhost>
Hello, Ben.
On 06/12/2010 01:13 AM, Ben Hutchings wrote:
> (more details at <http://bugs.debian.org/585556>).
>
> This is in Debian kernel version 2.6.32-15 which is based on stable
> version 2.6.32.14 but has your backported spurious IRQ handling patch
> taken from SLE11 (References: bnc#445872, bnc#589449). Any idea what's
> going wrong here? Is there a piece missing from that fix?
One great thing about traditional IDE is that the IRQ line is not
really under the control of the controller so the device can assert
the IRQ whether the controller want or not and there's nothing much
the driver can do to prevent runaway IRQs if the device is crazy
enough (some devices seem to have problem with toggling nIEN for
example). Ain't it just great? :-)
As the spurious interrupt handling kicked in, the spurious interrupts
itself shouldn't cause problem. It would be polling now, so it's
likely that the device is asserting interrupt and not responding to
commands properly. Does the drive work in other environments?
e.g. Can the BIOS recognize it and boot from it?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-06-12 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100611222746.37b5efa6@server.gazypan.dyndns.org>
2010-06-11 23:13 ` More ata_piix spurious IRQs Ben Hutchings
2010-06-12 17:33 ` Tejun Heo [this message]
2010-06-12 17:49 ` jeanseb
2010-06-12 19:06 ` Bug#585556: " maximilian attems
2010-06-12 20:38 ` Ben Hutchings
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=4C13C4D5.5080300@kernel.org \
--to=tj@kernel.org \
--cc=585556@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=jeanseb.valette@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).