Dell Precision 3560: system hang upon resume from s2idle suspend

[Brian J. Cohen]

On a Dell Precision 3560 with all-Intel graphics (no Nvidia). The machine will successfully go into s2idle suspend (sleep) but upon waking, the system will immediately freeze hard. In its frozen state, the mouse pointer will be visible against a black screen. Here are the troubleshooting steps I have taken so far:

- Can successfully reproduce under Ubuntu 20.04.2 (gdm3), Kubuntu 20.04.2 (sddm). For what it's worth, I can also reproduce this under Manjaro (stable), so it's conceivable this is a kernel bug.

- There's some evidence online that this issue, or something similar, was introduced in/around kernel 5.6.19 -- I have not been able to get Ubuntu to boot under a kernel earlier than 5.8 so I cannot confirm this.

- Updated BIOS to latest (1.6). 'Block sleep' is off. System > SATA is 'AHCI'. Post Behavior > Fastboot is 'Thorough'. Secure Boot is disabled.

- Determined that this BIOS does not appear to support 'deep' sleep, only s2idle.

- The problem does NOT occur if I boot to an Ubuntu 20.04.2 live USB disk. I compared the drivers that are loaded in that environment vs. those that are loaded under the installed OS and did not notice anything suspicious.

I am happy to supply any diagnostics or logs that are requested.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: brian 916 F.... pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-05-16 (0 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: Dell Inc. Precision 3560
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=03c4b3bd-b521-45b0-b01d-cd092ba108bc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-53-generic N/A
 linux-backports-modules-5.8.0-53-generic N/A
 linux-firmware 1.187.12
Tags: focal
Uname: Linux 5.8.0-53-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/19/2021
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 063MV5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd04/19/2021:br1.6:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn063MV5:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3560
dmi.product.sku: 0A22
dmi.sys.vendor: Dell Inc.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1928593/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1928593

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[Brian J. Cohen (brianjcohen)]

apport information

[koba (kobako)]

@Brian,
please try oem kernel, thanks
sudo apt update;sudo apt install linux-image-unsigned-5.10.0-1027-oem linux-headers-5.10.0-1027-oem

If the issue still can be observed, please reboot it and collect the journalctl log
#journalctl -k -b -1

[Brian J. Cohen (brianjcohen)]

@koba,

Funny you should mention that. I actually did yesterday try the 5.6.0-1032-oem kernel because that is the one that this machine was apparently certified under as documented here:
https://certification.ubuntu.com/hardware/202010-28315

And, sure enough, suspend mostly works under this kernel. Or, at least, it properly wakes from suspend.

I was not able to install linux-image-unsigned-5.10.0-1027-oem because it is not yet available in the respositories (even after 'apt update') but I installed linux-image-unsigned-5.10.0-1026-oem and I *am* able to reproduce the problem under this kernel. When I tried to resume from suspend, the mouse cursor was visible against a black screen and the machine was frozen. I restarted by holding down the power button and booted back into 5.6.0-1032-oem and ran journalctl -k -b -1, which I've attached.

[koba (kobako)]

@Brian,
would you mind helping me try this cmd? then please s2idle&resume.
*echo 0|sudo tee /sys/bus/pci/devices/*/d3cold_allowed

please also provide dmesg. thanks