[amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
suspend to ram crashes amdgpu.
System is still accessible via SSH after resume from standby.
Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped.
Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH.
I'll attach the dmesg output of several attempts.
This is the hardware:
https:/
Tested EFI and BIOS bootmode.
Please let me know if I can help tracking this down.
I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-)
Workaround:
Enable hibernation (suspend to disk) and use instead of suspend to ram (standby).
What didn't help:
Kernel parameters: no_console_suspend nomodeset amdgpu.
echo mem > /sys/power/state
systemctl start suspend.target
echo 0 > /sys/power/pm_async
Upgrading kernel from 5.4 to: 5.6.0-1010-oem
Using the kernel parameters
no_console_
idle=nowait amd_iommu=flush
and doing
echo mem > /sys/power/state
before suspend made the system acutally not crash.
Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either.
I'll try to find the minimal combination of kernel parameters.
nomodeset seems to be essential, but not sufficient.
Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.6.0-1010-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 31 18:43:54 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingI
GpuHangFrequency: Continuously
GpuHangReproduc
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Picasso [103c:85de]
InstallationDate: Installed on 2020-05-29 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ENVY x360 Convertible 13-ar0xxx
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.19
dmi.board.
dmi.board.name: 85DE
dmi.board.vendor: HP
dmi.board.version: 41.36
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.
dmi.modalias: dmi:bvnAMI:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx
dmi.product.sku: 9YN58EA#ABD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.