FS#74685 - [linux] suspend broken sporadically on AMD APUs

Attached to Project: Arch Linux
Opened by Bjoern Franke (bjo) - Monday, 09 May 2022, 08:54 GMT
Last edited by Toolybird (Toolybird) - Saturday, 10 June 2023, 23:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Somehow the same issue as in #73425, but it's a new one.

Additional info:
I'm trying to bisect the isssue on drm-next. I would be glad if some other affected users could help.
Upstream Issue:
https://gitlab.freedesktop.org/drm/amd/-/issues/1891

Steps to reproduce:
Suspend e.g. a Thinkpad A275, sometimes a suspend works fine, sometimes it freezes.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 10 June 2023, 23:06 GMT
Reason for closing:  Upstream
Additional comments about closing:  Arch cannot fix this kind of problem as it's not a packaging problem. If still happening, it *must* be reported upstream to the kernel folks.
Comment by Bjoern Franke (bjo) - Monday, 09 May 2022, 10:24 GMT
Affected versions: 5.16.x, 5.17.x. Unaffected: >5.15.14

Comment by Jelena (kasper) - Wednesday, 18 May 2022, 22:01 GMT
I have the same issue on my Lenovo IdeaPad 5 pro AMD Renoir Ryzen 5. I noticed this problem ~2 days ago. I keep system up to date (current kernel linux-5.17.8.arch1-1). Output from journal looks like this when the problem occurs:
...
May 18 23:03:32 myarch systemd[1]: Reached target Sleep.
May 18 23:03:32 myarch systemd[1]: Starting System Suspend...
May 18 23:03:32 myarch systemd-sleep[110683]: Entering sleep state 'suspend'...
--------------------------------------------------------------------------------
It seems like it doesn't enter the suspend mode correctly, there are no logs after "Entering sleep state" message when it happens (~ one or two times a day). Power LED is solid when it happens and I cannot wake it up (need to shut it down by pressing power off). I am currently testing it on 5.15.40-1-lts.

I detected the problem happened on linux-5.17.7.arch1-2 and linux-5.17.8.arch1-1. I am not sure about the linux-5.17.7.arch1-1, but I didn't have that problem before.
Comment by Toolybird (Toolybird) - Tuesday, 26 July 2022, 04:39 GMT
I don't see a resolution in the linked upstream issue. These hardware specific bugs are hard for Arch (or any distro) to deal with, as there is not much we can do, apart from encourage you to keep on debugging/bisecting/trying latest kernels and liaising with upstream to try and resolve it. Is the problem still occurring? Please let us know.
Comment by Bjoern Franke (bjo) - Tuesday, 26 July 2022, 09:55 GMT
I've sold my A275 now because of the reoccuring issues with it's APU.
Comment by Jelena (kasper) - Monday, 01 August 2022, 07:12 GMT
I updated my system and the problem is still active on linux-5.18.arch1-1. I didn't notice that problem on 5.15.55-2-lts. Suspend worked fine on non lts kernel before some version (around linux-5.17.7.arch1 or before). I didn't find anything in journal logs that would help me to understand what was happening. It just says entering sleep state 'suspend' and there is noting after it. I need to forcefully shutdown a computer by holding power off button for couple of seconds. I am using lts kernel where I can wake computer up from suspend, but I am not sure if the problem will appear in some next lts version.

Loading...