linux-kernel - Re: 3.4.4: disabling irq

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.1211201112360.1692-100000@iolanthe.rowland.org>
Date:	Tue, 20 Nov 2012 11:14:27 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Udo van den Heuvel <udovdh@...all.nl>
cc:	linux-usb@...r.kernel.org,
	Jan Ceuleers <jan.ceuleers@...puter.org>,
	Clemens Ladisch <clemens@...isch.de>,
	Simon Jones <sijones2010@...il.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: 3.4.4: disabling irq

On Tue, 20 Nov 2012, Udo van den Heuvel wrote:

> > Secondly, try building a kernel with the patch below and 
> > CONFIG_USB_DEBUG enabled.  Let's see what the dmesg log says when the 
> > problem occurs.
> 
> I just booted into 3.6.7 with the patch:
> 
> # dmesg|sort|uniq
> ohci_hcd 0000:00:12.0: IRQ: 24 8000005a
> ohci_hcd 0000:00:14.5: IRQ: 24 8000005a
> #
> 
> So what does this mean?
> I did not get the `disabling irq` yet.

It means your system was working normally.  Which you already knew, 
because the IRQ didn't get disabled.

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/