On Wed, Jun 25, 2008 at 01:00:22PM +0200, Helge Hafting wrote:
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
--