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:	Sun, 21 Sep 2008 16:16:42 -0700
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Kernel Testers List" <kernel-testers@...r.kernel.org>,
	"Alan Stern" <stern@...land.harvard.edu>,
	"David Brownell" <david-b@...bell.net>
Subject: Re: [Bug #11552] Disabling IRQ #23

On Sun, Sep 21, 2008 at 11:54 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=11552
> Subject         : Disabling IRQ #23
> Submitter       : Justin Mattock <justinmattock@...il.com>
> Date            : 2008-09-09 19:08 (13 days old)
> References      : http://marc.info/?l=linux-kernel&m=122098735230906&w=4
>                  http://marc.info/?l=linux-kernel&m=122107367715361&w=4
> Handled-By      : David Brownell <david-b@...bell.net>
>                  Alan Stern <stern@...land.harvard.edu>
> Patch           : http://marc.info/?l=linux-kernel&m=122187222705195&w=4
>
>
>

not sure if it should be;
>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.

-- 
Justin P. Mattock
--
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/