boot process hangs when wireless switch enabled

Bug #106256 reported by Christian Dalbjerg
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

My computer is a VEGA+ M31E1. It features an Intel PRO/Wireless 3945ABG wireless network-card.

It has a switch which enables/disables the wireless card. When the switch is turned 'on', the boot-process hangs for more than a minute. When the switch is turned 'off', the boot-process is smooth and fast.

I am running Ubuntu 6.10 with all updates installed (13/04 2007). I have tried installing Ubuntu 7.04 beta, but the problem remains. I don't know if I need to submit some logfiles, (or where to find them), so please do write me and ask for further information. Although I did found the following file: /var/log/boot :

Apr 13 17:07:18 rcS: * Reading files needed to boot... [80G
[74G[ ok ]
Apr 13 17:07:19 rcS: * Setting preliminary keymap... [80G
[74G[ ok ]
Apr 13 17:07:20 rcS: * Preparing restricted drivers... [80G
[74G[ ok ]
Apr 13 17:07:20 rcS: * Starting basic networking... [80G
[74G[ ok ]
Apr 13 17:07:20 rcS: * Starting kernel event manager... [80G
[74G[ ok ]
Apr 13 17:07:20 rcS: * Loading hardware drivers... [80G error receiving uevent message: No buffer space available
Apr 13 17:07:22 rcS:
[74G[ ok ]
Apr 13 17:07:23 rcS: * Loading manual drivers... [80G
[74G[ ok ]

THIS IS WHERE THE PROBLEM SEEMS TO OCCURE

Apr 13 17:07:23 rcS: * Mounting local filesystems... [80G
[74G[ ok ]
Apr 13 17:07:23 rcS: * Activating swapfile swap... [80G
[74G[ ok ]
Apr 13 17:08:30 rcS: * Configuring network interfaces... [80G
[74G[ ok ]
Apr 13 17:08:30 rcS: * Setting up console keymap... [80G
[74G[ ok ]

Apr 13 17:08:31 rc2: * Loading ACPI modules... [80G
[74G[ ok ]
Apr 13 17:08:31 rc2: * Starting ACPI services... [80G
[74G[ ok ]
Apr 13 17:08:32 rc2: * Starting system log... [80G
[74G[ ok ]
Apr 13 17:08:32 rc2: * Starting kernel log... [80G
[74G[ ok ]
Apr 13 17:08:33 rc2: * Starting GNOME Display Manager... [80G
[74G[ ok ]
Apr 13 17:08:34 rc2: * Starting Common Unix Printing System: cupsd [80G
[74G[ ok ]
Apr 13 17:08:34 rc2: * Starting HP Linux Printing and Imaging System [80G
[74G[ ok ]
Apr 13 17:08:35 rc2: * Starting system message bus dbus [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: * Starting Hardware abstraction layer hald [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: * Starting DBUS aware dhcp client: dhcdbd [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: * Starting NetworkManager daemon [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: * Starting NetworkManager dispatcher [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: * Starting System Tools Backends system-tools-backends [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: * Starting powernowd... [80G
[74G[ ok ]
Apr 13 17:08:37 rc2: Starting VMware services:
Apr 13 17:08:37 rc2: Virtual machine monitor[71G done
Apr 13 17:08:37 rc2: Virtual ethernet[71G done
Apr 13 17:08:37 rc2: Bridged networking on /dev/vmnet0[71G done
Apr 13 17:08:38 rc2: Host-only networking on /dev/vmnet1 (background)[71G done
Apr 13 17:08:38 rc2: Host-only networking on /dev/vmnet8 (background)[71G done
Apr 13 17:08:38 rc2: NAT service on /dev/vmnet8[71G done
Apr 13 17:08:38 rc2: * Starting Bluetooth services [80G
[74G[ ok ]
Apr 13 17:08:38 rc2: * Starting anac(h)ronistic cron: anacron [80G
[74G[ ok ]
Apr 13 17:08:38 rc2: * Starting deferred execution scheduler atd [80G
[74G[ ok ]
Apr 13 17:08:38 rc2: * Starting periodic command scheduler... [80G
[74G[ ok ]
Apr 13 17:08:38 rc2: * Enabling additional executable binary formats binfmt-support [80G
[74G[ ok ]
Apr 13 17:08:38 rc2: * Checking battery state... [80G
[74G[ ok ]
Apr 13 17:08:38 rc2: * Running local boot scripts (/etc/rc.local) [80G
[74G[ ok ]

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
Anders Westlund (ysse) wrote : "delays" describes the situation better than "hangs"

Got the same WLAN hardware, and also have the one minute delay at "Configuring network interfaces", when the WLAN switch is on.

I use NetworkManager for wireless roaming, which in turn depends on passwords in a keyring, so any attempt to start up the WLAN interface before login is doomed to fail.

uname -a:
Linux andersw 2.6.20-15-generic #2 SMP Sat Apr 14 00:54:01 UTC 2007 i686 GNU/Linux

dmesg.log attached. lspci -vvnn output forthcoming.

Revision history for this message
Anders Westlund (ysse) wrote : lspci -vvnn
Revision history for this message
Christian Dalbjerg (christiandalbjerg-deactivatedaccount) wrote : Requested output

I have run the commands, and the results are:

1. 'uname -a' :

Linux christian-laptop 2.6.17-11-generic #2 SMP Tue Mar 13 23:32:38 UTC 2007 i686 GNU/Linux

2. 'dmes > dmesg.log' : Resulting file attached

3. 'sudo lspci -vvnn > lspci-vvnn.log' : Resulting file attached

Revision history for this message
Christian Dalbjerg (christiandalbjerg-deactivatedaccount) wrote : lspci-vvnn.log
Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

description: updated
Revision history for this message
Mikael Nilsson (mini) wrote :

I no longer see this on 2.6.26 or 2.6.27.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I'll tentatively mark this "Fix Released" for Intrepid based on the previous comment. Christain, since you are the original bug reporter, if this is not fixed for you please reopen this report by setting the status from "Fix Released" back to "New". Thanks.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.