Bug 817635

Summary:	nm-online failed to start, hung on shutdown and breaks connectivity on startup
Product:	[Fedora] Fedora	Reporter:	Artemy Kapitula, Mail.Ru Cloud Solutions <dalt74>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	danw, dcbw, notting
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-01 02:50:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Artemy Kapitula, Mail.Ru Cloud Solutions 2012-04-30 17:30:26 UTC

Description of problem:

When NetworkManager-wait-online service failed to start on Dell notebook. On boot, system hang for a 30 seconds while trying to start NetworkManager-wait-online.service systemd unit. When 30 second expires, system continue to boot, but there are no WiFi connections until relaoding WiFi card driver (rmmod iwl3945; modprobe iwl3945 in my case) or switching wireless adapater on-off with hardware switch. On reboot, system hung and doesn't poweroff or reboot.

Version-Release number of selected component (if applicable):

NetworkManager-0.9.4.0-7.git20120403.fc17.x86_64

Additional info:

I tried to clean all information about WiFi networks, but it gives me no effect.

Then, I tried to disable service with systemctl (systemtl disable NetworkManager wait-online.service) but it doesn't give any effect or me too - on boot, system again waits on this unit, failes unit and then hung on startup. To escape problem, I removed /lib/systemd/system/NetworkManager-wait-online.service and this solved a problem:

No hung on startup
No hung at shutdown
After boot WiFi network connection activated if known network is available

Comment 1 Bill Nottingham 2012-05-01 02:50:29 UTC


*** This bug has been marked as a duplicate of bug 815091 ***