Bug 203500

Summary:	kernel lockups when booting at the network init script
Product:	[Fedora] Fedora	Reporter:	clifford snow <jcs>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-08-22 03:23:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.