public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 07:59:59 +0900	[thread overview]
Message-ID: <4B41216F.4070906@kernel.org> (raw)
In-Reply-To: <20100103221142.GA16783@sig21.net>

Hello,

On 01/04/2010 07:11 AM, Johannes Stezenbach wrote:
> On Wed, Dec 30, 2009 at 01:04:28PM +0100, Hans Werner wrote:
>>
>> testing in the Arch Linux Forums has shown that if one applies
>> a patch which you posted to the linux-ide ML on 2008-11-21
>> then the problem is no longer seen. Instead the kernel log shows
>> that a spurious IRQ was cleared.
>>
>> [PATCH #upstraem-fixes] ata_piix: detect and clear spurious IRQs
>> http://marc.info/?l=linux-ide&m=122724081603679&w=2
>> http://bbs.archlinux.org/viewtopic.php?id=86454
>>
>> What's the current status of this patch? Is it safe to use?
>> What does it tell us about the Samsung N130/140?
> 
> FWIW, I just tested a current git kernel (v2.6.33-rc2-268-g45d28b0)
> with Tejun's patch applied on my N130.  The ATA exception and hang is
> indeed gone, just "ata1: clearing spurious IRQ" is logged.
> 
> I've see Tejun's comment in
> http://bugzilla.kernel.org/show_bug.cgi?id=14314
> and I would like to add that the ATA irq is not shared.
> 
>  14:      43885          0   IO-APIC-edge      ata_piix
>  15:          0          0   IO-APIC-edge      ata_piix

Can you please post that on bug#14314?  If the IRQ line indeed wasn't
shared, it might mean that the controller raised the IRQ line before
getting its internal state in order and the IRQ checking sequence
cleared the external IRQ status while leaving the internal pending bit
intact, which I've never heard of on piix and don't think is possible.
Hmmmm... given that the problem was dependent on BIOS on the other
model (is it the N130?), maybe the BIOS is doing something funny.  :-(
Anyways, please post full output of "cat /proc/interrupts" at the bz.

Thanks.

-- 
tejun

  reply	other threads:[~2010-01-03 22:58 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 [this message]
2010-01-04  0:41     ` Johannes Stezenbach
2010-01-04  0:56       ` Tejun Heo
  -- 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=4B41216F.4070906@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