View previous topic :: View next topic |
Author |
Message |
quirkyaurora64 n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 20 Jul 2024 Posts: 2
|
Posted: Sat Jul 20, 2024 9:28 am Post subject: Suspend fails on ASUS TUF A16 |
|
|
Hello,
I recently bought an AMD TUF A16 Advantage Edition laptop with an AMD Ryzen 7 7735HS CPU, Radeon 680M integrated GPU, and Radeon RX 7700S GPU.
I installed Gentoo with a custom kernel (6.10.0) and have tried to suspend the system with both loginctl suspend and s2ram. Doing so causes the screen to go black momentarily, followed by the fans spinning up to full speed and the screen waking up.
I tried downgrading the kernel to 6.6.38, which did not fix the problem.
Following suspending, dmesg returns the following:
Code: |
[ 25.960160] amdgpu 0000:78:00.0: amdgpu: SMU is resuming...
[ 25.960176] [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000).
[ 25.960210] amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
[ 25.961872] amdgpu 0000:78:00.0: amdgpu: SMU is resumed successfully!
[ 25.969576] nvme nvme1: 16/0/0 default/read/poll queues
[ 25.970157] nvme nvme0: 16/0/0 default/read/poll queues
[ 25.997020] amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x81fc000000 for PSP TMR
[ 26.087680] [drm] JPEG decode initialized successfully.
[ 26.087684] amdgpu 0000:78:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 26.087686] amdgpu 0000:78:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
[ 26.087687] amdgpu 0000:78:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
[ 26.087688] amdgpu 0000:78:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
[ 26.087689] amdgpu 0000:78:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 26.087691] amdgpu 0000:78:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 26.087692] amdgpu 0000:78:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 26.087693] amdgpu 0000:78:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 26.087694] amdgpu 0000:78:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 26.087695] amdgpu 0000:78:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 26.087696] amdgpu 0000:78:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
[ 26.087697] amdgpu 0000:78:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
[ 26.087698] amdgpu 0000:78:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[ 26.087699] amdgpu 0000:78:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[ 26.087700] amdgpu 0000:78:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[ 26.087701] amdgpu 0000:78:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[ 26.142561] usb 5-1: reset full-speed USB device number 2 using xhci_hcd
[ 26.197541] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 26.213581] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 26.213583] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[ 26.213586] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[ 26.213590] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000035, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00525b00 (82.91.0)
[ 26.213594] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[ 30.906689] amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000006 SMN_C2PMSG_82:0x00000000
[ 30.906691] amdgpu 0000:03:00.0: amdgpu: Failed to enable requested dpm features!
[ 30.906693] amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
[ 30.906694] [drm:amdgpu_device_ip_resume_phase2] *ERROR* resume of IP block <smu> failed -62
[ 30.906699] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).
[ 30.906701] amdgpu 0000:03:00.0: PM: dpm_run_callback(): pci_pm_resume returns -62
[ 30.906705] amdgpu 0000:03:00.0: PM: failed to resume async: error -62
[ 30.910825] OOM killer enabled.
[ 30.910826] Restarting tasks ... done.
[ 30.911093] random: crng reseeded on system resumption
[ 30.913793] PM: suspend exit
|
I have tried suspending the system in Ubuntu with kernel version 6.9.3, which seems to have worked perfectly, so I suspect I have an issue in my Gentoo kernel configuration.
Any help or advice would be greatly appreciated.
Thank you! |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
jpsollie Apprentice
![Apprentice Apprentice](/images/ranks/rank_rect_2.gif)
Joined: 17 Aug 2013 Posts: 299
|
Posted: Sat Jul 20, 2024 12:49 pm Post subject: |
|
|
if you want to check whether it really is your kernel or some unknown userspace wakeup event, try this in console mode:
Code: |
echo mem > /sys/power/state
|
and then check if your laptop sleeps,
and whether you can wake it up again.
It's not much, but actually bypasses all wakeup event handlers some userspace stuff installs.
if it doesn't work, then there's probably some hardware not listening properly, or your kernel isn't configured properly, we'll see.... _________________ The power of Gentoo optimization (not overclocked): [img]https://www.passmark.com/baselines/V10/images/503714802842.png[/img] |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
quirkyaurora64 n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 20 Jul 2024 Posts: 2
|
Posted: Sun Jul 21, 2024 3:29 pm Post subject: |
|
|
Using that command causes my screen to go black for 3 seconds, followed by the computer immediately waking up. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
sublogic Apprentice
![Apprentice Apprentice](/images/ranks/rank_rect_2.gif)
![](images/avatars/92700334162390783722aa.png)
Joined: 21 Mar 2022 Posts: 264 Location: Pennsylvania, USA
|
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
Goverp Advocate
![Advocate Advocate](/images/ranks/rank-G-1-advocate.gif)
![](images/avatars/152613747847c6fd276c31a.jpg)
Joined: 07 Mar 2007 Posts: 2106
|
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
Hu Administrator
![Administrator Administrator](/images/ranks/rank-admin.gif)
Joined: 06 Mar 2007 Posts: 22364
|
Posted: Mon Jul 22, 2024 12:05 pm Post subject: |
|
|
I agree with the reporter of https://github.com/elogind/elogind/issues/285 that using s2idle is not a good default choice, but s2idle is a kernel feature that ought to either work fully or abort with a clear error saying "You cannot do that." In the reported Github issue, the kernel attempted the s2idle and did not abort, but did experience those odd errors. s2idle can be triggered without using elogind, so while elogind might have caused people to hit it who otherwise would not, elogind is not at fault for the underlying problem that s2idle is not playing well with amdgpu. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|