linux-kernel - Re: Problem: irq 217: nobody cared + backtrace

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.0608051042090.25249-100000@netrider.rowland.org>
Date:	Sat, 5 Aug 2006 10:48:33 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Jesper Juhl <jesper.juhl@...il.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	<linux-usb-devel@...ts.sourceforge.net>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: Problem: irq 217: nobody cared + backtrace

On Sat, 5 Aug 2006, Jesper Juhl wrote:

> > Just as before.
> >
> > I can't tell you what's causing this to happen, except that it appears to
> > be some sort of hardware problem.
> 
> Hmm, the odd thing is that there are no USB devices connected at all.

My guess is that this has nothing to do with the USB controller, other 
than the fact that IRQ 217 is enabled because the controller uses it.  
Probably the real problem, the unhandled interrupt requests, comes from 
some other device entirely.

> >  Since it doesn't seem to cause any harm
> > you could just live with it.
> >
> > Or, if you're not using any full-speed or low-speed USB devices, you could
> > simply prevent uhci-hcd from loading at all.  Then IRQ 217 wouldn't get
> > enabled in the first place.
> >
> True, that just seems like a hack...

It is.  Without knowing the underlying cause of the problem, it's the best 
I can suggest.

If you compare /proc/interrupts with earlier versions of the kernel (where 
the problem doesn't occur), does it look the same?

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/