From: Greg KH <greg@kroah.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Instances of visor us devices are not deleted (2.6.9-rc4-mm1)
Date: Wed, 20 Oct 2004 00:00:56 -0700 [thread overview]
Message-ID: <20041020070056.GA15620@kroah.com> (raw)
In-Reply-To: <20041020061647.GA20692@gamma.logic.tuwien.ac.at>
On Wed, Oct 20, 2004 at 08:16:47AM +0200, Norbert Preining wrote:
> Hi USB developers!
>
> I have the following problem with 2.6.9-rc4-mm1 which includes bk-usb:
>
> Everytime I sync my palm I get a new device id:
>
> ...start sync...
> usb 4-2.1: new full speed USB device using address 8
> visor 4-2.1:1.0: Handspring Visor / Palm OS converter detected
> usb 4-2.1: Handspring Visor / Palm OS converter now attached to ttyUSB2
> usb 4-2.1: Handspring Visor / Palm OS converter now attached to ttyUSB3
> ...
> ...many usb usb2: string descriptor 0 read error: -113 ...
> ...
> ...end of sync...
> usb 4-2.1: USB disconnect, address 8
> visor 4-2.1:1.0: device disconnected
> visor ttyUSB3: visor_write - usb_submit_urb(write bulk) failed with status = -19
> ...new sync...
> usb 4-2.1: new full speed USB device using address 9
> visor 4-2.1:1.0: Handspring Visor / Palm OS converter detected
> usb 4-2.1: Handspring Visor / Palm OS converter now attached to ttyUSB4
> usb 4-2.1: Handspring Visor / Palm OS converter now attached to ttyUSB5
>
> etc etc.
>
> Is this a known problem?
Hm, no it isn't. Are you sure that userspace doesn't still have the
device nodes open? If they do, the ttyUSB number will not be released
until that happens.
thanks,
greg k-h
next prev parent reply other threads:[~2004-10-20 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 6:16 Instances of visor us devices are not deleted (2.6.9-rc4-mm1) Norbert Preining
2004-10-20 7:00 ` Greg KH [this message]
2004-10-20 11:18 ` Norbert Preining
2004-10-20 23:56 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 14:27 Kurt Wall
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=20041020070056.GA15620@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=preining@logic.at \
/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.