[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0908101114320.3208-100000@iolanthe.rowland.org>
Date: Mon, 10 Aug 2009 11:18:29 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Bruno Prémont <bonbons@...ux-vserver.org>
cc: Greg Kroah-Hartman <gregkh@...e.de>,
<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 2.6.31-rc5 regression: Oops when USB Serial disconnected while
in use
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists