Bug 203500 - kernel lockups when booting at the network init script
Summary: kernel lockups when booting at the network init script
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-22 03:14 UTC by clifford snow
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-08-22 03:23:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description clifford snow 2006-08-22 03:14:10 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.