public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Nobody cared about IRQs at shutdown
Date: Sat, 27 Nov 2010 12:12:28 +0500	[thread overview]
Message-ID: <4CF0AF5C.6010003@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1011251522380.26094-100000@netrider.rowland.org>

26.11.2010 01:25, Alan Stern wrote:
> On Thu, 25 Nov 2010, Alexander E. Patrakov wrote:
>
>> 25.11.2010 21:06, Alan Stern wrote:
>>> On Thu, 25 Nov 2010, Alexander E. Patrakov wrote:
>>>
>>>> Hello.
>>>>
>>>> After switching my Gentoo desktop from sysvinit + openrc to systemd, I
>>>> started getting "nobody cared" messages about IRQs 16 and 19 (common
>>>> thing: they are assigned to the USB controllers, that's why CC:
>>> According to your listing, they are used by uhci-hcd.  Do the messages
>>> go away if you unload uhci-hcd before shutting down?
>> It is not a module here, so I have to recompile the kernel in order to
>> try this. Will do that tomorrow.
>>
>>> You may need to debug the uhci-hcd driver. Look into
>>> drivers/usb/host/uhci-hcd.c; the uhci_shutdown() routine ought to be
>>> called and it ought to call uhci_hc_died(), which in turn calls
>>> uhci_reset_hc() in pci-quirks.c, which is supposed to prevent the
>>> controller from generating any IRQs.
>> OK, tomorrow I will add some printks there.

Sorry, I didn't add them due to being busy with a different (non-kernel) 
bug. What do you want to know - just the fact that these functions are 
called before or after reporting the bad IRQ?

>>> Do you have any USB devices attached to bus 3 or bus 6?
>> Yes:
>>
>> Bus 006 Device 002: ID 05d8:4002 Ultima Electronics Corp. Artec Ultima
>> 2000 (GT6801 based)/Lifetec LT9385/ScanMagic 1200 UB Plus Scanner
>>
>> Should I unplug it and retest the bug now?
> Sure.

Tried, it didn't change anything.

> Even without rebuilding the kernel, you can unbind the uhci-hcd driver
> from the hardware by going to the /sys/bus/pci/drivers/uhci_hcd
> directory and doing:
>
> 	echo -n device-name>unbind
>
> where "device-name" is the name of one of the symlinks in that
> directory.

Thanks for the tip. Below are the updated test results, including the 
ones posted in my first mail, for completeness.

1. No irqpoll, no unbind: the system reports that nobody cared for IRQs, 
then waits, displays SATA errors, waits again, shuts down.

2. irqpoll, no unbind: the system shuts down without any delays.

3. No irqpoll, unbind uhci-hcd from everything it controls: the system 
reports bad IRQ 19 (consumed by firewire-ohci), waits, displays SATA 
errors, waits again, shuts down.

4. No irqpoll, unbind both uhci-hcd and firewire-ohci from everything: 
the system does not report any bad IRQs, waits, displays SATA errors, 
waits again, shuts down.

5. irqpoll, unbind both uhci-hcd and firewire-ohci from everything: same 
as (4).

I have no firewire devices.

-- 
Alexander E. Patrakov

  reply	other threads:[~2010-11-27  7:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 15:51 Nobody cared about IRQs at shutdown Alexander E. Patrakov
2010-11-25 16:06 ` Alan Stern
2010-11-25 16:14   ` Alexander E. Patrakov
2010-11-25 20:25     ` Alan Stern
2010-11-27  7:12       ` Alexander E. Patrakov [this message]
2010-11-27 15:16         ` Alan Stern
2010-11-30 18:08           ` Alexander E. Patrakov
2010-11-30 18:57             ` Alan Stern
2010-11-30 19:15               ` Alexander E. Patrakov
2010-12-01 14:59                 ` Alan Stern
2010-12-01 17:29                   ` Alexander E. Patrakov
2010-12-01 18:26                     ` Alan Stern

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=4CF0AF5C.6010003@gmail.com \
    --to=patrakov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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