From: Alan <alan@lxorguk.ukuu.org.uk>
To: Bjorn Wesen <bjorn.wesen@axis.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.20-rc3 IRQ race upon resume? => killing SATA IRQ
Date: Thu, 4 Jan 2007 10:13:32 +0000 [thread overview]
Message-ID: <20070104101332.165a54d3@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0701040244300.15167@localhost.localdomain>
> (correctly probably). Question is, where is the irq coming from then.
>
> Obviously this is a horribly wrong fix, since if the interrupt is shared, we
> will shadow the other interrupt so it never gets run (and corrupt our own
> BM DMA operations).
I wonder if it's left over from the resume I/O completing or the chip
coming back up in a stupid state. What occurs if the bit is cleared
during the early resume before IRQs are turned back on ?
prev parent reply other threads:[~2007-01-04 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 23:26 2.6.20-rc3 IRQ race upon resume? => killing SATA IRQ Bjorn Wesen
2007-01-04 1:55 ` Bjorn Wesen
2007-01-04 4:37 ` Tejun Heo
2007-01-04 10:13 ` Alan [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=20070104101332.165a54d3@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.wesen@axis.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).