All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org
Subject: Re: 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead
Date: Wed, 25 Jun 2008 22:39:59 -0700	[thread overview]
Message-ID: <20080626053959.GA25731@kroah.com> (raw)
In-Reply-To: <48622546.6070505@aitel.hist.no>

On Wed, Jun 25, 2008 at 01:00:22PM +0200, Helge Hafting wrote:

> The problem is triggered by bending the USB cable - likely a cable fault. 
> Sometimes I merely get a plain USB device disconnect. (This also
> aborts my gps logging as the gps tend to reconnect to /dev/ttyUSB1 instead 
> of /dev/ttyUSB0, but I guess that is a userland issue, not a kernel 
> problem. Or is this a race condition?)

That is because your userspace program still has ttyUSB0 open, so it
creates the next valid device, ttyUSB1.  There is no way to connect the
new device to the old one as it has no idea it should do so.

Flaky hardware connections are not nice on drivers at times, although we
should not be crashing :)

We are probably just not handling the fact that the device is still open
properly, although I thought all of those errors were long since fixed,
perhaps the tty layer changes are now showing other inadequacies of the
usb-serial core up...

Those debug logs would be most helpful in tracking this down.

thanks,

greg k-h

  reply	other threads:[~2008-06-26  5:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 18:22 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead Helge Hafting
2008-06-22 18:42 ` Greg KH
2008-06-23  4:01   ` Andrew Morton
2008-06-25 11:00     ` Helge Hafting
2008-06-26  5:39       ` Greg KH [this message]
2008-06-25 11:30   ` Helge Hafting
2008-07-02 21:18     ` Greg KH

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=20080626053959.GA25731@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.