Bug 217497 - Asus TUF617XS / FA617XS not entering suspend mode
Summary: Asus TUF617XS / FA617XS not entering suspend mode
Status: RESOLVED ANSWERED
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: Rafael J. Wysocki
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-28 10:50 UTC by drich
Modified: 2023-05-28 15:51 UTC (History)
0 users

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg.txt (129.50 KB, text/plain)
2023-05-28 10:50 UTC, drich
Details

Description drich 2023-05-28 10:50:47 UTC
Created attachment 304340 [details]
dmesg.txt

Hello,

This laptop does not seem to be able to enter suspend mode : screen goes off, ping stops responding, but fans and power led are still on.

For a keyboard issue, I had to apply the patch linked here https://bugzilla.kernel.org/show_bug.cgi?id=217336#c90 . Before applying, the laptop was resuming a few seconds after suspend, it now stays in the state described above.

Hibernate seems to work well.

Tested with 6.4.y, 6.3.4 and 6.1.30, always the same behavior.

Could this be an ACPI problem ? Should I attach an acpidump ?


System:
  Host: laptop Kernel: 6.4.0-rc3-amd64+ arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4.0-rc3-amd64+
    root=UUID=9012f2a0-b3f6-49eb-ae42-a08feded24dc ro
  Console: pty pts/0 DM: SDDM Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A16 FA617XS_TUF617XS v: 1.0
    serial: R3NRKD04193512F
  Mobo: ASUSTeK model: FA617XS v: 1.0 serial: C5W33M100AY UEFI: American Megatrends LLC.
    v: FA617XS.303 date: 03/23/2023
Comment 1 Artem S. Tashkinov 2023-05-28 12:12:51 UTC
Please repost this issue here as well:

https://gitlab.freedesktop.org/drm/amd/-/issues

From your logs it looks like the amdgpu driver is misbehaving.
Comment 2 drich 2023-05-28 15:51:23 UTC
Didn't pay enough attention while reading the dmesg, it complains about CONFIG_AMD_PMC not bundled into the kernel. Activating it solves the issue.

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