System freeze on attempt to suspend

[David Burke]

1. New install of 17.10 beta 2 on XPS 13 9350. Intel gpu and using wayland (enabled by default)
2. Select top right menu, hold alt, select suspend button

I expect the laptop to suspend. Instead the screen goes blank. The laptop remained on (power button is light, fans are on). The laptop is unresponsive until hard reboot (holding down power button). A suspended state is never reached.

The laptop previously suspended fine on 17.04.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic]
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: david 1388 F...m pulseaudio
 /dev/snd/controlC0: david 1388 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 30 12:18:05 2017
InstallationDate: Installed on 2017-09-30 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: Dell Inc. XPS 13 9350
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=a7e24755-5141-4ab1-a8d4-e4da5ebfe9ce ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic N/A
 linux-firmware 1.168
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 09JHRY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: NULL
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc3

[David Burke (bufke)]

I am now having trouble reproducing it. I see someone marked it affects them too. I'll try again tonight. If I can find steps to replicate it, I'll try the newer kernel.

[Harag (zaries)]

FYI, I also had suspend issues (Aspire E5-575G-53WP), after suspend (not sure if it was proper suspend) I could log in but system was only semi responsive, restart hanged, had to hard boot with power button. The mailine kernel fixed that (suspend issue and restart hanging) but introduced a networking issue leaving me without internet.

[David Burke (bufke)]

I can't reproduce this for the life of me now. Should it be closed? Harag's issue sounds like something else.

[Bereon Burns-Zimmerman (doctormaniac)]

I have reproduced the same suspend and reboot issues that Harag talks about on my laptop (Acer Aspire E5-575G-53VG). I'm not really sure what the cause is, but I have tested several distributions of Linux last month, and I have run into no issues with suspend or reboot. Arch Linux and Antergos could suspend and reboot without issue a couple of weeks ago, and now that I have decided to reinstall them, I run into suspend and reboot issues. The most interesting thing that I have tested was the live media. If you were to boot Ubuntu 17.10's with a bootable USB stick(on my laptop), and immediately decide to reboot, you won't run into any issues. However, if you boot into the bootable USB stick, connect to the WiFi, and then decide to reboot, then the computer will hang. The same thing happens with the Antergos bootable USB.

[David Burke (bufke)]

I had it crash again, this time when just closing the lid (leaving the computer turned on and melting). I've found that every time I try to reproduce it - it works great. Everytime I suspend in the wild - it fails. :(

If I find a way to reproduce it - I'll try the new kernel.

[Harag (zaries)]

I did some more testing:
Scenario 1:

1. Boot and loggin
2. Close lid
3. Wait a second or two
4. Open lid and get a black screen
5. Laptop seems unresponsive but pressing power button once every couple of seconds finally gets me login screen.

Scenario 2:

1. Boot and loggin
2. Close lid
3. Wait a minute or more
4a. Open lid and get login that is unresponsive, press power button once to get responsive loggin
4b. Open lid and login

With both scenarios once you are logged in you cant open any applications but terminal but the terminal will only run some commands like ls, if you try sudo tail -f -n40 /var/log/syslog it just hangs up and Ctrl C wont exit the command you have to close the terminal and reopen.

I have syslog sections for before and after suspend freeze

Here are some snippets:

Oct 10 17:18:14 golumn systemd-sleep[1676]: 'SUSPEND' command timed out.
Oct 10 17:18:14 golumn systemd-sleep[1677]: /lib/systemd/system-sleep/wpasupplicant failed with error code 254.
Oct 10 17:18:14 golumn systemd-sleep[1676]: Suspending system...
Oct 10 17:18:14 golumn kernel: [ 80.234679] PM: Syncing filesystems ... done.
Oct 10 17:18:14 golumn kernel: [ 80.244854] PM: Preparing system for sleep (mem)
Oct 10 17:18:34 golumn kernel: [ 80.247130] Freezing user space processes ...
Oct 10 17:18:34 golumn kernel: [ 100.254362] Freezing of tasks failed after 20.004 seconds (9 tasks refusing to freeze, wq_busy=0):

