From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] Re: 2.6.11-rc4 libata-core (irq 30: nobody cared!)
Date: Mon, 28 Feb 2005 11:10:33 -0500 [thread overview]
Message-ID: <42234279.6030004@rtr.ca> (raw)
In-Reply-To: <4220D9DE.10904@pobox.com>
>"irq XX: nobody cared" is a screaming interrupt situation, which could have 1001 causes.
Speaking of which. The 3ware drivers appear to have a bug
in their handling of this. They *always* report "handled=1"
from their interrupt routines, regardless of whether it was
their hardware or not that was signalling for attention.
Cheers
prev parent reply other threads:[~2005-02-28 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050224015859.55191.qmail@web40910.mail.yahoo.com>
[not found] ` <421D3D33.9060707@pobox.com>
2005-02-24 2:36 ` [PATCH] Re: 2.6.11-rc4 libata-core (irq 30: nobody cared!) Jeff Garzik
2005-02-24 2:58 ` Brian Kuschak
2005-02-26 19:32 ` Rogério Brito
2005-02-26 20:19 ` Jeff Garzik
2005-02-26 23:18 ` Rogério Brito
2005-02-28 16:10 ` 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=42234279.6030004@rtr.ca \
--to=liml@rtr.ca \
--cc=jgarzik@pobox.com \
--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).