All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	gregkh@suse.de, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: WARNINGs in usb-serial.c
Date: Fri, 4 Sep 2009 16:48:24 +0100	[thread overview]
Message-ID: <20090904164824.391876b3@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0909041014490.3008-100000@iolanthe.rowland.org>

On Fri, 4 Sep 2009 10:17:30 -0400 (EDT)
Alan Stern <stern@rowland.harvard.edu> wrote:

> On Fri, 4 Sep 2009, Miklos Szeredi wrote:
> 
> > On Thu, 3 Sep 2009, Greg KH wrote:
> > > On Thu, Sep 03, 2009 at 04:13:34PM +0200, Miklos Szeredi wrote:
> > > > I get the following warnings in 2.6.31-rc.  A lot of them:
> > > > 
> > > > WARNING: at drivers/usb/serial/usb-serial.c:414
> > > > serial_write_room+0x59/0x6e [usbserial]() WARNING: at
> > > > drivers/usb/serial/usb-serial.c:401 serial_write+0x77/0x9d
> > > > [usbserial]()
> > > > 
> > > > This is a huawei-3565 modem.
> > > > 
> > > > The messages don't seem to hurt, but there's lot of trouble
> > > > with this gadget.  Sometimes it just doesn't work after a while
> > > > and a reboot is needed.  Sometimes it hangs the kernel after
> > > > suspend, etc.  Not sure if this is related to the warnings...
> > > 
> > > {sigh}
> > > 
> > > The tty layer changes are being a pain here :(
> > > 
> > > Alan Stern posted a set of patches to the linux-usb list to
> > > hopefully address stuff like this, is there any way you could
> > > test them out to see if they help or not?
> > 
> > Nope, it doesn't seem to help.  Still got the same warnings with the
> > patched kernel (latest git + ghk tree + usbserial patches).
> 
> What were you doing when these warnings appeared?

The usual way to get it was

	close
		users = 0
		ldisc processing
		echo
		write room
			hey we are closed
				Spew

I suspect the actual check in write_room is now simply bogus with it
all being refcounted (the ldisc will hold a tty kref at that point)

  reply	other threads:[~2009-09-04 14:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1MjD4A-0002wi-KL@pomaz-ex.szeredi.hu>
2009-09-03 18:36 ` WARNINGs in usb-serial.c Greg KH
2009-09-03 21:24   ` Rafael J. Wysocki
2009-09-03 21:43     ` Greg KH
2009-09-04 15:46       ` Alan Cox
2009-09-04  8:09   ` Miklos Szeredi
2009-09-04 14:17     ` Alan Stern
2009-09-04 15:48       ` Alan Cox [this message]
2009-09-04 15:12         ` Alan Stern
2009-09-07 11:14           ` Miklos Szeredi
2009-09-07 15:08             ` Alan Stern
2009-09-07 17:50               ` Miklos Szeredi
2009-09-07 19:25                 ` Alan Stern
2009-09-07 20:09                   ` Miklos Szeredi
2009-09-08  1:43                     ` Alan Stern
2009-09-08  8:01                       ` Miklos Szeredi

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=20090904164824.391876b3@linux.intel.com \
    --to=alan@linux.intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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.