[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090727162044.GA9657@Pilar.aei.mpg.de>
Date: Mon, 27 Jul 2009 18:20:44 +0200
From: "Carlos R. Mafra" <crmafra2@...il.com>
To: Ferenc Wagner <wferi@...f.hu>
Cc: Alan Stern <stern@...land.harvard.edu>, Greg KH <greg@...ah.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
Kay Sievers <kay.sievers@...y.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [Bisected] [Bug #13821] Replugging USB serial converter uses
new device node
On Mon 27.Jul'09 at 17:53:18 +0200, Ferenc Wagner wrote:
> Alan Stern <stern@...land.harvard.edu> writes:
> >
> > Are you certain this really is a regression? Under 2.6.30 and 2.6.27
> > the same thing happened if I unplugged a USB serial device while it was
> > in use.
>
> My original report is about unplugging the USB servial device *after*
> using it.
Yes, I did this:
1) plug the surfstick
2) connect to the internert (with draknetcenter)
3) disconnect (and wait a bit)
4) unplug the surfstick (and wait a bit)
Then when I plug it again, the devices created are /dev/ttyUSB{1,2} instead
of /dev/ttyUSB{0,1}.
That breaks 'draknetcenter', because if I try to connect again it
says that /dev/ttyUSB0 can not be found.
And during the bisection, for the commits which were marked "good", there
was no problem to reconnect and 'draknetcenter' was happy (although perhaps
it should not be so dependent on /dev/tttyUSB0 only, but that is another
story).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists