From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.39.2: usb kernel panic/oops: schedule+ehci_irq+0x266/0x830
Date: Wed, 6 Jul 2011 16:14:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1107061614140.25497@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1107061040510.1995-100000@iolanthe.rowland.org>
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.
next prev parent reply other threads:[~2011-07-06 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 21:51 Justin Piszcz
2011-07-06 8:15 ` Justin Piszcz
2011-07-06 13:46 ` Justin Piszcz
2011-07-06 14:41 ` Alan Stern
2011-07-06 20:14 ` Justin Piszcz [this message]
2011-07-06 20:38 ` Alan Stern
2011-07-06 14:40 ` Alan Stern
2011-07-06 20:14 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1107061614140.25497@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®