From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrien Beau Date: Fri, 20 Jun 2003 18:44:27 +0000 Subject: Re: Hotplug bug in Linux 2.4.21? Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Friday 20 June 2003 19:51, Greg KH wrote: > > On Fri, Jun 20, 2003 at 07:25:59PM +0200, Adrien Beau wrote: > > three connection events were fired when the modem was detected > > (...). When I disconnected it, my remover was launched three > > times, simultaneously. > > Yes, we now call /sbin/hotplug for ever interface of a USB > device, instead of just once. I've talked to the speedtouch > kernel driver's author a bunch about this, and he says that he > has a updated hotplug script to properly handle this. To which Duncan Sands quickly replied: > > Actually I said that it was a pain to write such a script in 2.4 > because there is no easy way to get the interface number. Okay. I guess that if we had that, we could easily react to only one of the events, and ignore the others. Meanwhile, it seems like my lockfile approach is the better answer to the issue, if only there wasn't this strange behavior. If you want to have a look at it, have put my script there: http://adrien.beau.free.fr/slackware/hotplug/speedtouch http://adrien.beau.free.fr/slackware/hotplug/speedtouch.usermap http://adrien.beau.free.fr/slackware/hotplug/speedtouch.log It is intended to work with the *usermode* SpeedTouch driver, and should of course be put under /etc/hotplug/usb. The logfile might interest you, too. So, if anybody can help finding why: * When everything works fine, a second instance of the script is launched approximately seven seconds after the first one. It looks like there's a timeout somewhere. Look at the logfile entries on June 17th for a typical occurence of the problem. This only happens at boot time. Hotplugging works (worked) fine. * When two instances of the script are run at a few seconds interval, the lockfile mechanism works fine (again, see for example June 17th), but when three instances run at the same time, the mechanism fails in an impossible manner (see the log entries starting on June 20th, at 12:15pm for the first occurence of this, and see the entries at 12:55:55pm for an occurence with the timestamps printed in the logs). ... I would be very grateful. > Hope this helps, Well, sure, now I know on what problem to work. :-) -- adrien.beau@free.fr - http://adrien.beau.free.fr/ ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel