From: Greg KH <greg@kroah.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.31-rc5 regression: Oops when USB Serial disconnected while in use
Date: Mon, 10 Aug 2009 11:13:06 -0700 [thread overview]
Message-ID: <20090810181306.GA24989@kroah.com> (raw)
In-Reply-To: <20090810191822.26370810@neptune.home>
On Mon, Aug 10, 2009 at 07:18:22PM +0200, Bruno Prémont wrote:
> On Mon, 10 August 2009 Greg KH <greg@kroah.com> 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
next prev parent reply other threads:[~2009-08-10 18:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 17:47 2.6.31-rc5 regression: Oops when USB Serial disconnected while in use Bruno Prémont
2009-08-09 14:02 ` Ozan Çağlayan
2009-08-09 15:00 ` Alan Stern
2009-08-10 15:18 ` Alan Stern
2009-08-10 15:44 ` Greg KH
2009-08-10 17:18 ` Bruno Prémont
2009-08-10 18:13 ` Greg KH [this message]
2009-08-10 18:35 ` Bruno Prémont
2009-08-10 18:51 ` Bruno Prémont
2009-08-10 19:29 ` Greg KH
2009-08-18 17:00 ` Bruno Prémont
2009-08-18 22:36 ` Greg KH
2009-08-18 23:16 ` Greg KH
2009-08-19 17:22 ` Bruno Prémont
2009-08-19 18:20 ` Alan Stern
2009-08-19 20:15 ` Bruno Prémont
2009-08-19 21:01 ` Alan Stern
2009-08-19 21:50 ` Alan Cox
2009-08-19 22:44 ` Alan Stern
2009-08-20 19:25 ` Bruno Prémont
2009-08-20 21:20 ` Alan Stern
2009-08-21 9:25 ` Bruno Prémont
2009-08-21 15:43 ` Alan Stern
2009-08-21 15:48 ` Alan Cox
2009-08-21 17:39 ` Alan Stern
2009-08-21 18:42 ` Alan Cox
2009-08-21 20:52 ` Alan Stern
2009-08-21 23:16 ` Alan Cox
2009-08-22 2:30 ` Alan Stern
2009-08-23 2:51 ` Alan Stern
2009-08-23 16:15 ` Alan Stern
2009-08-23 16:30 ` Bruno Prémont
2009-08-24 1:24 ` Alan Stern
2009-08-24 20:15 ` Bruno Prémont
2009-08-25 1:42 ` Alan Stern
2009-08-25 20:19 ` Bruno Prémont
2009-08-25 23:42 ` Alan Stern
2009-08-26 20:32 ` Bruno Prémont
2009-08-27 2:19 ` Alan Stern
2009-08-21 16:50 ` Bruno Prémont
2009-08-20 21:58 ` Alan Cox
2009-08-21 14:02 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090810181306.GA24989@kroah.com \
--to=greg@kroah.com \
--cc=bonbons@linux-vserver.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.