All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: jeanseb <jeanseb.valette@free.fr>, Tejun Heo <tj@kernel.org>
Cc: 585556@bugs.debian.org, linux-ide@vger.kernel.org
Subject: Re: More ata_piix spurious IRQs
Date: Sat, 12 Jun 2010 21:38:46 +0100	[thread overview]
Message-ID: <1276375126.14011.199.camel@localhost> (raw)
In-Reply-To: <20100612194944.750682d7@server.gazypan.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

Le Sat, 12 Jun 2010 19:33:09 +0200,
Tejun Heo <tj@kernel.org> a écrit :

> Hello, Ben.
> 
> On 06/12/2010 01:13 AM, Ben Hutchings wrote:
> > (more details at <http://bugs.debian.org/585556>).
> > 
> > This is in Debian kernel version 2.6.32-15 which is based on stable
> > version 2.6.32.14 but has your backported spurious IRQ handling
> > patch taken from SLE11 (References: bnc#445872, bnc#589449).  Any
> > idea what's going wrong here?  Is there a piece missing from that
> > fix?
> 
> One great thing about traditional IDE is that the IRQ line is not
> really under the control of the controller so the device can assert
> the IRQ whether the controller want or not and there's nothing much
> the driver can do to prevent runaway IRQs if the device is crazy
> enough (some devices seem to have problem with toggling nIEN for
> example).  Ain't it just great?  :-)

I didn't realise that.  Of course it should be obvious, given that PATA
is based on extension of the ISA bus.

> As the spurious interrupt handling kicked in, the spurious interrupts
> itself shouldn't cause problem.  It would be polling now, so it's
> likely that the device is asserting interrupt and not responding to
> commands properly.  Does the drive work in other environments?
> e.g. Can the BIOS d  it and boot from it?

On Sat, 2010-06-12 at 19:49 +0200, jeanseb wrote:
> Hi,
> the Drive is recognizes by bios and works (fine enough to install
> debian).
 
But you originally complained that it was responding slowly.

It seems like this is really a hardware bug.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      parent reply	other threads:[~2010-06-12 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100611222746.37b5efa6@server.gazypan.dyndns.org>
2010-06-11 23:13 ` More ata_piix spurious IRQs Ben Hutchings
2010-06-12 17:33   ` Tejun Heo
2010-06-12 17:49     ` jeanseb
2010-06-12 19:06       ` Bug#585556: " maximilian attems
2010-06-12 20:38       ` Ben Hutchings [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=1276375126.14011.199.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=585556@bugs.debian.org \
    --cc=jeanseb.valette@free.fr \
    --cc=linux-ide@vger.kernel.org \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.