Bug 2148809 - AMD Ryzen 3 5300U fails to resume from suspend (non-boot CPUs)
Summary: AMD Ryzen 3 5300U fails to resume from suspend (non-boot CPUs)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-28 03:32 UTC by Glenn Morris
Modified: 2023-12-06 11:33 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-06 11:33:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output from just before a failed "processors" pm_test. (107.54 KB, text/plain)
2022-11-28 03:32 UTC, Glenn Morris
no flags Details

Description Glenn Morris 2022-11-28 03:32:41 UTC
Created attachment 1927913 [details]
dmesg output from just before a failed "processors" pm_test.

Hi,

1. Please describe the problem:

I have an ASUS PN51 mini-pc with an AMD Ryzen 3 5300U CPU.
The system fails to resume from suspend.
It appears to suspend correctly (display goes off, fan stops, power light blinks), but does not resume (power light becomes solid, fan starts, but no display or keyboard capslock, system is non-responsive and needs a hard boot).

Experimenting with /sys/power/pm_test, I find that "freezer", "devices", and "platform" work ok, but "processors" and "core" fail as above.

Motivated by this, I find that the system will correctly suspend and resume if I disable non-boot CPUs before suspend, with "chcpu -d 1-7",
and then enable them again post-resume.

BIOS has been updated to the latest manufacturer version. There don't appear to be any BIOS options related to suspend.


2. What is the Version-Release number of the kernel:

6.0.9-300.fc37.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 :

I think it used to work several months ago, but it stopped working partway through Fedora 36. I'm afraid I can't be more precise.


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

Reproduces every time, with
echo mem >| /sys/power/state


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``:

Fails in the same way with rawhide kernel 6.1.0-0.rc6.46.fc38.


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.

Attached is dmesg from just before a "processors" pm_test suspend.


Thanks!

Comment 1 Glenn Morris 2023-04-30 00:56:51 UTC
Still failing in Fedora 38 with kernel 6.2.13-300.fc38.x86_64.

Comment 2 Aoife Moloney 2023-11-23 00:37:50 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2023-12-06 11:33:24 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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


Note You need to log in before you can comment on or make changes to this bug.