linux-kernel - Re: 3.4.4: disabling irq

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.1207151122050.25880-100000@netrider.rowland.org>
Date:	Sun, 15 Jul 2012 11:35:35 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Udo van den Heuvel <udovdh@...all.nl>
cc:	linux-usb@...r.kernel.org,
	Jan Ceuleers <jan.ceuleers@...puter.org>,
	Clemens Ladisch <clemens@...isch.de>,
	Simon Jones <sijones2010@...il.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: 3.4.4: disabling irq

On Sun, 15 Jul 2012, Udo van den Heuvel wrote:

> > The conclusion is that ohci-hcd is the only driver using IRQ 18.  If 
> > you build a kernel with CONFIG_USB_DEBUG enabled, it will be possible 
> > to see if the OHCI hardware is responsible for the IRQ problem.
> > 
> > When the IRQ line gets disabled again, make a copy of the
> > 
> > 	/sys/kernel/debug/usb/ohci/*/registers
> > 
> > files and post them, along with a copy of 
> > /sys/kernel/debug/usb/devices.

> After disabling:

This indicates the controller at 0000:00:13.1 has an outstanding 
interrupt request:

> bus pci, device 0000:00:13.1
> OHCI Host Controller
> ohci_hcd
> OHCI 1.0, NO legacy support registers, rh state running
> control 0x08f HCFS=operational IE PLE CBSR=3
> cmdstatus 0x00000 SOC=0
> intrstatus 0x00000026 FNO SF WDH
> intrenable 0x8000005a MIE RHSC UE RD WDH

The WDH bit is set in both intrstatus and intrenable.  None of the 
other controllers show anything similar.  Therefore, in the absence of 
hardware bugs, this controller must be the one causing your problem.

You can test this by unbinding that controller from the ohci-hcd 
driver:

	echo 0000:00:13.1 >/sys/bus/pci/drivers/ohci_hcd/unbind

Do this before the IRQ error occurs, and see if you get another error.
If you do, get another copy of those "register" files as quickly
afterwards as you can.

That's the controller for bus 4, which has one of the webcams.  If you 
prefer, you could simply unplug the webcam from bus 4 instead; the end 
result should be the same.  (Or even unplug both webcams...)

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/