Bug 630381

Summary: after resume, networkmanager sometimes remains in state: asleep
Product: [Fedora] Fedora Reporter: Craig Ringer <craig>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 13CC: bugzilla, dcbw, jklimes, projects.rg, pza
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-18 08:32:44 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:
Attachments:
Description Flags
Logs from NM, covering sleep and resume, then subsequent NM restart
none
grep NetworkManager /var/log/messages none

Description Craig Ringer 2010-09-05 08:33:22 UTC 
Description of problem:

After my Dell XPS M1330 (Intel 10/100 ethernet, iwl4965agn wifi) running Fedora Core 13 x64 with kernel 2.6.33.8-149.fc13.x86_64 resumes from suspend, sometimes networking doesn't come back up.

The GNOME NetworkManager applet shows "Enable networking" unchecked and usually greyed out. If it's not greyed out, checking it has no apparent effect; it remains unchecked, wifi doesn't come back up, etc.

When NetworkManager is in this condition, nm-tool reports "State: asleep" .

The underlying hardware still works fine. I can use iwconfig and ifconfig to get a wifi connection set up, then dhclient to obtain an IP, just like in the pre-NM days.

Restarting NetworkManager appears to restore it to functionality, and it connects to wifi if it becomes available.

This is a fresh Fedora Core 13 x64 install on a machine that was previously running Ubuntu 10.04 (32 bit). I didn't see this issue under Ubuntu, but it was running nm 0.70 whereas fc13 has 0.8.1 .


How reproducible:

It's intermittent and I haven't been able to reproduce it on demand. It occurs on something like 1/5 of resumes. I suspect a race condition somewhere.
Comment 1 Craig Ringer 2010-09-05 08:40:08 UTC 
This probably isn't related to bug 573799 or bug 589108, as they appear to relate to NM state tracking after the machine is suspended, then loses power. In this case the machine resumed normally, but NM didn't seem to "notice" the resume, thinking the system was still suspended.

Logging attached.
Comment 2 Craig Ringer 2010-09-05 08:40:54 UTC 
Created attachment 443131 [details]
Logs from NM, covering sleep and resume, then subsequent NM restart
Comment 3 Craig Ringer 2010-09-05 08:45:08 UTC 
Oh: Having failed to provide the obvious:

NetworkManager-0.8.1-4.git20100817.fc13.x86_64
Comment 4 Raphael Groner 2010-09-05 19:04:05 UTC 
Confirmed here.

NetworkManager-0.8.1-4.git20100817.fc13.x86_64

Although, resume from hibernation (instead of standby) seems to work.
Comment 5 Raphael Groner 2010-09-05 19:09:35 UTC 
Created attachment 443187 [details]
grep NetworkManager /var/log/messages
Comment 6 Raphael Groner 2010-09-05 19:14:43 UTC 
Duplication of bug #629783?
Comment 7 Phil Anderson 2010-09-05 23:26:11 UTC 
I'm also encountering this.  It's only been happening for a couple of weeks now, on both my and my partner's laptop.  I'm trying out NetworkManager-0.8.1-6.git20100831.fc13 now to see if it improves the situation.
Comment 8 Raphael Groner 2010-09-06 17:45:13 UTC 
Take a look to my comment #10 to bug #627365. The workaround there works for me to fix the issue.
Comment 9 Jirka Klimes 2010-09-07 10:53:01 UTC 
The issue not waking up has been fixed in NetworkManager-0.8.1-6.git20100831:
NM don't rely on pm-utils now:
see https://bugzilla.redhat.com/show_bug.cgi?id=627279#c13
There is a workaround to the issue - adding '--print-reply' to /usr/lib64/pm-utils/sleep.d/55NetworkManager:
see https://bugzilla.redhat.com/show_bug.cgi?id=627279#c10

The issue of grayed checkboxes has been fixed by NetworkManager-0.8.1-6.git20100831 as well (bug 627365)
Comment 10 Phil Anderson 2010-11-17 01:17:01 UTC 
I'm not encountering this anymore with the current NetworkManager packages.
Comment 11 Jirka Klimes 2010-11-18 08:32:44 UTC 
Thanks for reporting! I close the bug then.
Comment 12 Gerhard 2010-11-18 10:25:49 UTC 
Sorry, but with F14 and nm-version
NetworkManager-0.8.1-9.git20100831.fc13.x86_64
I have the problem again.
I'm not sure, but I think, it's only on hidden networks (I can test, if you want).
With F13 I didn't have the problem.