public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Bongani Hlope <bonganilinux@mweb.co.za>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: irq 21: nobody cared 2.6.24-rc1
Date: Wed, 07 Nov 2007 14:18:42 -0500	[thread overview]
Message-ID: <47320F92.3060108@rtr.ca> (raw)
In-Reply-To: <200711020133.28907.bonganilinux@mweb.co.za>

Bongani Hlope wrote:
> On Thursday 01 November 2007 22:32:38 Andrew Morton wrote:
>> On Thu, 25 Oct 2007 10:45:36 +0200
>>
>> Bongani Hlope <bonganilinux@mweb.co.za> wrote:
>>> Booting with irqpoll works
>>>
>>> ls /proc/irq/21/ (with irqpoll)
>>> ehci_hcd:usb1/  smp_affinity  uhci_hcd:usb2/  uhci_hcd:usb3/ 
>>> uhci_hcd:usb4/
>>>
>>>  Disabling IRQ #21
>> Was any earlier kernel version OK?  2.6.23?
> 
> Yes the 2.6.23 kernel works fine. This seems to happen when I boot the 
> 2.6.24-rc1 kernel with an iPod attached (hope this helps), but the 2.6.23 
> kernel doesn't experience this problem.
..

Something in 2.6.24-rc* seems to be a lot more fussy about this kind
of situation than in 2.6.23.   I have a driver (sata_qstor) that manages
a piece of hardware that unfortunately generates spurious interrupts
regularly.

With 2.6.23, it was only rarely bad enough to cause the "Disabling IRQ #nn"
event to occur.  But in 2.6.24-rc*, it happens almost immediately now
(so, yes, I've gone and put a workaround into the driver for it).

Something's different.

      reply	other threads:[~2007-11-07 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  8:45 irq 21: nobody cared 2.6.24-rc1 Bongani Hlope
2007-11-01 20:32 ` Andrew Morton
2007-11-01 21:25   ` Theodore Tso
2007-11-01 23:33   ` Bongani Hlope
2007-11-07 19:18     ` Mark Lord [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=47320F92.3060108@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@linux-foundation.org \
    --cc=bonganilinux@mweb.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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