linux-kernel - Re: [Bug #11552] Disabling IRQ #23

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:	Mon, 22 Sep 2008 06:53:46 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Justin Mattock <justinmattock@...il.com>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	David Brownell <david-b@...bell.net>
Subject: Re: [Bug #11552] Disabling IRQ #23

On Sun, 21 Sep 2008, Justin Mattock wrote:

> From over here, I did a bad install
> of isight-firmware-tools, causing hal and udev
> to clash.  After making sure the package was either
> using hal or udev, there is no message of disable irq #23.
> If its not too much trouble is there a way to verify that this was
> the case, i.g. if udev creates a dev, then hal creates the same device
> will this cause ehci_hcd to have messages of this kind? If so
> then thats what happened, if not then theres something else causing this.

You didn't read what I wrote earlier, did you?  The "HC died" message 
should NEVER occur!  It doesn't matter what games you play with hal and 
udev -- it should NEVER occur.  Not ever.

And since the "HC died" is what causes IRQ #23 to be disabled, that 
shouldn't happen either.

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/