[SOLVED] Laptop reboots on suspend - only on battery!

OdinEidolon · 2016-12-31 10:19:09

tl;dr: my laptop boots from zero when waking from suspend, but only if on battery.
EDIT: the same problem is present in Windows and I suspect started when I bumped the RAM to 32GB. So it's a Dell BIOS / hardware issue, it seems...

I have a Dell XPS15 9550 (see signature).
Since a few days ago it started behaving strangely with suspend: if I suspend the laptop when on AC, all is fine.
If I unplug it from the wall, then try to suspend (with any method), it successfully suspends, but when trying to wake it up it just reboots, as if it was turned off. If the lid is closed, opening it is sufficient to make it boot from zero.

This happens no matter if I try to suspend with `systemctl suspend`, or via Plasma, or by closing the lid (which is also handled by Plasma).
Here is my logind.conf (only showing non-defaults settings):

[Login]
HandleLidSwitch=ignore
LidSwitchIgnoreInhibited=no
RuntimeDirectorySize=20%

This is an example systemd journal tail for a on-battery suspend, which seems to go well:

Dec 31 10:55:36 XPS15af org_kde_powerdevil[626]: powerdevil: Suspend session trigger
Dec 31 10:55:36 XPS15af kdeconnectd[576]: kdeconnect.core: Broadcasting identity pac
Dec 31 10:55:36 XPS15af org_kde_powerdevil[626]: powerdevil: Suspend session trigger
Dec 31 10:55:36 XPS15af org_kde_powerdevil[626]: powerdevil: Starting Login1 suspend
Dec 31 10:55:36 XPS15af kded5[532]: kscreen.kded: System is going to suspend, won't 
Dec 31 10:55:36 XPS15af ksmserver[558]: lock called
Dec 31 10:55:36 XPS15af kded5[532]: bluedevil: About to suspend
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.3992] manager: slee
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.3992] manager: slee
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.3994] manager: Netw
Dec 31 10:55:36 XPS15af nm-dispatcher[1272]: req:3 'connectivity-change': new reques
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4013] device (wlp2s
Dec 31 10:55:36 XPS15af nm-dispatcher[1272]: req:3 'connectivity-change': start runn
Dec 31 10:55:36 XPS15af ksmserver[558]: Lock window Id:  18874378
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 18874378
Dec 31 10:55:36 XPS15af ksmserver[558]: UnmapNotify: 18874378
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4180] device (wlp2s
Dec 31 10:55:36 XPS15af kded5[532]: plasma-nm: Unhandled active connection state cha
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 12582915
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4506] dhcp4 (wlp2s0
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4506] dhcp4 (wlp2s0
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4527] dhcp6 (wlp2s0
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4527] dhcp6 (wlp2s0
Dec 31 10:55:36 XPS15af wpa_supplicant[381]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=3
Dec 31 10:55:36 XPS15af kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp ip
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4577] dns-mgr: Remo
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 12582919
Dec 31 10:55:36 XPS15af nm-dispatcher[1272]: req:4 'down' [wlp2s0]: new request (2 s
Dec 31 10:55:36 XPS15af nm-dispatcher[1272]: req:4 'down' [wlp2s0]: start running or
Dec 31 10:55:36 XPS15af NetworkManager[357]: <warn>  [1483178136.4850] sup-iface[0x2
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4852] device (wlp2s
Dec 31 10:55:36 XPS15af kded5[532]: plasma-nm: Not emitting connection deactivated n
Dec 31 10:55:36 XPS15af NetworkManager[357]: <info>  [1483178136.4862] device (wlp2s
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 12582924
Dec 31 10:55:36 XPS15af ntpd[1320]: ntpd exiting on signal 15 (Terminated)
Dec 31 10:55:36 XPS15af systemd[1]: Stopping Network Time Service...
Dec 31 10:55:36 XPS15af ntpd[1320]: 212.45.144.3 local addr 192.168.1.107 -> <null>
Dec 31 10:55:36 XPS15af ntpd[1320]: 31.14.131.188 local addr 192.168.1.107 -> <null>
Dec 31 10:55:36 XPS15af ntpd[1320]: 2.228.72.62 local addr 192.168.1.107 -> <null>
Dec 31 10:55:36 XPS15af ntpd[1320]: 213.251.52.250 local addr 192.168.1.107 -> <null
Dec 31 10:55:36 XPS15af systemd[1]: Stopped Network Time Service.
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: file:///usr/share/plasma/wallpape
Dec 31 10:55:36 XPS15af systemd[1]: Stopping OpenSSH Daemon...
Dec 31 10:55:36 XPS15af sshd[1326]: Received signal 15; terminating.
Dec 31 10:55:36 XPS15af systemd[1]: Stopped OpenSSH Daemon.
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No file found for ".xml" , even t
                                                   Either it was just removed, or th
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No file found for ".xml" , even t
                                                   Either it was just removed, or th
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 12582926
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 12582928
Dec 31 10:55:36 XPS15af ksmserver[558]: MapNotify: 12582926
Dec 31 10:55:36 XPS15af ksmserver[558]: MapNotify: 18874378
Dec 31 10:55:36 XPS15af ksmserver[558]: CreateNotify: 12582930
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No metadata file in the package, 
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No metadata file in the package, 
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No metadata file in the package, 
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No metadata file in the package, 
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No metadata file in the package, 
Dec 31 10:55:36 XPS15af kscreenlocker_greet[1351]: No metadata file in the package, 
Dec 31 10:55:37 XPS15af wpa_supplicant[381]: nl80211: deinit ifname=p2p-dev-wlp2s0 d
Dec 31 10:55:37 XPS15af kded5[532]: networkmanager-qt: virtual void NetworkManager::
Dec 31 10:55:37 XPS15af plasmashell[579]: networkmanager-qt: virtual void NetworkMan
Dec 31 10:55:37 XPS15af kded5[532]: networkmanager-qt: virtual void NetworkManager::
Dec 31 10:55:37 XPS15af plasmashell[579]: networkmanager-qt: virtual void NetworkMan
Dec 31 10:55:37 XPS15af kernel: brcmfmac: brcmf_cfg80211_escan_handler: scan not rea
Dec 31 10:55:37 XPS15af kernel: brcmfmac: brcmf_fweh_event_worker: event handler fai
Dec 31 10:55:37 XPS15af wpa_supplicant[381]: nl80211: deinit ifname=wlp2s0 disabled_
Dec 31 10:55:37 XPS15af systemd[1]: Reached target Sleep.
Dec 31 10:55:37 XPS15af systemd[1]: Starting Suspend...
Dec 31 10:55:37 XPS15af systemd-sleep[1415]: Suspending system...

And the following try-to-unsuspend-but-reboots is:

Dec 31 10:56:04 localhost kernel: Linux version 4.8.15-2-ck-skylake (squishy@ease) (
Dec 31 10:56:04 localhost kernel: Command line: \vmlinuz-linux-ck-skylake rw root=UU
Dec 31 10:56:04 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floa
Dec 31 10:56:04 localhost kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE regi
Dec 31 10:56:04 localhost kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX regi
Dec 31 10:56:04 localhost kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX boun
Dec 31 10:56:04 localhost kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Dec 31 10:56:04 localhost kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]: 
Dec 31 10:56:04 localhost kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]: 
Dec 31 10:56:04 localhost kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]: 
Dec 31 10:56:04 localhost kernel: x86/fpu: Enabled xstate features 0x1f, context siz
Dec 31 10:56:04 localhost kernel: x86/fpu: Using 'eager' FPU context switches.
Dec 31 10:56:04 localhost kernel: e820: BIOS-provided physical RAM map:
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000000
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000000001000-0x0000000000057
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009c
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x000000000009d000-0x000000000009f
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000271a1
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000271a2000-0x00000000271a2
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000271a3000-0x00000000271cc
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000271cd000-0x0000000027223
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000027224000-0x0000000027a14
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000027a15000-0x0000000038ab9
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000038aba000-0x0000000038e31
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000038e32000-0x0000000038e83
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000038e84000-0x00000000397f5
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000397f6000-0x000000003a4fe
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x000000003a4ff000-0x000000003a4ff
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x000000003a500000-0x000000003a5ff
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000effff
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000fffff
Dec 31 10:56:04 localhost kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008bdfff
Dec 31 10:56:04 localhost kernel: NX (Execute Disable) protection: active
Dec 31 10:56:04 localhost kernel: e820: update [mem 0x2150c018-0x21525657] usable ==
Dec 31 10:56:04 localhost kernel: e820: update [mem 0x22a85018-0x22a95057] usable ==
Dec 31 10:56:04 localhost kernel: extended physical RAM map:
Dec 31 10:56:04 localhost kernel: reserve setup_data: [mem 0x0000000000000000-0x0000
Dec 31 10:56:04 localhost kernel: reserve setup_data: [mem 0x0000000000001000-0x0000
Dec 31 10:56:04 localhost kernel: reserve setup_data: [mem 0x0000000000058000-0x0000
Dec 31 10:56:04 localhost kernel: reserve setup_data: [mem 0x0000000000059000-0x0000
Dec 31 10:56:04 localhost kernel: reserve setup_data: [mem 0x000000000009d000-0x0000
........

Which seems pretty normal to me.

The only things that have changed from last time I know it was working are:
- BIOS updated: this may be a cause but I've seen nobody with a similar issue
- EDIT: wait, I think it MAY have started when I bumped the RAM to 32GB. That's another thing that may have changed...
- following packages were updated:

[2016-12-28 09:45] [ALPM] upgraded llvm-libs (3.9.0-3 -> 3.9.1-1)
[2016-12-28 09:45] [ALPM] upgraded gnupg (2.1.17-1 -> 2.1.17-3)
[2016-12-28 09:45] [ALPM] upgraded bluedevil (1:5.8.4-1 -> 1:5.8.5-1)
[2016-12-28 09:45] [ALPM] upgraded kdecoration (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:45] [ALPM] upgraded breeze (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:45] [ALPM] upgraded breeze-gtk (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded python2 (2.7.12-2 -> 2.7.13-1)
[2016-12-28 09:46] [ALPM] upgraded breeze-kde4 (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded curl (7.51.0-3 -> 7.52.1-1)
[2016-12-28 09:46] [ALPM] upgraded drkonqi (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded grep (2.26-1 -> 2.27-1)
[2016-12-28 09:46] [ALPM] upgraded kactivitymanagerd (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kde-cli-tools (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kde-gtk-config (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded libksysguard (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded milou (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kscreenlocker (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kwin (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-integration (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kuiserver (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-workspace (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kdeplasma-addons (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kgamma5 (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded khotkeys (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kinfocenter (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kmenuedit (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded libkscreen (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kscreen (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded ksshaskpass (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded ksysguard (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kwallet-pam (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kwayland-integration (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded kwrited (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded lib32-llvm-libs (3.9.0-1 -> 3.9.1-1)
[2016-12-28 09:46] [ALPM] upgraded mpv (1:0.22.0-2 -> 1:0.23.0-1)
[2016-12-28 09:46] [ALPM] upgraded oxygen (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded pandoc (1.19.1-3 -> 1.19.1-6)
[2016-12-28 09:46] [ALPM] upgraded polkit-kde-agent (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded systemsettings (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-desktop (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-nm (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-pa (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-sdk (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded plasma-workspace-wallpapers (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded powerdevil (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded sddm-kcm (5.8.4-1 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded user-manager (5.8.4-2 -> 5.8.5-1)
[2016-12-28 09:46] [ALPM] upgraded youtube-dl (2016.12.20-1 -> 2016.12.22-1)
[2016-12-28 11:01] [ALPM] upgraded memtest86-efi (7.1-1 -> 7.2-1)

AFAIK nothing that should impact suspend was updated.

I have no modules in mkinitcpio.conf
Hooks are:

HOOKS="systemd autodetect modconf block filesystems fsck"

What could be the cause of this issue?

Last edited by OdinEidolon (2017-01-03 11:12:52)

ugjka · 2016-12-31 10:36:58

You can try disabling pm_async as a first step

sudo bash -c "echo 0 > /sys/power/pm_async"

This solved my hibernation issues

Last edited by ugjka (2016-12-31 10:37:47)

OdinEidolon · 2016-12-31 12:45:14

ugjka wrote:

You can try disabling pm_async as a first step
sudo bash -c "echo 0 > /sys/power/pm_async"
This solved my hibernation issues

No change, but... I just tried in Windows, and IT DOES THE SAME!

So it seems that with my upgraded 32GB or RAM the laptop cannot suspend while on battery. This looks definitely like a bug on Dell's side...

md1flynn · 2017-01-01 12:10:26

Sounds like it's affected by the same Skylake bug:

[url]https://bugzilla.kernel.org/show_bug.cgi?id=108801[/url]

- See if there is a BIOS update available
- Try a BIOS Downgrade

If those don't work, the method that works for me is to take the battery out of the laptop and put it back in and the suspend will work fine unless I do a hard reset by holding the power button.

OdinEidolon · 2017-01-01 12:37:21

md1flynn wrote:

Sounds like it's affected by the same Skylake bug:
[url]https://bugzilla.kernel.org/show_bug.cgi?id=108801[/url]
- See if there is a BIOS update available
- Try a BIOS Downgrade
If those don't work, the method that works for me is to take the battery out of the laptop and put it back in and the suspend will work fine unless I do a hard reset by holding the power button.

However, it happens on Windows too for me, so it might be something different. Yesterday I did a BIOS reset and I tested twice today and it seems to be working... I will continue testing

md1flynn · 2017-01-01 19:39:34

OdinEidolon wrote:

However, it happens on Windows too for me

Yes it's definitely a hardware issue that seems to have different triggers and quirks depending on the brand and model - the common denominator being skylake. Same issue for me, once a hard reset has been done, both Windows and Linux reset when waking from suspend on battery.

OdinEidolon · 2017-01-01 20:16:39

md1flynn wrote:

OdinEidolon wrote:
However, it happens on Windows too for me
Yes it's definitely a hardware issue that seems to have different triggers and quirks depending on the brand and model - the common denominator being skylake. Same issue for me, once a hard reset has been done, both Windows and Linux reset when waking from suspend on battery.

Thank you, that would explain it. I now know to just mess with BIOS resets and hard resets if it starts again, until it is fixed...

Arch Linux

#1 2016-12-31 10:19:09

[SOLVED] Laptop reboots on suspend - only on battery!

#2 2016-12-31 10:36:58

Re: [SOLVED] Laptop reboots on suspend - only on battery!

#3 2016-12-31 12:45:14

Re: [SOLVED] Laptop reboots on suspend - only on battery!

#4 2017-01-01 12:10:26

Re: [SOLVED] Laptop reboots on suspend - only on battery!

#5 2017-01-01 12:37:21

Re: [SOLVED] Laptop reboots on suspend - only on battery!

#6 2017-01-01 19:39:34

Re: [SOLVED] Laptop reboots on suspend - only on battery!

#7 2017-01-01 20:16:39

Re: [SOLVED] Laptop reboots on suspend - only on battery!

Board footer