linux-kernel - Re: Nobody cared about IRQs at shutdown

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1011251056530.22247-100000@netrider.rowland.org>
Date:	Thu, 25 Nov 2010 11:06:02 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Alexander E. Patrakov" <patrakov@...il.com>
cc:	linux-kernel@...r.kernel.org, <linux-usb@...r.kernel.org>
Subject: Re: Nobody cared about IRQs at shutdown

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?

> linux-usb) at shutdown. Also, instead of shutting down immediately, the 
> kernel started waiting for something to time out (and after the timeout, 
> it does power off the computer). Adding the "irqpoll" parameter does 
> work around the issue. A screen photo illustrating the problem and the 
> kernel config are attached.
> 
> I didn't try to bisect because there is no known good kernel. I.e., the 
> issue doesn't exist without systemd, and I didn't run systemd with 
> earlier kernels.
> 
> Please help diagnosing and, if possible, fixing this problem.
> 
> The broken image at the top of the screen is from extlinux (I use it to 
> boot the kernel because I don't like grub).

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.

Do you have any USB devices attached to bus 3 or bus 6?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/