LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   RC5 - Long delay during boot (http://www.linuxquestions.org/questions/slackware-14/rc5-long-delay-during-boot-4175428568/)

astrogeek 09-22-2012 03:17 PM

RC5 - Long delay during boot
 
Fresh, full install of RC5.

During boot I experience a long (~15 seconds) delay usually immediately after i915 drm is initialized, everything seems to just freeze. After the delay I get the following messages, then it continues to boot normally.

Code:

udevd[1032] worker [1046] timeout kill it
udevd[1032] seq 1122 'devices/pci0000:00/0000:00:1e.0/0000:05:04.0'  killed

On first boot I thought it was associated with the display driver but now I think it is the wireless device and the timing is just coincidental. I expect it needs a module or udev rule to get past it, but I am not udev guru enough to know what to do with it.

Additional info...

Code:

lspci

...
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
05:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
...

Code:

/etc/udev/rules.d/70-persistent-net.rules

# PCI device 0x8086:/sys/devices/pci0000:00/0000:00:1e.0/0000:05:04.0 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:ce:4b:24:6c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

I don't get anything useful from dmesg as far as I can tell.

Problem is essentially the same with huge or generic kernels.

Any help appreciated!

[EDIT]
The ipw2200 module is loading and the device is accessible via ifconfig after boot (I do not use it so have not configured it).
[/EDIT]

philanc 09-22-2012 03:40 PM

Quote:

Originally Posted by astrogeek (Post 4786726)
Fresh, full install of RC5.

During boot I experience a long (~15 seconds) delay [...]

Code:

udevd[1032] worker [1046] timeout kill it
udevd[1032] seq 1122 'devices/pci0000:00/0000:00:1e.0/0000:05:04.0'  killed

On first boot I thought it was associated with the display driver but now I think it is the wireless device [...]

The udevd message seems to confirm the issue was with your wireless device (pci 05:04.0 is the wifi card according to the lspci fragment you provided).

I have the same issue here. Also with the wifi controller, although this is a Broadcom BCM43225 (driver is brcmsmac).

It has been reported several times here in previous threads. IIRC, it can be avoided by hand-loading the kernel module before udevd tries to do it.

For the moment I just reverted to udev-165 (from 13.37) which works fine on my PC

Phil

Marcelo_Belfalas 09-22-2012 04:10 PM

I had the same problem...

Also thought i915 was the problem and it was brcmsmac driver...

To solve it I blacklisted the brcmsmac driver on udev and loaded it in rc.local.

yenn 09-22-2012 04:39 PM

Another workaround is to create initrd with that particular module. Udev will throw few warnings/errors, but as far as I tried, they are harmless. At least it works for my ipw2200 wireless module.

astrogeek 09-22-2012 05:04 PM

Fixed for now by adding ipw2200 to my initrd.

I was hoping to understand the "why" a little better, but no time today. Anyone know of a good, useful overview of udev and the rules files?

Thanks to all who replied!

Marcelo_Belfalas 09-22-2012 05:29 PM

Don't know why, but adding the brcmsmac didn't solved mine when I tried before. The module wouldn't load automatically and I had to add it manually if I had it on initrd.

The udev problem in my case seems to be with CRDA, but this is just a guess...

guanx 09-22-2012 06:13 PM

Quote:

Originally Posted by philanc (Post 4786737)
...
It has been reported several times here in previous threads.
...

Quote:

Originally Posted by astrogeek (Post 4786791)
...
I was hoping to understand the "why" a little better, but no time today.
...

Have no time? Searching this forum takes few minutes.

If someone else finds the same problem and step into this thread, just believe philanc and do a search to find detailes in this forum about cause and cure.

astrogeek 09-22-2012 06:27 PM

Quote:

Originally Posted by guanx (Post 4786811)
Have no time? Searching this forum takes few minutes.

If someone else finds the same problem and step into this thread, just believe philanc and do a search to find detailes in this forum about cause and cure.

Actually, I had done more than a cursory look in these forums, and found several threads for both the i915 driver and the wireless, but nothing that I found really helpful to understanding the ipw2200 problem. I had thought that I would add the module to the initrd on next boot, but was looking for a better understanding of it more than a quick fix. In the end, I have a quick fix but still lack any good understanding of why it fails with udev.

It might well be due to my own slow rate of understanding the obvious, but I did not find a useful cause/cure for it here.

yenn 09-22-2012 06:28 PM

Quote:

Originally Posted by astrogeek (Post 4786791)
Fixed for now by adding ipw2200 to my initrd.

I was hoping to understand the "why" a little better, but no time today. Anyone know of a good, useful overview of udev and the rules files?

Due to changes in udev, some modules that needs to load firmware just timeout now. See http://www.spinics.net/lists/linux-w.../msg83448.html. We either need to revert udev back to old behaviour or patch ipw2200 and other similar acting modules for new udev.

astrogeek 09-22-2012 06:31 PM

Quote:

Originally Posted by yenn (Post 4786817)
Due to changes in udev, some modules that needs to load firmware just timeout now. See http://www.spinics.net/lists/linux-w.../msg83448.html. We either need to revert udev back to old behaviour or patch ipw2200 and other similar acting modules for new udev.

Now THAT looks helpful! I'll digest it later today!

Thanks yenn!

philanc 09-22-2012 08:29 PM

Quote:

Originally Posted by yenn (Post 4786817)

Great explanation. Thanks for the link!

Phil

astrogeek 09-23-2012 03:12 PM

My horizons are expanded, if not my actual gray matter!

Read yenn's link to learn why it broke from older behavior. I have often read refs to "reverting to udev-xxx" and it always made me ask, "But WHY?".

Quote:

Originally Posted by yenn (Post 4786817)
See http://www.spinics.net/lists/linux-w.../msg83448.html. We either need to revert udev back to old behaviour or patch ipw2200 and other similar acting modules for new udev.

Then, the extent of my previous udev knowledge was mostly gained from ordering my net and USB device names - sketchy at best. In looking into this I read the ArchWiki article here https://wiki.archlinux.org/index.php/Udev which has all the answers, including the vagaries of rules files and blacklisting - read it!


All times are GMT -5. The time now is 11:43 PM.