Red Hat Bugzilla – Bug 203498
kernel lockups when booting at the network init script
Last modified: 2007-11-30 17:11:41 EST
Description of problem: When booting up, to 2.6.17-1.2174.2.1_FC5.netdev.8 kernel with the bcm43xx wireless network driver, the system locks ups at the network if a wired connection is present. Without the wired connection, NetworkManager never connects to my WPA wireless network. Version-Release number of selected component (if applicable): kernel 2.6.17-1.2174.2.1_FC5.netdev.8 How reproducible: Always Steps to Reproduce: 1. Install 2.6.17-1.2174.2.1_FC5.netdev.8 2. Connect wired network to eth0 device 3. Reboot Actual results: System locks up at the eth0 network device Expected results: System boots up normally with network connection on eth0 Additional info: This may be a duplicate to 184440 kernel/bcm43xx lockup report. Without a wired connection, NetworkManager attemts to connect to last good wireless network but never connects. Also - I have a different password for the Gnome-keyring than the login which causes the keyring to prompt for a password. I'm not sure what if any the delay causes NetworkManager. I believe that an downstream update to gnome-keyring will allow the user to change the password. I can't wait.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
This report is for kernel 2.6.17-1.2174.2.1_FC5.netdev.8 BTW - the same condidtions occur in subsequent updates to latest the netdev kernel.
What is the wired device? Please attach the output of running "sysreport"...thanks!
I just successfully installed 2.6.18-1.2200.2.10.fc5.netdev.13.1 which works. I can give you a copy of sysreport if you still want, otherwise, you can close this out. ...thanks