You are not logged in.

Pages: 1

#1 2025-07-07 15:01:16

anthqiu
Member
Registered: 2025-07-07
Posts: 2

[amdgpu] failed to resume from S3 suspend (smu failed -62)

Hi community,

I just fresh installed Arch Linux, and noticed that every time when I suspend the system, my discrete GPU (Radeon 6950 XT) would fail to wake up, forcing me to hard-reset the machine.

fastfetch:

                  -`                     qhurc@qhurc-desktop
                 .o+`                    -------------------
                `ooo/                    OS: Arch Linux x86_64
               `+oooo:                   Kernel: Linux 6.15.5-arch1-1
...
           `/++++/+++++++:               Display (MAG274UPF): 3840x2160 @ 144 Hz (as 2560x1440) in 27" [External]
          `/++++++++++++++:              DE: KDE Plasma 6.4.2
         `/+++ooooooooooooo/`            WM: KWin (Wayland)
...
 `+sso+:-`                 `.-/+oso:     CPU: AMD Ryzen 7 7800X3D (16) @ 5.05 GHz
`++:.                           `-/+/    GPU: AMD Radeon RX 6950 XT [Discrete]
.`                                 `/    Memory: 5.22 GiB / 31.00 GiB (17%)
                                         Swap: 0 B / 4.00 GiB (0%)
                                         Disk (/): 9.98 GiB / 294.23 GiB (3%) - ext4
...

journalctl:

GitHub Gist, where I triggered system suspend at line 1792, then the following snippet appeared at line 2670:

Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000006 SMN_C2PMSG_82:0x00000000
Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: amdgpu: Failed to enable requested dpm features!
Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: amdgpu: resume of IP block <smu> failed -62
Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).
Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: PM: dpm_run_callback(): pci_pm_resume returns -62
Jul 07 09:53:21 qhurc-desktop kernel: amdgpu 0000:03:00.0: PM: failed to resume async: error -62

I tried disabling `Global C-State Control` in BIOS and it seemed could suppress this issue, unknowing why. I wanted to see if the community have any insights or could help me collect more information to diagnose where lies the root problem.

Thanks!


====== update ======

I installed my GPU in another machine, tried different BIOS settings and kernel parameters, and did multiple fresh installs of Windows and Arch Linux. I'm almost certain at this point that it must be a hardware issue. After switching to an NVIDIA card, everything is working fine now.

Last edited by anthqiu (2025-07-12 14:27:11)

Offline

#2 2025-07-10 12:27:59

Wereii
Member
Registered: 2024-06-25
Posts: 8

Re: [amdgpu] failed to resume from S3 suspend (smu failed -62)

I believe we are getting the same problem, the closest issue I could find on the freedesktop GL is this, https://gitlab.freedesktop.org/drm/amd/ … te_3000497 , already reported my kernel log there.
There already are some comments about what to try (I haven't had time to try them yet).

For posterity: 
Intel 13900kf, AMD RX 7900 XTX, 64G DDR5, 6.15.5-arch1-1, X11

The important bits of the failure seem to be this (extracted from my last failure):

Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 timeout, signaled seq=913448, emitted seq=913450
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: Starting sdma0 ring reset
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: reset sdma queue (0:0:0)
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: Ring sdma0 reset failure
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
Jul 10 10:59:12 pc-linux kernel: amdgpu 0000:03:00.0: amdgpu: Failed to disallow df cstate
Jul 10 10:59:12 pc-linux kernel: ------------[ cut here ]------------
Jul 10 10:59:12 pc-linux kernel: WARNING: CPU: 7 PID: 90482 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:631 amdgpu_irq_put+0x46/0x70 [amdgpu]
Jul 10 10:59:12 pc-linux kernel: Modules linked in: nft_masq nft_ct nft_reject_ipv4 nf_reject_ipv4 nft_reject act_csum cls_u32 sch_htb bridge stp llc xt_MASQUERADE xt_tcpudp xt_mark nft_compat nft_chain_nat rpcsec_gss_krb5 nf_nat n>
Jul 10 10:59:12 pc-linux kernel:  snd_soc_core intel_powerclamp snd_compress coretemp ac97_bus amdxcp snd_hda_codec_hdmi mac80211 snd_pcm_dmaengine gpu_sched kvm_intel drm_panel_backlight_quirks snd_hda_intel drm_buddy libarc4 snd_>
Jul 10 10:59:12 pc-linux kernel:  sha512_ssse3 sha256_ssse3 nvme sha1_ssse3 aesni_intel nvme_core crypto_simd spi_intel_pci cryptd nvme_keyring spi_intel nvme_auth video wmi
Jul 10 10:59:12 pc-linux kernel: CPU: 7 UID: 0 PID: 90482 Comm: kworker/u128:77 Tainted: G           OE       6.15.5-arch1-1 #1 PREEMPT(full)  d4bfd61c9343a8a5cd6331b14f20b7f081e8650a
Jul 10 10:59:12 pc-linux kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Jul 10 10:59:12 pc-linux kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E07/PRO Z790-A WIFI (MS-7E07), BIOS A.E0 09/30/2024
Jul 10 10:59:12 pc-linux kernel: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]
Jul 10 10:59:12 pc-linux kernel: RIP: 0010:amdgpu_irq_put+0x46/0x70 [amdgpu]
Jul 10 10:59:12 pc-linux kernel: Code: c0 74 33 48 8b 4e 10 48 83 39 00 74 29 89 d1 48 8d 04 88 8b 08 85 c9 74 11 f0 ff 08 74 07 31 c0 c3 cc cc cc cc e9 5a fd ff ff <0f> 0b b8 ea ff ff ff c3 cc cc cc cc b8 ea ff ff ff c3 cc cc cc cc
Jul 10 10:59:12 pc-linux kernel: RSP: 0000:ffffcf2349d13c38 EFLAGS: 00210246
Jul 10 10:59:12 pc-linux kernel: RAX: ffff8a5481eeb5b0 RBX: ffff8a5538800000 RCX: 0000000000000000
Jul 10 10:59:12 pc-linux kernel: RDX: 0000000000000000 RSI: ffff8a55388259b8 RDI: ffff8a5538800000
Jul 10 10:59:12 pc-linux kernel: RBP: ffff8a5538800000 R08: 0000000002400020 R09: ffffffffb9e544e0
Jul 10 10:59:12 pc-linux kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8a5538800000
Jul 10 10:59:12 pc-linux kernel: R13: ffff8a55387fffe8 R14: ffff8a5591168000 R15: ffff8a5538810830
Jul 10 10:59:12 pc-linux kernel: FS:  0000000000000000(0000) GS:ffff8a6404cef000(0000) knlGS:0000000000000000
Jul 10 10:59:12 pc-linux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 10 10:59:12 pc-linux kernel: CR2: 00007f1ae993a540 CR3: 0000000c9325d002 CR4: 0000000000f72ef0
Jul 10 10:59:12 pc-linux kernel: PKRU: 55555554
Jul 10 10:59:12 pc-linux kernel: Call Trace:
Jul 10 10:59:12 pc-linux kernel:  <TASK>
Jul 10 10:59:12 pc-linux kernel:  gfx_v11_0_hw_fini+0x2b/0x100 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  amdgpu_ip_block_suspend+0x24/0x50 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  amdgpu_device_ip_suspend_phase2+0x93/0x200 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  ? amdgpu_ip_block_suspend+0x24/0x50 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  amdgpu_device_ip_suspend+0x46/0x80 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  ? amdgpu_device_ip_need_full_reset+0x16/0x80 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  amdgpu_device_pre_asic_reset+0xe9/0x2c0 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  amdgpu_device_gpu_recover.cold+0x58a/0xd1b [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  amdgpu_job_timedout.cold+0x20a/0x450 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 10:59:12 pc-linux kernel:  drm_sched_job_timedout+0x85/0x120 [gpu_sched 8bcbf91c3468fe4a97e8312e3d021d5305a517fb]
Jul 10 10:59:12 pc-linux kernel:  process_one_work+0x190/0x350
Jul 10 10:59:12 pc-linux kernel:  worker_thread+0x2d7/0x410
Jul 10 10:59:12 pc-linux kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 10 10:59:12 pc-linux kernel:  kthread+0xf9/0x240
Jul 10 10:59:12 pc-linux kernel:  ? __pfx_kthread+0x10/0x10
Jul 10 10:59:12 pc-linux kernel:  ret_from_fork+0x31/0x50
Jul 10 10:59:12 pc-linux kernel:  ? __pfx_kthread+0x10/0x10
Jul 10 10:59:12 pc-linux kernel:  ret_from_fork_asm+0x1a/0x30
Jul 10 10:59:12 pc-linux kernel:  </TASK>
Jul 10 10:59:12 pc-linux kernel: ---[ end trace 0000000000000000 ]---

Followed by this:

Jul 10 11:02:26 pc-linux kernel: INFO: task ThreadPoolSingl:46158 blocked for more than 122 seconds.
Jul 10 11:02:26 pc-linux kernel:       Tainted: G        W  OE       6.15.5-arch1-1 #1
Jul 10 11:02:26 pc-linux kernel:       Blocked by coredump.
Jul 10 11:02:26 pc-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 10 11:02:26 pc-linux kernel: task:ThreadPoolSingl state:D stack:0     pid:46158 tgid:46077 ppid:46033  task_flags:0x40044c flags:0x00004002
Jul 10 11:02:26 pc-linux kernel: Call Trace:
Jul 10 11:02:26 pc-linux kernel:  <TASK>
Jul 10 11:02:26 pc-linux kernel:  __schedule+0x409/0x1320
Jul 10 11:02:26 pc-linux kernel:  ? kfree+0x334/0x3b0
Jul 10 11:02:26 pc-linux kernel:  schedule+0x27/0xd0
Jul 10 11:02:26 pc-linux kernel:  schedule_timeout+0xbd/0x100
Jul 10 11:02:26 pc-linux kernel:  dma_fence_default_wait+0x198/0x280
Jul 10 11:02:26 pc-linux kernel:  ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Jul 10 11:02:26 pc-linux kernel:  dma_fence_wait_timeout+0x109/0x130
Jul 10 11:02:26 pc-linux kernel:  amdgpu_vm_fini+0xe9/0x5f0 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 11:02:26 pc-linux kernel:  ? idr_destroy+0x77/0xb0
Jul 10 11:02:26 pc-linux kernel:  amdgpu_driver_postclose_kms+0x199/0x270 [amdgpu 37e8e6d4e0a29d60f3fb5f370e878e15037f9482]
Jul 10 11:02:26 pc-linux kernel:  drm_file_free+0x226/0x290
Jul 10 11:02:26 pc-linux kernel:  drm_release+0xc3/0x140
Jul 10 11:02:26 pc-linux kernel:  __fput+0xe3/0x2a0
Jul 10 11:02:26 pc-linux kernel:  task_work_run+0x5a/0x90
Jul 10 11:02:26 pc-linux kernel:  do_exit+0x313/0xa80
Jul 10 11:02:26 pc-linux kernel:  do_group_exit+0x2d/0xc0
Jul 10 11:02:26 pc-linux kernel:  get_signal+0x81c/0x840
Jul 10 11:02:26 pc-linux kernel:  arch_do_signal_or_restart+0x3f/0x280
Jul 10 11:02:26 pc-linux kernel:  syscall_exit_to_user_mode+0x174/0x1c0
Jul 10 11:02:26 pc-linux kernel:  do_syscall_64+0x87/0x810
Jul 10 11:02:26 pc-linux kernel:  ? futex_wake+0x8a/0x190
Jul 10 11:02:26 pc-linux kernel:  ? audit_reset_context+0x2c8/0x330
Jul 10 11:02:26 pc-linux kernel:  ? syscall_exit_to_user_mode_prepare+0x17e/0x1f0
Jul 10 11:02:26 pc-linux kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Jul 10 11:02:26 pc-linux kernel:  ? do_syscall_64+0x87/0x810
Jul 10 11:02:26 pc-linux kernel:  ? hrtimer_cancel+0x15/0x40
Jul 10 11:02:26 pc-linux kernel:  ? futex_wait+0x88/0x120
Jul 10 11:02:26 pc-linux kernel:  ? __pfx_hrtimer_wakeup+0x10/0x10
Jul 10 11:02:26 pc-linux kernel:  ? __rseq_handle_notify_resume+0x9b/0x4d0
Jul 10 11:02:26 pc-linux kernel:  ? switch_fpu_return+0x4e/0xd0
Jul 10 11:02:26 pc-linux kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x7c/0x90
Jul 10 11:02:26 pc-linux kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Jul 10 11:02:26 pc-linux kernel:  ? do_syscall_64+0x87/0x810
Jul 10 11:02:26 pc-linux kernel:  ? irqentry_exit_to_user_mode+0x2c/0x1b0
Jul 10 11:02:26 pc-linux kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jul 10 11:02:26 pc-linux kernel: RIP: 0033:0x7fd29d2b5e22
Jul 10 11:02:26 pc-linux kernel: RSP: 002b:00007fd2748d5218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
Jul 10 11:02:26 pc-linux kernel: RAX: fffffffffffffe00 RBX: 00007fd2748d5440 RCX: 00007fd29d2b5e22
Jul 10 11:02:26 pc-linux kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 00007fd2748d5460
Jul 10 11:02:26 pc-linux kernel: RBP: 00007fd2748d5250 R08: 0000000000000000 R09: 00000000ffffffff
Jul 10 11:02:26 pc-linux kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
Jul 10 11:02:26 pc-linux kernel: R13: 00007fd2748d5418 R14: 0000000000000000 R15: 0000000000000000
Jul 10 11:02:26 pc-linux kernel:  </TASK>
Jul 10 11:02:26 pc-linux kernel: INFO: task kworker/u129:0:89047 blocked for more than 122 seconds.
Jul 10 11:02:26 pc-linux kernel:       Tainted: G        W  OE       6.15.5-arch1-1 #1
Jul 10 11:02:26 pc-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 10 11:02:26 pc-linux kernel: task:kworker/u129:0  state:D stack:0     pid:89047 tgid:89047 ppid:2      task_flags:0x4208060 flags:0x00004000
Jul 10 11:02:26 pc-linux kernel: Workqueue: ttm ttm_bo_delayed_delete [ttm]
Jul 10 11:02:26 pc-linux kernel: Call Trace:
Jul 10 11:02:26 pc-linux kernel:  <TASK>
Jul 10 11:02:26 pc-linux kernel:  __schedule+0x409/0x1320
Jul 10 11:02:26 pc-linux kernel:  ? get_nohz_timer_target+0x2f/0x150
Jul 10 11:02:26 pc-linux kernel:  schedule+0x27/0xd0
Jul 10 11:02:26 pc-linux kernel:  schedule_timeout+0xbd/0x100
Jul 10 11:02:26 pc-linux kernel:  dma_fence_default_wait+0x198/0x280
Jul 10 11:02:26 pc-linux kernel:  ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Jul 10 11:02:26 pc-linux kernel:  dma_fence_wait_timeout+0x109/0x130
Jul 10 11:02:26 pc-linux kernel:  dma_resv_wait_timeout+0xc7/0x1c0
Jul 10 11:02:26 pc-linux kernel:  ttm_bo_delayed_delete+0x2a/0x80 [ttm 98a4cee4dbe026bdded718b343675bbd2ffa4d40]
Jul 10 11:02:26 pc-linux kernel:  process_one_work+0x190/0x350
Jul 10 11:02:26 pc-linux kernel:  worker_thread+0x2d7/0x410
Jul 10 11:02:26 pc-linux kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 10 11:02:26 pc-linux kernel:  kthread+0xf9/0x240
Jul 10 11:02:26 pc-linux kernel:  ? __pfx_kthread+0x10/0x10
Jul 10 11:02:26 pc-linux kernel:  ret_from_fork+0x31/0x50
Jul 10 11:02:26 pc-linux kernel:  ? __pfx_kthread+0x10/0x10
Jul 10 11:02:26 pc-linux kernel:  ret_from_fork_asm+0x1a/0x30
Jul 10 11:02:26 pc-linux kernel:  </TASK>

Last edited by Wereii (2025-07-10 12:28:12)

Offline

#3 2025-07-12 14:36:20

anthqiu
Member
Registered: 2025-07-07
Posts: 2

Re: [amdgpu] failed to resume from S3 suspend (smu failed -62)

Wereii wrote:

I believe we are getting the same problem, the closest issue I could find on the freedesktop GL is this, https://gitlab.freedesktop.org/drm/amd/ … te_3000497 , already reported my kernel log there.
There already are some comments about what to try (I haven't had time to try them yet).

In my case I'm also having sleep/suspend issue under Windows, so I feel mine's more of a hardware issue. I'm switching to NVIDIA sad

Last edited by anthqiu (2025-07-12 14:38:58)

Offline

#4 2025-07-12 15:14:50

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,217

Re: [amdgpu] failed to resume from S3 suspend (smu failed -62)

You might want to search the forum on that subject first…
Also 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2025-07-15 09:42:34

Wereii
Member
Registered: 2024-06-25
Posts: 8

Re: [amdgpu] failed to resume from S3 suspend (smu failed -62)

I've switched to linux-lts and it's been working alright since then.

Offline

Pages: 1

Board footer

Powered by FluxBB