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]

Message-ID: <Pine.LNX.4.44L0.1001202043540.3608-100000@netrider.rowland.org>
Date:	Wed, 20 Jan 2010 20:52:03 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
cc:	linux-kernel@...r.kernel.org, <linux-geode@...ts.infradead.org>,
	<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:

> > > If I boot with 'irqpoll' then everything seems fine.
> > > 
> > > Any idea how I can figure out why irqpoll makes it happy?  Does it give
> > > any reports anywhere about misrouted irqs?
> > 
> > Not that I know of.
> 
> That's unfortunate.  After all it would be nice if irqpoll found an
> unhandled irq and called all the other handlers and the irq went away,
> then a report of which handler cleared it would be very helpful.

You could try changing the set of drivers loaded in memory.  For 
example, after booting with irqpoll you can unload ehci-hcd plus some 
other driver, and then load ehci-hcd again.  If the IRQ storm occurs 
then you'll know where to look.

> > Does 2.6.26 fail on the new machine?
> 
> Yes.
> 
> As far as I can tell some machines don't see the problem.  I am still
> investigating that.

Same kernel, initramfs, and everything else?

> > Are you using a .config different from the one that used to work with 
> > 2.6.26?
> 
> Well of course, but not for the USB settings.  It is supposed to be the
> same as far as possible.  I will go compare them in more detail.

What I meant was: Is your current 2.6.26 still built using the same 
.config as the old 2.6.26 which used to work okay?

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/