On Fri, Mar 16, 2012 at 05:45:14PM +0800, Ken Huang wrote: > 2012/3/15 Johan Hovold <jhovold@xxxxxxxxx> > > > > > > Please try the above with 3.2.11. > > > > > > > It can be reproduced with 3.2.11, but I just don't know how to capture the > > > crash message, > > > cause system has no response when the oops shows. > > > So how can I capture this oops message? > > > > Can you take a photo of the screen with the oops message and its > > backtrace? (Otherwise, just write down the backtrace by hand.) > > > > Other options could be to set up a serial or net console but you > > need another host for that. > > > > Did you say that the oops didn't occur until you unplug the device > > again? > > > > Thanks, > > Johan > > > >Did you say that the oops didn't occur until you unplug the device > >again? > No, I run my test program and plug modem, oops shows immediately. > And I can reproduce it every time with these two steps. > > Here is the oops info from dmesg: Thanks for your detailed description of the problem. I'm able to reproduce the bug here. Turns out there is a race in usb-serial core between open and probe. I'll respond to this mail with a patch that should fix it. Care to give it a try? Thanks, Johan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
