Bugzilla – Bug 183225
NetworkManager doesn't activate networks after Suspend2Disk
Last modified: 2006-06-12 08:10:34 UTC
On my machine, each time I resume the system from Suspend2Disk, NetworkManager doesn't set up the network. Even ifconfig doesn't show eth0 which is powered by the tg3 driver. Solution for me is, right now, to set the NetworkManager to the offline mode after resume, and then to online mode. After this procedure it sees the interfaces and activates them, as he should have done before. Maybe this affects Suspend2Ram too, but at the moment I'm not able to test it because the tg3 driver isn't working with Suspend2Ram. See #159136 I will attach the log file from the NetworkManager.
Created attachment 88283 [details] The log file
Sounds like a driver or power management issue, not NM specific.
This is a duplicate of bug #159136. *** This bug has been marked as a duplicate of 159136 ***
Dennis, sorrry, I haven't carefully read the initial bug description. But still, it is most likely a duplicate of bug 159136. Can you please check whether the output of nm-tool shows "Hardware Link: yes" after resuming? Thank you!
After resuming nm-tools output is "Hardware Link: no". Are you sure that this is a duplicate of bug #159136? As far as I understand the discribtion there, this applies only to suspend to ram. I've also add comments there, because the problem with suspend to ram is occuring here, too. I've got another question: My system doesn't complete the resume after suspend to ram, but I don't know if this is also an effect of the tg3 driver. So after resuming from STR, the powersave daemon doesn't seem to work any longer, and the uhci_hcd driver for example isn't reloaded. Should I file a new bug for this issue?