On Tue, 5 Jul 2011, Justin Piszcz wrote:Done, I'll update when I have a new crash, thank you for the suggestion!
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.
I was wondering if it could be HW related, even though I cannot seem to findIs this a valid kernel bug?
What's the difference between a "valid" kernel bug and an "invalid"
kernel bug? :-)
I wish it was, I tried above (30+ USB devices) no crash, its more or less
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.