networking didn't return from suspend

Bug #1251054 reported by Seth Arnold on 2013-11-13
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

Wireless networking did not work when I resumed from suspend.

Using the indicator/applet to "Enable Networking" didn't associate my wireless with the AP. Plugging in an Ethernet cable did not bring back networking. The hardware rfkill switch did not bring back networking.

A reboot allowed me to associate as I expected.


ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
 /dev/snd/controlC0: sarnold 2966 F.... pulseaudio
Date: Wed Nov 13 15:03:20 2013
HibernationDevice: RESUME=UUID=81b2976f-2830-4449-9dae-e1d44a43fa78
InstallationDate: Installed on 2012-10-18 (391 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: LENOVO 2359CTO
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash vt.handoff=7
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-11-06 (7 days ago) 09/13/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ET62WW (2.04 )
dmi.board.asset.tag: Not Available 2359CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG4ET62WW(2.04):bd09/13/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: 2359CTO
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO

Seth Arnold (seth-arnold) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
description: updated
Seth Forshee (sforshee) wrote :

I've seen some reports about NetworkManager failing to work after suspend, and since none of your connections work I'd guess this is what you're seeing. Next time this happens see if restarting NetworkManager fixes the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
Seth Arnold (seth-arnold) wrote :

Seth Forshee, good news, bluntly restarting NetworkManager allowed me to continue without the reboot:

$ sudo service network-manager restart
[sudo] password for sarnold:
network-manager stop/waiting
network-manager start/running, process 6165

I didn't see anything in my logs that suggests what the error is.

Is 'linux' still the correct package? Or since restarting NetworkManager 'fixes' the problem, should this be re-assigned towards nm?


Seth Forshee (sforshee) wrote :

From what I see in the logs there's not even an attempt to establish a connection after resume, so I think the problem is likely with network-manager. Reassigning.

affects: linux (Ubuntu) → network-manager (Ubuntu)
Rafael Levi (rlevi66) wrote :

I have the same problem.

'sudo killall NetworkManager"

restores the connection.

Rafael Levi (rlevi66) wrote :

This is the syslog for suspend and wakeup. The networkmanager didn't wake up.

Seth Arnold (seth-arnold) wrote :

Here's my syslog around another failure. I suspend in Nov 21, resume in Nov 22, and used "sudo restart network-manager" to bring networking back.


Yanpas (yanpaso) wrote :

Still in Trusty... Did fresh install help somebody?

Seth Arnold (seth-arnold) wrote :

I upgraded from 13.10 to 14.04 LTS but I can confirm that this problem still happens in 14.04 LTS.

sudo killall systemd-logind -> changed nothing
sudo killall NetworkManager --> fixed networking immediately.

Toggling the software "Enable Networking" in the NM applet did not work. Toggling the hardware rfkill switch did not work.

NoOp (glgxg) wrote :

$ uname -r

$ apt-cache policy network-manager
  Version table:
 *** 0
        500 trusty/main amd64 Packages
        100 /var/lib/dpkg/status

       description: Wireless interface
       product: Centrino Wireless-N 1000 [Condor Peak]
       vendor: Intel Corporation

$ lsmod | grep wifi
iwlwifi 169932 1 iwldvm
cfg80211 484040 3 iwlwifi,mac80211,iwldvm

sudo killall NetworkManager
sudo kill PIDofNetworkManager

works for me as well.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers