Bootup delay at /etc/rc.d/rc.udev

dive · 11-14-2007, 01:30 PM

There have been a few posts about this with some suggestions posted but none that seem to help my problem.

Anyway I thought I would try to get to the bottom of this since my pc was hanging at the 'trigger udev events...' stage for almost a minute it seems.

By putting in some echoes in rc.udev I find that it is udevsettle that is the problem:

/sbin/udevtrigger $OPT && /sbin/udevsettle --timeout=120

All I have managed to do is make the timeout 45 secs which helps a little but is still too long. Anything less than 45 secs and dhcp is not able to get an ip address and hangs indefinitely in rc.inet1 until I give the 3 fingered salute. I'm guessing that it's because udev hasn't found or initiated my NIC yet(?)

I really don't know where to go from here except to downgrade udev and test, downgrade, test, etc.

If anyone has any thoughts on this or has anything to add please do.

onebuck · 11-15-2007, 07:25 AM

Hi,

Did you check your '/etc/udev/rules.d/75-network-devices.rules' for the NIC? What about the '/etc/rc.d/rc.inet1.conf' file, settings correct for the device(s)?

evilDagmar · 11-16-2007, 11:48 AM

Quote:

Originally Posted by dive

There have been a few posts about this with some suggestions posted but none that seem to help my problem.

Anyway I thought I would try to get to the bottom of this since my pc was hanging at the 'trigger udev events...' stage for almost a minute it seems.

By putting in some echoes in rc.udev I find that it is udevsettle that is the problem:

/sbin/udevtrigger $OPT && /sbin/udevsettle --timeout=120

All I have managed to do is make the timeout 45 secs which helps a little but is still too long. Anything less than 45 secs and dhcp is not able to get an ip address and hangs indefinitely in rc.inet1 until I give the 3 fingered salute. I'm guessing that it's because udev hasn't found or initiated my NIC yet(?)

I really don't know where to go from here except to downgrade udev and test, downgrade, test, etc.

If anyone has any thoughts on this or has anything to add please do.

You simply wait for the udev guys to fix this. This is a bit of a "known problem" at this point. It should go away if you actually have a carrier (i.e., a network plugged into) on the ethernet interfaces when it's probing them because that's what it's waiting for.

Yes, it's annoying, but we're Linux users so we don't reboot very often.

dive · 11-16-2007, 01:25 PM

Quote:

Originally Posted by onebuck

Hi,

Did you check your '/etc/udev/rules.d/75-network-devices.rules' for the NIC? What about the '/etc/rc.d/rc.inet1.conf' file, settings correct for the device(s)?

Yep all seems correct.

Quote:

Originally Posted by evilDagmar

You simply wait for the udev guys to fix this. This is a bit of a "known problem" at this point. It should go away if you actually have a carrier (i.e., a network plugged into) on the ethernet interfaces when it's probing them because that's what it's waiting for.

Yes, it's annoying, but we're Linux users so we don't reboot very often.

Yeah mine is on practically 24/7 anyway now, but it is annoying when I used to boot in 30 secs or so.

I do have a carrier from my cable modem afaik (all the leds are on as normal). Strange thing is I tried udev 097 package, but with the rc.udev from 116 and the problem went away. But I had quite a few dhcpd errors and also an error because 097 udevtrigger doesn't seem to recognise the '--retry-failed' switch. But taking this out just made boot up freeze at rc.inet1. Strange.