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

Message-ID: <alpine.DEB.2.02.1107061614140.25497@p34.internal.lan>
Date:	Wed, 6 Jul 2011 16:14:25 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Alan Stern <stern@...land.harvard.edu>
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, Alan Stern wrote:

> On Wed, 6 Jul 2011, Justin Piszcz wrote:
>
>> On Wed, 6 Jul 2011, Justin Piszcz wrote:
>>
>>>
>>>
>>> On Tue, 5 Jul 2011, Justin Piszcz wrote:
>>>
>>>> Hi,
>>>>
>>>> I plan to build a new machine in the future (one with console access) but
>>>> in the meantime, after my PSU replacement, the host is still having issues,
>>>> I've turned off bluetooth wireless (built into the DP55KG) and will see if
>>>> it panics again, link the latest panic/oops/etc:
>>>>
>>
>> When it recurs, I will disable the 'threadirq' boot option with 2.6.39, as
>> that is when all this started happening and report back if it happens without
>> this option enabled.
>>
>> Is there a reason why threadirq would cause weird issues on one HW type
>> chipset vs. another (both Intel)?
>
> 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.

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