From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 16 Mar 2007 14:59:29 +0000 Subject: Re: udev or kernel broken with rsdl 0.30 patch Message-Id: <1174057169.21549.82.camel@lov.localdomain> List-Id: References: <20070315104654.19025CA4097@mx1.ciphirelabs.net> In-Reply-To: <20070315104654.19025CA4097@mx1.ciphirelabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Fri, 2007-03-16 at 15:39 +0100, Andreas Jellinghaus wrote: > Ok, thanks for the udev rules fixes. >=20 > but with all rules fixes I still have the issue: openct not started with = the=20 > rsdl patched kernel.=20 >=20 > My guess is the temp. success was only because udevd debugging and the > wrong rules slowed udevd down and thus evaded the race problem. >=20 > Please let me know if I can be of any further help, like testing more con= fig=20 > options or testing patches or anything like that.=20 Hmm, if it's a timing issue we should be able to fix it with WAIT_FOR_SYSFS. What does: udevtest /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1.3/4-1.3:1.0 for the interface (the one with the ":") say to WAIT_FOR_SYSFS? It finds the attributes, and says it would run your program? It does not work on device plug-in, does it work if you write "add" to the "uevent"-file of the device in sysfs? Does adding PROGRAM=3D"/bin/sleep 1" make a difference? Kay ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ 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