laptop unresponsive after suspend

Bug #1415039 reported by Till on 2015-01-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pm-utils (Ubuntu)
Undecided
Unassigned

Bug Description

After suspend, the system becomes unresponsive. Fan keeps running, full reboot needed.

In /var/log/pm-suspend.log the only error is:

"Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory"

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 27 14:40:12 2015
InstallationDate: Installed on 2015-01-26 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

Till (n-ubunnu-c) wrote :
Adam Colligan (adam-p) wrote :

Can you try something for me? I'm wondering whether you're getting the same thing I reported here that may be a part of another, earlier bug (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271/comments/8).

When you resume from suspend and find the system non-responsive, press ctrl-alt-f1. If you get a text login screen, don't do anything on it, but press ctrl-alt F7. This should bring you back to the visual session. Do you then get an unlock screen or a working desktop? If so, it's probably the same issue I'm having (waiting to see if it should be a new bug or a continuation of that old one). If not, let me know anyway just so I can cross it off the list.

Adam Colligan (adam-p) wrote :

You can also check /var/log/syslog , which often has more in-depth details about what happened during a suspend.

Till (n-ubunnu-c) wrote :

Hi Adam,

Thanks for your response. Switching to other TTYs does not work.

This is the relevant section of syslog, looks like suspend is never completed:

Jan 26 23:38:17 thinkpad anacron[1016]: Job `cron.daily' started
Jan 26 23:38:17 thinkpad anacron[2580]: Updated timestamp for job `cron.daily' to 2015-01-26
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> sleep requested (sleeping: no enabled: yes)
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> sleeping or disabling...
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> (eth0): cleaning up...
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> (eth0): taking down device.
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> NetworkManager state is now ASLEEP
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> (wlan0): device state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37]
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> (wlan0): cleaning up...
Jan 26 23:44:19 thinkpad NetworkManager[847]: <info> (wlan0): taking down device.
Jan 26 23:44:20 thinkpad dbus[772]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
Jan 26 23:44:20 thinkpad dbus[772]: [system] Successfully activated service 'org.freedesktop.systemd1'
Jan 27 17:15:23 thinkpad rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="775" x-info="http://www.rsyslog.com"] start
Jan 27 17:15:23 thinkpad rsyslogd: rsyslogd's groupid changed to 104
Jan 27 17:15:23 thinkpad rsyslogd: rsyslogd's userid changed to 101
Jan 27 17:15:23 thinkpad kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jan 27 17:15:23 thinkpad kernel: [ 0.000000] Initializing cgroup subsys cpu
Jan 27 17:15:23 thinkpad kernel: [ 0.000000] Initializing cgroup subsys cpuacct

Till (n-ubunnu-c) wrote :

I should add that system randomly freezes. No info in syslog, as hard boot commences completely out of the blue:

Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> (wlan0): DHCPv4 state changed renew -> renew
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> address x.x.x.x
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> prefix 24 (255.255.255.0)
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> gateway x.x.x.x
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> nameserver 'x.x.x.x'
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> nameserver 'x.x.x.x'
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> domain name 'xxx'
Jan 27 18:53:24 thinkpad NetworkManager[966]: <info> wins 'x.x.x.x'
Jan 27 18:53:24 thinkpad dbus[863]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 27 18:53:24 thinkpad dbus[863]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 27 18:56:08 thinkpad rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="942" x-info="http://www.rsyslog.com"] start
Jan 27 18:56:08 thinkpad rsyslogd: rsyslogd's groupid changed to 104
Jan 27 18:56:08 thinkpad rsyslogd: rsyslogd's userid changed to 101
Jan 27 18:56:08 thinkpad kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jan 27 18:56:08 thinkpad kernel: [ 0.000000] Initializing cgroup subsys cpu
Jan 27 18:56:08 thinkpad kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Jan 27 18:56:08 thinkpad kernel: [ 0.000000] Linux version 3.13.0-32-generic (buildd@kissel) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 (Ubuntu 3.13.0-32.57-generic 3.13.11.4)
Jan 27 18:56:08 thinkpad kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=94d57f89-9362-4b77-a5e4-a73e2f799edc ro quiet splash vt.handoff=7
Jan 27 18:56:08 thinkpad kernel: [ 0.000000] KERNEL supported cpus:

Dirk F (fieldhouse) wrote :

The message in /var/log/pm-suspend.log quoted in the report

"Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory"

comes from the wpa_supplicant sleep hook. This hook shouldn't be run when NetworkManager is operating, since NM handles sleep and resume DBus notifications itself. More often than not, the result of the race between the two is a half-working network that appears from the GUI to be working but actually isn't and has to be fixed by disabling and re-enabling Networking.

At any rate it isn't connected with the original problem.

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

Other bug subscribers