Waking from Suspend causes screen to appear with grey static (like a TV with no signal)

[Craig Stein]

I am running Kubuntu 18.10. This is the PH517-61 Acer Predator Helios 500 with the Ryzen processor. My first issue I need to deal with is Suspend. I have temporarily disabled suspend in the kcmshell5 configuration. If I do let the laptop suspend and then hit the keyboard I get what appears to be a 1950s TV with no signal. At this point I manually power down and then power up again and am able to view things on screen.

Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support

$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54 CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

$ uname -a
Linux craig-Predator-PH517-61 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

This is a Vega 56 card but Kubuntu seems to think it is a Vega 64:
$ lspci -k | grep -EA3 'VGA|3D|Display'
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c7)
Subsystem: Acer Incorporated [ALI] Vega 10 XT [Radeon RX Vega 64]
Kernel driver in use: amdgpu
Kernel modules: amdgpu

$ glxinfo | grep "OpenGL version"
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2

I will attempt to flesh this out more when I get home.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: craig 2094 F.... pulseaudio
 /dev/snd/controlC0: craig 2094 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2019-01-28 (1 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
MachineType: Acer Predator PH517-61
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=5f69d6c1-716a-41ac-a88c-b271a71ce5a0 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-13-generic N/A
 linux-backports-modules-4.18.0-13-generic N/A
 linux-firmware 1.175.1
Tags: cosmic
Uname: Linux 4.18.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/12/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Cayman_PRS
dmi.board.vendor: PRS
dmi.board.version: V1.07
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd10/12/2018:svnAcer:pnPredatorPH517-61:pvrV1.07:rvnPRS:rnCayman_PRS:rvrV1.07:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Predator Helios 500
dmi.product.name: Predator PH517-61
dmi.product.sku: 0000000000000000
dmi.product.version: V1.07
dmi.sys.vendor: Acer

[Craig Stein (whitebunnyflock)]

Expected Behaviour:
I expect to continue to be able to use my machine normally and be able to see what is happening on screen.

Actual Behaviour:
Static on screen obscures everything.

[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 1813820

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.

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Craig Stein (whitebunnyflock)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc4 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] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc4/

[Craig Stein (whitebunnyflock)]

$ uname -a
Linux craig-Predator-PH517-61 5.0.0-050000rc4-generic #201901272036 SMP Mon Jan 28 01:38:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Suspend to ram still results in gibberish on the screen with the latest upstream kernel. Confirmed bug and added tag kernel-bug-exists-upstream.

Please let me know what steps to take next.

[Kai-Heng Feng (kaihengfeng)]

It's a Vega 10 graphics, so please also test AMDGPU firmware in linux-firmwares [1].

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

[Craig Stein (whitebunnyflock)]

took the following steps:
Went to https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
Downloaded the master branch which was uploaded 5 days ago by Josh Boyer
Backup my current firmware: sudo cp -r /lib/firmware /lib/firmware-$(uname -r)
tar -xvzf linux-firmware-master.tar.gz
CD into the resulting directory
sudo make install
mkdir -p /lib/firmware
sudo cp -r * /lib/firmware
sudo find /lib/firmware \( -name 'WHENCE' -or -name 'LICENSE.*' -or -name 'LICENCE.*' \) -exec rm -- {} \;

Rebooted and tried to suspend. Still have the same result as above. Let me know if I did any of this incorrectly.

[Craig Stein (whitebunnyflock)]

today tried another new kernel with the same result, still the screen produces garbage after resuming from suspend. This was the kernel used: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/

should i report this upstream to bugzilla? should mention i also switched from Kubuntu 18.10 to Ubuntu 18.10..

uname -a

5.0.2-050002-generic #201903131832 SMP Wed Mar 13 22:35:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[Kai-Heng Feng (kaihengfeng)]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

[Kai-Heng Feng (kaihengfeng)]

Also please attach `journalctl -b -1 -k`.

[Craig Stein (whitebunnyflock)]

here is the output of 'journalctl -b -1 -k'

[Kai-Heng Feng (kaihengfeng)]

Sorry I didn't make it explicit - please reproduce the issue, reboot, then attach 'journalctl -b -1 -k'.

[Craig Stein (whitebunnyflock)]

ok produced this with the correct steps this time

[Kai-Heng Feng (kaihengfeng)]

I don't see any error after the resume. The system is apparently alive, so it's more likely to ba graphics driver issue.

Please follow comment #23, to let upstream maintainer debug this.

[Craig Stein (whitebunnyflock)]

Reported here: https://bugs.freedesktop.org/show_bug.cgi?id=110117

[Craig Stein (whitebunnyflock)]

tested the kernel from here today with the same result: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/

generic amd64

[Craig Stein (whitebunnyflock)]

if by chance this is an Acer UEFI bug is there somewhere else I could report it? either in launchpad or upstream?

[Craig Stein (whitebunnyflock)]

today I started to follow the steps here: https://wiki.ubuntu.com/DebuggingKernelSuspend

I found this in the dmesg after replicating the problem with pm_trace

[ 0.950964] Magic number: 0:66:1001
[ 0.950965] hash matches drivers/base/power/main.c:1012

Is there more going on here perhaps than a video driver? Not sure what else to do with this information.

[jman6495 (jman6495)]

Similar issues on the HP Envy 13 x360 (Ryzen 3500U)

I've attached the dmesg of a an attempted suspend.

Could be related to:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842785
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1849084