On Sat, 8 Aug 2009, Bruno [UTF-8] 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. By the way, there are quite a few serial patches in Greg KH's tree. At least one of them looks like it is meant to fix exactly this problem. Can you try running with http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-all-2.6.31-rc5.patch applied to the standard 2.6.31-rc5 source? Alan Stern -- 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
