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:13 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1107061611520.25497@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1107061036190.1995-100000@iolanthe.rowland.org>
On Wed, 6 Jul 2011, Alan Stern wrote:
> On Tue, 5 Jul 2011, Justin Piszcz wrote:
>
> You need to enable CONFIG_FRAME_POINTER; without that it is difficult
> to interpret the stack dump. Also you should collect more than a
> single screen's worth of information, say by using a serial console or
> netconsole.
Done, I'll update when I have a new crash, thank you for the suggestion!
>> Is this a valid kernel bug?
>
> What's the difference between a "valid" kernel bug and an "invalid"
> kernel bug? :-)
I was wondering if it could be HW related, even though I cannot seem to find
any HW fault. Example, I attached 30+ USB devices as a test, R/W on all of
the flash and hard drives, no problems, this seems to occur spuriously when
little or no activity is occurring, hopefully w/FRAME POINTERS we will
get something useful next time.
>
> Yes, clearly it is a bug in the kernel.
>
>
> This could any of a number of things. More information is needed.
>
> If the problem is easily reproducible, you can use git bisect to pin
> down the commit responsible for exposing the bug.
I wish it was, I tried above (30+ USB devices) no crash, its more or less
random, will wait for next crash and upadte then.
Thanks for the response.
Justin.
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
2011-07-06 20:38 ` Alan Stern
2011-07-06 14:40 ` Alan Stern
2011-07-06 20:14 ` Justin Piszcz [this message]
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.1107061611520.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®