From: Greg KH <gregkh@suse.de>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Greg KH <greg@kroah.com>, Alan Stern <stern@rowland.harvard.edu>,
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: Tue, 18 Aug 2009 15:36:48 -0700 [thread overview]
Message-ID: <20090818223648.GA25659@suse.de> (raw)
In-Reply-To: <20090818190016.73ce53de@neptune.home>
On Tue, Aug 18, 2009 at 07:00:16PM +0200, Bruno Prémont wrote:
> Hi Greg,
>
> Were you able to reproduce this with a FTDI usbserial device?
No, I can't find one in my box. I'll go dig in the attic next to try to
find on, I knew I had one before...
> I just had a short look with 2.6.31-rc6, it crashes harder... once
> kernel did panic with general protection fault after reporting
> tty_port_close_start: count=-1
> The second time id started output of an Oops but only half of the first
> line ever showed up on screen (Intel KMS).
>
> Note: this was with just usbserial.ko and ftdi_sio.ko rebuilt with
> CONFIG_DEBUG_INFO=y in the hope to find out what did access a bad
> pointer. (make CONFIG_DEBUG_INFO=y drivers/usb/serial/$module.ko)
>
> Will retry now with a fresh compile with CONFIG_DEBUG_INFO enabled for
> whole kernel and see if I can get better information, eventually
> switching to vesa framebuffer in case the partial output happens again.
>
> This pretty much looks like unbalanced ref-count...
Yeah, it sounds like it. More info would be great to have if you can
get it.
thanks,
greg k-h
next prev parent reply other threads:[~2009-08-18 22:38 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
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 [this message]
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=20090818223648.GA25659@suse.de \
--to=gregkh@suse.de \
--cc=bonbons@linux-vserver.org \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox