Trouble with udevtrigger/udevsettle

Trouble with udevtrigger/udevsettle

[Logan Rathbone]

I'm getting udev set up on a relatively "from-scratch" machine, and I'm 
having a bit of trouble with something.  I'm using version 097, with the 
udevtrigger and udevsettle combo to get  the modules properly loaded for 
my coldplugged hardware, and it's working well, except for one thing:

in /dev/.udev/queue, I get a stray class@net@eth0@ that takes quite a 
while before it gets pushed into /dev/.udev/failed.  Thus I have to wait 
quite a while (about a minute or so) for udevsettle to complete and have 
my bootup continue.  Any ideas what this could be about?  My eth0 device 
itself is an onboard VIA ethernet controller whose module name is 
'via-rhine.'  I almost never use that particular card though, as I have 
a PCI card that I prefer to use.  I never really have a network cable 
plugged into the via-rhine, but I don't see why that would make a 
difference.

My kernel is a self-compiled vanilla kernel from kernel.org, version 
2.6.17.8

Any help resolving this would be greatly appreciated!
--Logan

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

Re: Trouble with udevtrigger/udevsettle

[Bryan Kadzban]

[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]

Oops, didn't send this to the list last time:

Bryan Kadzban wrote:
> Logan Rathbone wrote:
> 
>>Thus I have to wait quite a while (about a minute or so) for
>>udevsettle to complete and have my bootup continue.  Any ideas what
>>this could be about?
> 
> 
> Hmm...  Just guessing here, but:
> 
> 
>>I never really have a network cable plugged into the via-rhine, but I
>>don't see why that would make a difference.
> 
> 
> Your distro may have a rule set up to try to ifup the interface when it
> sees an add event for it.  If this ifup is trying to use DHCP, it *may*
> take a long time to fail when it can't find a DHCP server.  I seem to
> remember a 30-second timeout with dhcpcd in the past, which it waits for
> twice; that would match up with the one-minute timing you're seeing.
> 
> I would suspect that the DHCP client should to fail immediately if it
> doesn't detect a link, but I don't know for sure whether all of them do.
> 
> You might try blacklisting via-rhine in modprobe.conf.  That way you
> should never get an add event for eth0, and if the long delay is due to
> some rule that triggers from that, it shouldn't happen.

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]

[-- Attachment #2: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
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

Re: Trouble with udevtrigger/udevsettle

[Kay Sievers]

On Thu, 2006-09-21 at 07:08 -0400, Bryan Kadzban wrote:
> Oops, didn't send this to the list last time:
> 
> Bryan Kadzban wrote:
> > Logan Rathbone wrote:
> > 
> >>Thus I have to wait quite a while (about a minute or so) for
> >>udevsettle to complete and have my bootup continue.  Any ideas what
> >>this could be about?
> > 
> > 
> > Hmm...  Just guessing here, but:
> > 
> > 
> >>I never really have a network cable plugged into the via-rhine, but I
> >>don't see why that would make a difference.
> > 
> > 
> > Your distro may have a rule set up to try to ifup the interface when it
> > sees an add event for it.  If this ifup is trying to use DHCP, it *may*
> > take a long time to fail when it can't find a DHCP server.  I seem to
> > remember a 30-second timeout with dhcpcd in the past, which it waits for
> > twice; that would match up with the one-minute timing you're seeing.

You may try to run "udevtest /class/net/eth0" and see what the event is
calling and which may take that long to finish. Your system/distro
should fix that by detaching with all such tools from the udev event
process, an operate in the background, instead of blocking the udev
queue.

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=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

Re: Trouble with udevtrigger/udevsettle

[Logan Rathbone]

Bryan Kadzban wrote:
> Oops, didn't send this to the list last time:
>
> Bryan Kadzban wrote:
>   
>> Logan Rathbone wrote:
>>
>>     
>>> Thus I have to wait quite a while (about a minute or so) for
>>> udevsettle to complete and have my bootup continue.  Any ideas what
>>> this could be about?
>>>       
>> Hmm...  Just guessing here, but:
>>
>>
>>     
>>> I never really have a network cable plugged into the via-rhine, but I
>>> don't see why that would make a difference.
>>>       
>> Your distro may have a rule set up to try to ifup the interface when it
>> sees an add event for it.  If this ifup is trying to use DHCP, it *may*
>> take a long time to fail when it can't find a DHCP server.  I seem to
>> remember a 30-second timeout with dhcpcd in the past, which it waits for
>> twice; that would match up with the one-minute timing you're seeing.
>>
>> I would suspect that the DHCP client should to fail immediately if it
>> doesn't detect a link, but I don't know for sure whether all of them do.
>>
>> You might try blacklisting via-rhine in modprobe.conf.  That way you
>> should never get an add event for eth0, and if the long delay is due to
>> some rule that triggers from that, it shouldn't happen.
>>     
Yes, you are right!  The udev SRPM I built from came from Mandriva, who 
set up udev rules to automatically configure and start hotplugged 
ethernet devices.  I guess they don't use udevtrigger for coldplugging, 
as that would probably produce the same problem I was having.  I suppose 
that I could reconfigure the rules to fork the dhclient process, but 
then I'd possibly risk a race condition with some later services (not 
likely, but possible).  But I guess I'm doing that anyway since my 
'network' initscript uses ifplugd to bring the interfaces up.

But I digress!  Maybe in the future I'll toy around with it and have 
udev rules handle the configuration and starting/stopping of my ethernet 
devices, but I certainly don't need that functionality atm.

Thanks for your help, guys.

--Logan

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

Re: Trouble with udevtrigger/udevsettle

[Andrey Borzenkov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 22 September 2006 07:10, Logan Rathbone wrote:
>  The udev SRPM I built from came from Mandriva, who
> set up udev rules to automatically configure and start hotplugged
> ethernet devices.  I guess they don't use udevtrigger for coldplugging,

not yet. Should be in post-2007
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFE/9sR6LMutpd94wRAoZBAKCNHknGLD3htpC0OHDDjdQo1UbaNQCgtNN/
+fSq3UuOoVkNa9pmq4ltkvs=OET3
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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