suspend fails on Dell XPS 9350

Bug #2008992 reported by John Steele Scott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-oem-5.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead it turns off.

Journald output:

Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.3571] manager: sleep: sleep requested (sleeping: no enabled: yes)
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.3575] device (p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mar 02 17:31:53 nugget ModemManager[1061]: <info> [sleep-monitor] system is about to suspend
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.3593] manager: NetworkManager state is now ASLEEP
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.3602] device (wlp58s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=940 comm="/usr/sbin/NetworkManager -->
Mar 02 17:31:53 nugget systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 02 17:31:53 nugget systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DISCONNECTED bssid=6c:70:9f:ea:29:9f reason=3 locally_generated=1
Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.4826] device (wlp58s0): supplicant interface state: completed -> disconnected
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.4834] device (wlp58s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for fe80::7389:c602:b63c:8452 on wlp58s0.
Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv6 with address fe80::7389:c602:b63c:8452.
Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv6 no longer relevant for mDNS.
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.5110] dhcp4 (wlp58s0): canceled DHCP transaction
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.5111] dhcp4 (wlp58s0): activation: beginning transaction (timeout in 45 seconds)
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.5112] dhcp4 (wlp58s0): state changed no lease
Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for 192.168.1.217 on wlp58s0.
Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on interface wlp58s0.IPv4 with address 192.168.1.217.
Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset search domain list.
Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client set default route setting: no
Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv4 no longer relevant for mDNS.
Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset DNS server list.
Mar 02 17:31:53 nugget NetworkManager[940]: <info> [1677740513.5824] device (wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0
Mar 02 17:31:54 nugget systemd[1]: Reached target Sleep.
Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:54 nugget systemd[1]: Starting Record successful boot for GRUB...
Mar 02 17:31:54 nugget systemd[1]: Starting System Suspend...
Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=wlp58s0 disabled_11b_rates=0
Mar 02 17:31:54 nugget systemd[1]: grub-common.service: Deactivated successfully.
Mar 02 17:31:54 nugget systemd[1]: Finished Record successful boot for GRUB.
Mar 02 17:31:54 nugget systemd[1]: Starting GRUB failed boot detection...
Mar 02 17:31:54 nugget systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Mar 02 17:31:54 nugget systemd[1]: Finished GRUB failed boot detection.
Mar 02 17:31:54 nugget systemd-sleep[3429]: Entering sleep state 'suspend'...
Mar 02 17:31:54 nugget kernel: PM: suspend entry (deep)

Suspend was working find when I was running 5.17.0-1021-oem.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1027-oem 5.17.0-1027.28
ProcVersionSignature: Ubuntu 5.17.0-1027.28-oem 5.17.15
Uname: Linux 5.17.0-1027-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Thu Mar 2 17:39:54 2023
InstallationDate: Installed on 2016-07-02 (2434 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: linux-signed-oem-5.17
UpgradeStatus: Upgraded to jammy on 2022-04-19 (317 days ago)

Revision history for this message
John Steele Scott (toojays) wrote :
Revision history for this message
John Steele Scott (toojays) wrote :

Upgrading to linux-image-unsigned-6.2.1-060201-generic_6.2.1-060201.202302251141 did not fix the issue.

Nor did rolling back to 5.17.0-1021-oem.

And along the way I found a log file which showed suspend working one time with 5.17.0-1027-oem.

So now I'm not sure what changed to stop this working. :(

Revision history for this message
John Steele Scott (toojays) wrote :

Changing the BIOS Fastboot option to "Thorough" seems to have got it working again. Not sure why this would be necessary now.

Changed in linux-signed-oem-5.17 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.