LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-22-2012, 03:17 PM   #1
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,635

Rep: Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567
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]

Last edited by astrogeek; 09-22-2012 at 03:20 PM.
 
Old 09-22-2012, 03:40 PM   #2
philanc
Member
 
Registered: Jan 2011
Posts: 59

Rep: Reputation: 21
Quote:
Originally Posted by astrogeek View Post
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
 
1 members found this post helpful.
Old 09-22-2012, 04:10 PM   #3
Marcelo_Belfalas
LQ Newbie
 
Registered: Apr 2012
Location: Brazil
Distribution: Slackware64-current multilib
Posts: 23

Rep: Reputation: 10
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.
 
1 members found this post helpful.
Old 09-22-2012, 04:39 PM   #4
yenn
Member
 
Registered: Jan 2011
Location: Czech Republic
Distribution: Slackware, Gentoo
Posts: 152

Rep: Reputation: 21
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.
 
1 members found this post helpful.
Old 09-22-2012, 05:04 PM   #5
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,635

Original Poster
Rep: Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567
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!
 
Old 09-22-2012, 05:29 PM   #6
Marcelo_Belfalas
LQ Newbie
 
Registered: Apr 2012
Location: Brazil
Distribution: Slackware64-current multilib
Posts: 23

Rep: Reputation: 10
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...
 
Old 09-22-2012, 06:13 PM   #7
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by philanc View Post
...
It has been reported several times here in previous threads.
...
Quote:
Originally Posted by astrogeek View Post
...
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.
 
Old 09-22-2012, 06:27 PM   #8
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,635

Original Poster
Rep: Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567
Quote:
Originally Posted by guanx View Post
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.
 
Old 09-22-2012, 06:28 PM   #9
yenn
Member
 
Registered: Jan 2011
Location: Czech Republic
Distribution: Slackware, Gentoo
Posts: 152

Rep: Reputation: 21
Quote:
Originally Posted by astrogeek View Post
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.
 
2 members found this post helpful.
Old 09-22-2012, 06:31 PM   #10
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,635

Original Poster
Rep: Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567
Quote:
Originally Posted by yenn View Post
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!
 
Old 09-22-2012, 08:29 PM   #11
philanc
Member
 
Registered: Jan 2011
Posts: 59

Rep: Reputation: 21
Quote:
Originally Posted by yenn View Post
Great explanation. Thanks for the link!

Phil
 
Old 09-23-2012, 03:12 PM   #12
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,635

Original Poster
Rep: Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567Reputation: 567
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 View Post
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!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Greylisting delay too long chiglet Linux - Newbie 2 02-07-2012 07:42 AM
battery monitor long delay maginotjr Slackware 0 07-27-2005 04:35 PM
long delay dummyagain Programming 1 10-28-2003 04:49 AM
lilo long delay??? comtronics Debian 2 10-22-2003 03:59 AM
takes a long delay to resolve name Kocil Linux - Networking 2 03-11-2003 09:09 AM


All times are GMT -5. The time now is 09:21 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration