From: Jeff Garzik <jgarzik@pobox.com>
To: izvekov@lps.ele.puc-rio.br
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: libata sata_sil broken on 2.6.13.1
Date: Fri, 16 Sep 2005 02:41:39 -0400 [thread overview]
Message-ID: <432A6923.2070000@pobox.com> (raw)
In-Reply-To: <61375.200.141.106.169.1126842173.squirrel@correio.lps.ele.puc-rio.br>
izvekov@lps.ele.puc-rio.br wrote:
>From what i understand up to now, my problem wasnt that the controller
> triggered an interrupt with NIEN set, but that the handler was returning
> it as not handled.
Essentially that is what happened. Albert's patch simply fixed it
another way.
ATA is a bit annoying in that, we try to "know" when an interrupt is
expected. There is no 100% solution that simply allows us to check for
pending interrupts, without side effects.
Thus the explosion when unexpected interrupts are received.
Jeff
next parent reply other threads:[~2005-09-16 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61637.200.141.106.169.1126660632.squirrel@correio.lps.ele.puc-rio.br>
[not found] ` <60519.200.141.106.169.1126727337.squirrel@correio.lps.ele.puc-rio.br>
[not found] ` <43290893.7070207@pobox.com>
[not found] ` <1126790860.19133.75.camel@localhost.localdomain>
[not found] ` <61929.200.141.106.169.1126815191.squirrel@correio.lps.ele.puc-rio.br>
[not found] ` <1126823405.7034.14.camel@localhost.localdomain>
[not found] ` <61375.200.141.106.169.1126842173.squirrel@correio.lps.ele.puc-rio.br>
2005-09-16 6:41 ` Jeff Garzik [this message]
2005-09-16 22:10 ` libata sata_sil broken on 2.6.13.1 Matheus Izvekov
2005-09-22 2:46 ` Jeff Garzik
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=432A6923.2070000@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=izvekov@lps.ele.puc-rio.br \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).