Bug 1917622

Summary: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
Product: [Fedora] Fedora Reporter: Török Edwin <edwin+bugs>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, itamar, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 18:16:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg.txt
none
dmesg output for an occurrence of the bug none

Description Török Edwin 2021-01-18 23:47:46 UTC 
1. Please describe the problem:
I try to suspend the system, but instead of suspending the monitors turn off and the system stays on.
There is an amdgpu error in the kernel logs (see below).
I suspend my computer daily, and this issue happens quite rarely (journalctl can only find one instance in its history,
so it happened only once since November)

2. What is the Version-Release number of the kernel:
5.9.16-200.fc33.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Hard to tell when it first appeared, it is a rare issue

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

* press Suspend in the Poweroff/Logout menu in Gnome or lockscreen
* monitors turn off, but the system stays on (I can hear the fans)
* have to hard reboot the system with the reset button
* after reboot I see the resume error in journalctl, apparently it failed to suspend halfway through,
then tried to resume and it failed

Since Nov 27 (journalctl doesn't go back further than that) this issue only happened once, but I remember
that it happened around 3 times since I'm using Fedora 33.

Looking at the logs from last there weren't too many crashes on suspend:
$ last|grep crash
edwin-wo tty8         tty8             Mon Jan  4 08:48 - crash (6+14:58)
edwin    :0           :0               Thu Dec 31 11:34 - crash (10+12:12)
... these 2 are the same crash, just different logins ...

edwin    tty2         tty2             Fri Dec 18 21:44 - crash (5+15:01)
... here the resume was succesful, so maybe it wasn't amdgpu that crashed

edwin-wo tty3         tty3             Mon Sep 21 09:08 - crash (5+03:35)
edwin    tty2         tty2             Mon Sep 21 09:08 - crash (5+03:35)
... these 2 again the same crash, but I haven't got logs for it anymore

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

I'm running 5.10.7-200.fc33.x86_64 now, which is the latest Fedora 33 kernel, 
will reply here if the problem occurs again.
I don't have a reliable repro, so trying the rawhide kernel wouldn't necessarily give a useful datapoint.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Comment 1 Török Edwin 2021-01-18 23:55:07 UTC 
Created attachment 1748595 [details]
dmesg.txt

Jan 10 23:41:00 storm-broadband kernel: Disabling non-boot CPUs ...
Jan 10 23:41:00 storm-broadband kernel: Wakeup pending. Abort CPU freeze
Jan 10 23:41:00 storm-broadband kernel: Non-boot CPUs are not disabled
Jan 10 23:41:00 storm-broadband kernel: ACPI: Waking up from system sleep state S3
Jan 10 23:41:00 storm-broadband kernel: serial 00:04: activated
Jan 10 23:41:00 storm-broadband kernel: sd 2:0:0:0: [sda] Starting disk
Jan 10 23:41:00 storm-broadband kernel: sd 3:0:0:0: [sdb] Starting disk
Jan 10 23:41:00 storm-broadband kernel: sd 4:0:0:0: [sdc] Starting disk
Jan 10 23:41:00 storm-broadband kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000000000).
Jan 10 23:41:00 storm-broadband kernel: [drm] PSP is resuming...
Jan 10 23:41:00 storm-broadband kernel: nvme nvme1: Shutdown timeout set to 8 seconds
Jan 10 23:41:00 storm-broadband kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Jan 10 23:41:00 storm-broadband kernel: nvme nvme2: 7/0/0 default/read/poll queues
Jan 10 23:41:00 storm-broadband kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jan 10 23:41:00 storm-broadband kernel: [drm] reserve 0x900000 from 0x800f400000 for PSP TMR
Jan 10 23:41:00 storm-broadband kernel: nvme nvme1: 32/0/0 default/read/poll queues
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x00000036, smu fw if version = 0x00000037, smu fw version = 0x002a3d00 (42.61.>
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched
Jan 10 23:41:00 storm-broadband kernel: usb 1-2: reset low-speed USB device number 3 using xhci_hcd
Jan 10 23:41:00 storm-broadband kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 10 23:41:00 storm-broadband kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 10 23:41:00 storm-broadband kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 10 23:41:00 storm-broadband kernel: ata5.00: configured for UDMA/133
Jan 10 23:41:00 storm-broadband kernel: ata4.00: configured for UDMA/133
Jan 10 23:41:00 storm-broadband kernel: ata3.00: configured for UDMA/133
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: failed send message:     RunBtc (58)         param: 0x00000000 response 0xffffffc2
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: RunBtc failed!
Jan 10 23:41:00 storm-broadband kernel: amdgpu 0000:0c:00.0: amdgpu: Failed to setup smc hw!
Jan 10 23:41:00 storm-broadband kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
Jan 10 23:41:00 storm-broadband kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-62).
Jan 10 23:41:00 storm-broadband kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -62
Jan 10 23:41:00 storm-broadband kernel: PM: Device 0000:0c:00.0 failed to resume async: error -62
Jan 10 23:41:00 storm-broadband kernel: PM: resume devices took 2.385 seconds
Comment 2 Martin 2021-03-16 20:59:08 UTC 
Created attachment 1763781 [details]
dmesg output for an occurrence of the bug
Comment 3 Martin 2021-03-16 20:59:49 UTC 
This happened to me today. The computer was still running, but the displays and peripherals (keyboard, etc) also seemed to be "off" (LEDs for scroll lock, num lock, caps lock would not illuminate), and I had to reset the system.

In the BIOS settings, "Above 4G Decoding" and SR-IOV support were enabled.

dmesg output attached to this bug as "dmesg_martin.txt".

OS: Fedora 33
Mesa 20.3.4-2.fc33

CPU: AMD Ryzen 5 3600X
Graphics Card: AMD Radeon RX 5700
Motherboard: ASUS Pro WS X570-ACE (BIOS version 3302, AGESA 1.2.0.1)
Memory: Crucial Ballistix Elite 4x8GB DDR4 3600MHz
Internal Storage: Crucial P1 1TB 3D NAND NVMe PCIe M.2 SSD
PSU: Seasonic PRIME Ultra 1000 Titanium
Comment 4 Martin 2021-03-16 21:01:22 UTC 
Forgot to mention, this happened to me using kernel 5.10.22-200.fc33.x86_64.
Comment 5 Ben Cotton 2021-11-04 14:54:46 UTC 
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Ben Cotton 2021-11-04 15:53:21 UTC 
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 7 Ben Cotton 2021-11-30 18:16:39 UTC 
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.