[SOLVED] CRDA slowing boot process.

paranoid times · 09-20-2011, 08:17 AM

So my system is taking quite awhile to boot. In taking a look in the boot log I found the follow:

Code:

Sep 18 17:52:53 magicbane kernel: [    7.548806] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 18 17:52:53 magicbane kernel: [    7.687552] cfg80211: Calling CRDA to update world regulatory domain
Sep 18 17:52:53 magicbane kernel: [    7.719399] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (05e3:0505)
Sep 18 17:52:53 magicbane kernel: [   71.992543] cfg80211: World regulatory domain updated:
Sep 18 17:52:53 magicbane kernel: [   71.992553] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Sep 18 17:52:53 magicbane kernel: [   71.992562] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 18 17:52:53 magicbane kernel: [   71.992569] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep 18 17:52:53 magicbane kernel: [   71.992577] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep 18 17:52:53 magicbane kernel: [   71.992584] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 18 17:52:53 magicbane kernel: [   71.992592] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 18 17:52:53 magicbane kernel: [   71.992619] cfg80211: Calling CRDA for country: FR
Sep 18 17:52:53 magicbane kernel: [   72.006474] usbcore: registered new interface driver uvcvideo
Sep 18 17:52:53 magicbane kernel: [   72.006643] USB Video Class driver (v1.0.0)

So I suspect that the kernel calls CRDA to update the world domain. Then it loads up the camera, then it waits. The world domain would be CRDA figuring out where I am then setting which WIFI channels it will use based off of that? If that is right, given that I know I am in France, can I just tell it to skip this check? As it stands I'm wondering how it would do that to begin with (Hasn't started any networking devices yet) which suggests that I just don't know what it is doing.

Whatever the case, I would like to verify that it is indeed CRDA that is taking the time (not the camera or some other seemingly unlikely thing). And moreover any ideas on how I might speed my boot up by sixty seconds or so.

Thanks,
Michael

corp769 · 09-21-2011, 02:13 AM

Hello,

I know this might seem odd, but what kind of wireless device do you have? I had a similar issue to this, and I had a wireless-N chipset; After identifying the underlaying driver, I switched to either a different driver or something (yes, I forget exactly what I did) but after messing around, I was able to get it to stop complaining as much.

Cheers,

Josh

paranoid times · 09-21-2011, 06:13 AM

A good thought. I poked around with it a bit. First I removed CRDA, no change. So I started to suspect that maybe there really was a problem with loading up the camera. Well after disabling it I get the following:

Code:

Sep 21 13:03:44 magicbane kernel: [    7.525185] cfg80211: Calling CRDA to update world regulatory domain
Sep 21 13:03:44 magicbane kernel: [    7.579071] usb 1-8: new high speed USB device using ehci_hcd and address 3
Sep 21 13:03:44 magicbane kernel: [   73.278257] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input8
Sep 21 13:03:44 magicbane kernel: [   73.326576] cfg80211: World regulatory domain updated:

Very similar, but everything has shifted a bit. I had a simular but more verbose problem a little earlier:
http://www.linuxquestions.org/questi...g-boot-902565/
Well reverting the kernel to the install kernel made the error messages go away. But I suspect the same thing is still happening. Just more quietly. So I think I'm going to move from the assumption that it i still the soft lockup problem. Unless anyone has any suggestions to the contrary.

Speaking of which does anyone have any suggestions for what I might do to approach this problem?

Thanks,
Michael

paranoid times · 10-02-2011, 08:21 AM

Well I appear to have come across a solution. I was disabling devices that I wasn't using in BIOS. And after disabling the onboard LAN everything boots up right quick. I tested it a few times. With the ethernet enabled things pause during boot. Without it everything is fine. Not the best solution, but since I don't use the wired network here, it works fine for me.