linux-kernel - Re: Strange EHCI/OHCI IRQ and other PCI errors on boot with 2.6.32 (which 2.6.26 did not see) on Geode LX/CS5536.

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]

Date:	Wed, 20 Jan 2010 15:13:22 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
cc:	Kernel development list <linux-kernel@...r.kernel.org>,
	<linux-geode@...ts.infradead.org>,
	USB list <linux-usb@...r.kernel.org>,
	<linux-pci@...r.kernel.org>
Subject: Re: Strange EHCI/OHCI IRQ and other PCI errors on boot with 2.6.32
 (which 2.6.26 did not see) on Geode LX/CS5536.

On Wed, 20 Jan 2010, Lennart Sorensen wrote:

> On Wed, Jan 20, 2010 at 11:37:07AM -0500, Alan Stern wrote:
> > It's true that the USB controllers appear to be the only devices using
> > IRQ 5.  But your startup log shows that only two of the three
> > controllers have an associated driver.  Maybe the third controller is
> > generating the unwanted interrupts?
> 
> Could be.  But I never saw the problem with 2.6.26.  That's puzzling me.
> 
> Now I think the 3rd controller may be a client mode interface on the
> Geode LX, which I certainly don't use if it has such a thing.
> 
> I know what EHCI and OHCI mean.  I don't know what UDC is.  I see mention
> of UDC under USB gadget support.  I will try enabling that driver and
> see what it does.

"UDC" stands for "USB Device Controller".  It is for use in device
mode, as opposed to host mode (i.e., you could plug that controller
into a regular PC and then use the Geode as a USB peripheral).

It's possible that some change in the PCI setup is allowing that 
controller to generate interrupts whereas before it didn't.  Or this 
could be a total red herring.

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/