linux-kernel - Re: 2.6.39.2: usb kernel panic/oops: schedule+ehci

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] [day] [month] [year] [list]

Date:	Wed, 6 Jul 2011 16:38:28 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
cc:	linux-kernel@...r.kernel.org, <linux-usb@...r.kernel.org>,
	Alan Piszcz <ap@...arrain.com>
Subject: Re: 2.6.39.2: usb kernel panic/oops: schedule+ehci_irq+0x266/0x830

On Wed, 6 Jul 2011, Justin Piszcz wrote:

> > ehci-hcd doesn't use threaded interrupts, so in theory that option
> > shouldn't make any difference.  Of course, theory isn't always right.
> >
> > Alan Stern
> >
> 
> Hi,
> 
> In that case I will leave it on w/ FRAME pointers enabled and we'll see 
> what happens.

Right.  It's always possible that the threaded IRQ code causes a bug
somewhere else in the kernel, and it just happens to show up
sporadically in ehci-hcd.  Having more information will help narrow 
this down.

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/