Oct 10 17:18:34 golumn kernel: [ 100.255894] whoopsie D 0 1186 1 0x00000004
Oct 10 17:18:34 golumn kernel: [ 100.255899] Call Trace:
Oct 10 17:18:34 golumn kernel: [ 100.255908] __schedule+0x28b/0x890
Oct 10 17:18:34 golumn kernel: [ 100.255917] schedule+0x36/0x80
Oct 10 17:18:34 golumn kernel: [ 100.255924] schedule_preempt_disabled+0xe/0x10
Oct 10 17:18:34 golumn kernel: [ 100.255932] __mutex_lock.isra.2+0x190/0x4e0
Oct 10 17:18:34 golumn kernel: [ 100.255941] ? __kmalloc_node_track_caller+0x1ea/0x2a0
Oct 10 17:18:34 golumn kernel: [ 100.255950] __mutex_lock_slowpath+0x13/0x20
Oct 10 17:18:34 golumn kernel: [ 100.255957] ? __mutex_lock_slowpath+0x13/0x20
Oct 10 17:18:34 golumn kernel: [ 100.255965] mutex_lock+0x2f/0x40
Oct 10 17:18:34 golumn kernel: [ 100.255970] rtnetlink_rcv+0x19/0x30
Oct 10 17:18:34 golumn kernel: [ 100.255975] netlink_unicast+0x18e/0x220
Oct 10 17:18:34 golumn kernel: [ 100.255981] netlink_sendmsg+0x2c5/0x3c0
Oct 10 17:18:34 golumn kernel: [ 100.255991] sock_sendmsg+0x38/0x50
Oct 10 17:18:34 golumn kernel: [ 100.255995] SYSC_sendto+0x13f/0x180
Oct 10 17:18:34 golumn kernel: [ 100.256003] ? ktime_get_ts64+0x4e/0xe0
Oct 10 17:18:34 golumn kernel: [ 100.256009] SyS_sendto+0xe/0x10
Oct 10 17:18:34 golumn kernel: [ 100.256015] entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct 10 17:18:34 golumn kernel: [ 100.256018] RIP: 0033:0x7fbef23a0bdf
Oct 10 17:18:34 golumn kernel: [ 100.256020] RSP: 002b:00007ffce2581080 EFLAGS: 00000246

Oct 10 17:19:49 golumn dbus-daemon[1007]: Successfully activated service 'org.gnome.Nautilus'
Oct 10 17:19:49 golumn nautilus[1814]: g_key_file_load_from_file: assertion 'file != NULL' failed
Oct 10 17:19:49 golumn nautilus[1814]: Could not establish a conne...

[Harag (zaries)]

Tried Mainline 4.14rc4 tonight and I can not reproduce this problem. (if you have network issues on 4.14rc as a quick hack you can disable apparmor). So for me this is a work around for the next couple of days at least.

[Kai-Heng Feng (kaihengfeng)]

Did you plug docking station, or anything thunderbolt related?

[Harag (zaries)]

No docking station not thunderbolt.

Did the tests with the laptop, usb mouse and usb keybord.

[venturia (alessandro-venturini)]

I don't know if the issue is exactly the same but on my desktop the suspend resume cycle doesn't work properly.

1. New install of 17.10 beta 2 on Packard Bell IMedia 5204. Nvidia gpu and using wayland (enabled by default)
2. Select top right menu, hold alt, select suspend button. The desktop goes in "suspend" state (power button is light on suspend, fans are off).

When try to resume pushing the power button, I've black screen, hard disk spinning forever and desktop doesn't resume.

I can't any crash reported in /var/crash related to this issue.

There is anything I can do to help in debug?

[solax (solax76)]

I have a different system (DELL Latitude E6510) with NVIDIA graphic card, but same error.
I've tried with kernel v4.14-rc8 and this issue is solved, systems seems to work correctly.

[Kai-Heng Feng (kaihengfeng)]

Does the new kernel from artful-proposed have the issue?

[Ben Dischinger (ben.dischinger)]

I've also been seeing this issue on my Dell Inspiron laptop since upgrading to 17.10.

Here is the journalctl -r output where the issue occurs for me.

Nov 12 20:07:50 ben-Inspiron-15-3567 gnome-session[11603]: gnome-session-binary[11603]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Nov 12 20:07:50 ben-Inspiron-15-3567 org.gnome.Shell.desktop[11669]: (EE)
Nov 12 20:07:50 ben-Inspiron-15-3567 org.gnome.Shell.desktop[11669]: (EE) failed to read Wayland events: Connection reset by peer
Nov 12 20:07:50 ben-Inspiron-15-3567 org.gnome.Shell.desktop[11669]: Fatal server error:
Nov 12 20:07:50 ben-Inspiron-15-3567 org.gnome.Shell.desktop[11669]: (EE)
Nov 12 20:07:50 ben-Inspiron-15-3567 systemd-sleep[13189]: Suspending system...
Nov 12 20:07:50 ben-Inspiron-15-3567 systemd-sleep[13190]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Nov 12 20:07:50 ben-Inspiron-15-3567 systemd-sleep[13189]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
Nov 12 20:07:50 ben-Inspiron-15-3567 systemd[1]: Starting Suspend...
Nov 12 20:07:50 ben-Inspiron-15-3567 systemd[1]: Reached target Sleep.
Nov 12 20:07:50 ben-Inspiron-15-3567 update-notifier[12482]: Error reading events from display: Broken pipe
Nov 12 20:07:50 ben-Inspiron-15-3567 nixnote2[12021]: Error reading events from display: Broken pipe
Nov 12 20:07:50 ben-Inspiron-15-3567 blueman-applet[12039]: Error reading events from display: Broken pipe
Nov 12 20:07:50 ben-Inspiron-15-3567 kernel: gnome-shell[11669]: segfault at 0 ip 00007f88d76a884c sp 00007ffc047e1d30 error 4 in libmutter-1.so.0.0.0[7f88d7
Nov 12 20:07:49 ben-Inspiron-15-3567 kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_AML_MUTEX_NOT_ACQUIRED (20170531/psparse-
Nov 12 20:07:49 ben-Inspiron-15-3567 kernel: ACPI Error: Cannot release Mutex [PATM], not acquired (20170531/exmutex-393)

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]