Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> writes: >>> Another thing to check is whether this patch (not yet merged) fixes it: >>> >>> http://marc.info/?l=linux-usb&m=124825571403844&w=2 >> >> No, unfortunately it does not fix it. I've just tested it. > > I wouldn't expect it to. > > In the ppp case you have this occuring on an unplug > > USB layer > unplug > hangup tty > PPPD > SIGHUP > ouch > log stuff > close down > > However at the same time that PPPD is logging stuff and closing down th > USB layer is going to see the replug if you just unplug/replug quickly > and in that case you will get ttyUSB1. That aspect is timing dependant. Looks like there's some misunderstanding here. Let's try to straighten it out! This report is not about yanking the device while pppd is happily using it. It's about yanking the device *after* pppd was fully shut down via poff. > If everything has closed down and given the port back before you replug > it you should get ttyUSB0 again. Yes. I'm not sure how to check whether "everything has closed down and gived the port back", but pppd is definitely not in the process list when I replug. Still I don't get the same minor number again. As Alan Stern suggests, it has nothing to do with pppd specifically. I'll also check that in a couple of hours. -- Regards, Feri. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
