On Mon, Aug 10, 2009 at 07:18:22PM +0200, Bruno Prémont wrote: > On Mon, 10 August 2009 Greg KH <greg@xxxxxxxxx> wrote: > > On Mon, Aug 10, 2009 at 11:18:29AM -0400, Alan Stern wrote: > > > On Sat, 8 Aug 2009, Bruno Prémont wrote: > > > > > > > I tried bisecting this but bisect did end up on a fully unrelated > > > > commit (which is not even being compiled into my kernel). > > > > Possibly the failed bisect could be related to mis-classified > > > > kernel panic/hang while pulling the USB cable (there were two > > > > such panics for the whole iteration)? > > > > > > > > There are quite a few patches touching tty, ttyUSB and friends > > > > between rc4 and now so pretty hard to guess on the correct one. > > > > > > > > The oops always happens when I disconnect the USB serial console > > > > (here the one built into Marvell SheevaPlug) while having minicom > > > > connected to it. > > > > During the bisection for the last few bad iterations minicom got > > > > killed (segfault), the bad ones on the iteration left a minicom > > > > zombie in 'D' state. Ok, a few questions. Are you pulling the device out when you have a console attached to the device, or just a "normal" minicom connection with it? I can't seem to duplicate this here at the moment for some reason :( thanks, greg k-h -- 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
