From: Tejun Heo <tj@kernel.org>
To: Johannes Stezenbach <js@sig21.net>
Cc: Hans Werner <HWerner4@gmx.de>,
linux-kernel@vger.kernel.org, trenn@suse.de, mmalygin@ked.de,
hancockrwd@gmail.com, greg@kroah.com
Subject: Re: Samsung N130 ATA exception after 5min uptime -- Phoenix FailSafe issue?
Date: Mon, 04 Jan 2010 09:56:24 +0900 [thread overview]
Message-ID: <4B413CB8.1050808@kernel.org> (raw)
In-Reply-To: <20100104004147.GA19558@sig21.net>
Hello,
On 01/04/2010 09:41 AM, Johannes Stezenbach wrote:
> I've updated bug#14314. It is certainly a BIOS issue, but the
> "spurious IRQ" check deals way better with it than the previous
> 30sec hang waiting for timeout. IMHO the patch should be merged
> into mainline asap. Or do you think it has any downside?
The danger is that when the hardware is actually malfunctioning and
causing IRQ storm, the driver will tell the IRQ subsystem that the
IRQs aren't spurious. This will bypass the IRQ storm detection logic
and lead to complete system lockup under such conditions. Small
modification to the patch should remove that problem. I'll post an
updated patch soon.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-01-04 0:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 12:04 Samsung N130 ATA exception after 5min uptime -- Phoenix FailSafe issue? Hans Werner
2010-01-03 22:11 ` Johannes Stezenbach
2010-01-03 22:59 ` Tejun Heo
2010-01-04 0:41 ` Johannes Stezenbach
2010-01-04 0:56 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-26 16:42 Johannes Stezenbach
2009-11-28 19:19 ` Greg KH
2009-11-28 20:30 ` Robert Hancock
2009-11-28 21:34 ` Greg KH
2009-11-28 22:22 ` Johannes Stezenbach
2009-11-29 0:17 ` Greg KH
2009-11-29 0:51 ` Johannes Stezenbach
2009-11-30 8:52 ` Tejun Heo
2009-11-30 10:21 ` Johannes Stezenbach
2009-11-30 11:06 ` Tejun Heo
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=4B413CB8.1050808@kernel.org \
--to=tj@kernel.org \
--cc=HWerner4@gmx.de \
--cc=greg@kroah.com \
--cc=hancockrwd@gmail.com \
--cc=js@sig21.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmalygin@ked.de \
--cc=trenn@suse.de \
/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