AMD Cezanne takes 5 minutes to wake up from suspend

Bug #1993715 reported by You-Sheng Yang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
New
Undecided
Unassigned
linux (Ubuntu)
In Progress
High
You-Sheng Yang
Jammy
Invalid
Undecided
Unassigned
Kinetic
Fix Released
Medium
You-Sheng Yang
linux-oem-6.0 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
High
You-Sheng Yang
Kinetic
Invalid
Undecided
Unassigned

Bug Description

[SRU Justification]

[Impact]

AMD Cezanne takes 5 minutes to wake up from suspend.

[Fix]

A fix originated from AMD is being proposed to upstream mailing list.

[Test Case]

$ rtcwake -m mem -s 10

[Where problems could occur]

This patch fixes the issue we had, but maybe there are still some other corner cases that can cause similar problems.

[Other Info]

The problematic commit landed in v5.19-rc1, so kernels >= v5.19 are
nominated for fix.

========== original bug description ==========

[Summary]
rtcwake may be blocked for 5 minutes.

Model name: AMD Ryzen 5 7530U with Radeon Graphics
CPU family: 25
Model: 80
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 1
Stepping: 0

[Reproduce Steps]
1. $ rtcwake -m mem -s 10
2. The device takes 5 minutes to resume

[Results]
Expected: Should resume after 10 seconds
Actual: System stays asleep for 5 minutes

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Proposed fix in https://<email address hidden>/

tags: added: oem-priority originate-from-1991500 somerville
Changed in linux (Ubuntu Jammy):
status: New → Confirmed
status: Confirmed → Invalid
Changed in linux (Ubuntu Kinetic):
status: New → Confirmed
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: New → Triaged
Changed in linux-oem-6.0 (Ubuntu Kinetic):
status: New → Invalid
Revision history for this message
You-Sheng Yang (vicamo) wrote :
description: updated
Changed in linux (Ubuntu Kinetic):
status: Confirmed → In Progress
importance: Undecided → High
assignee: nobody → You-Sheng Yang (vicamo)
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: Triaged → In Progress
importance: Undecided → High
assignee: nobody → You-Sheng Yang (vicamo)
Timo Aaltonen (tjaalton)
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-6.0/6.0.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Tested on WM2N5B-DVT1-A3_202210-30676 with 6.0.0-1007-oem in proposed.

Run

$ sudo rtcwake -m freeze -s 15

The device can resume after 15 seconds. Here is the kernel log for reference.

tags: added: verification-done-jammy
Stefan Bader (smb)
Changed in linux (Ubuntu Kinetic):
importance: High → Medium
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (58.3 KiB)

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1007.7

---------------
linux-oem-6.0 (6.0.0-1007.7) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1007.7 -proposed tracker (LP: #1992023)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.10.10)

  * AMD Cezanne takes 5 minutes to wake up from suspend (LP: #1993715)
    - SAUCE: platform/x86/amd: pmc: Read SMU version during suspend on Cezanne
      systems

  * Add iommu passthrough quirk for Intel IPU6 on RaptorLake (LP: #1989041)
    - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Raptor
      Lake

  * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
    (LP: #1993561)
    - SAUCE: drm/i915/display: Drop check for doublescan mode in modevalid
    - SAUCE: drm/i915/display: Prune Interlace modes for Display >=12

  * [SRU] SoF for RPL platform support (LP: #1992714)
    - ASoC: Intel: common: add ACPI matching tables for Raptor Lake
    - ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions

  * Can only reach PC3 when ethernet is plugged r8169 (LP: #1946433)
    - SAUCE: r8169: Enable chip-specific ASPM regardless of PCIe ASPM status
    - SAUCE: r8169: Use mutex to guard config register locking
    - SAUCE: r8169: Implement dynamic ASPM mechanism

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
    luminance (LP: #1978986)
    - drm: New function to get luminance range based on static hdr metadata
    - drm/amdgpu_dm: Rely on split out luminance calculation function
    - drm/i915: Use luminance range calculated during edid parsing

  * Add support for AMD PMF Cool and Quiet Framework (CnQF) (LP: #1991609)
    - platform/x86/amd/pmf: Add support for CnQF
    - platform/x86/amd/pmf: Add sysfs to toggle CnQF
    - Documentation/ABI/testing/sysfs-amd-pmf: Add ABI doc for AMD PMF

  * TEE Support for CCP driver (LP: #1991608)
    - SAUCE: crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * Jammy update: v6.0.3 upstream stable release (LP: #1994038)
    - ALSA: oss: Fix potential deadlock at unregistration
    - ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free()
    - ALSA: usb-audio: Fix potential memory leaks
    - ALSA: usb-audio: Fix NULL dererence at error path
    - ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530
    - ALSA: hda/realtek: Correct pin configs for ASUS G533Z
    - ALSA: hda/realtek: Add quirk for ASUS GV601R laptop
    - ALSA: hda/realtek: Add Intel Reference SSID to support headset keys
    - mtd: rawnand: atmel: Unmap streaming DMA mappings
    - io_uring: add custom opcode hooks on fail
    - io_uring/rw: don't lose partial IO result on fail
    - io_uring/net: don't lose partial send/recv on fail
    - io_uring/rw: fix unexpected link breakage
    - io_uring/rw: don't lose short results on io_setup_async_rw()
    - io_uring/net: fix fast_iov assignment in io_setup_async_msg()
    - io_uring/net: don't update msg_name if not provided
    - io_uring: limit registration w/ SINGLE_ISSUER
    - io_uring/net: handle -EINPROGRESS correct for IORING_OP_CONNECT
    - io_uring: correct pinned_vm ac...

Changed in linux-oem-6.0 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.19.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux verification-needed-kinetic
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (100.4 KiB)

This bug was fixed in the package linux - 5.19.0-28.29

---------------
linux (5.19.0-28.29) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-28.29 -proposed tracker (LP: #1999746)

  * mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux
    5.19.0-27.28 (LP: #1999094)
    - fix coredump breakage

linux (5.19.0-27.28) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-27.28 -proposed tracker (LP: #1997794)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * selftests/.../nat6to4 breaks the selftests build (LP: #1996536)
    - [Config] Disable selftests/net/bpf/nat6to4

  * Expose built-in trusted and revoked certificates (LP: #1996892)
    - [Packaging] Expose built-in trusted and revoked certificates

  * support for same series backports versioning numbers (LP: #1993563)
    - [Packaging] sameport -- add support for sameport versioning

  * Add cs35l41 firmware loading support (LP: #1995957)
    - ASoC: cs35l41: Move cs35l41 exit hibernate function into shared code
    - ASoC: cs35l41: Add common cs35l41 enter hibernate function
    - ASoC: cs35l41: Do not print error when waking from hibernation
    - ALSA: hda: cs35l41: Don't dereference fwnode handle
    - ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations
    - ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR()
    - ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41
    - ALSA: hda: hda_cs_dsp_ctl: Add Library to support CS_DSP ALSA controls
    - ALSA: hda: hda_cs_dsp_ctl: Add apis to write the controls directly
    - ALSA: hda: cs35l41: Save codec object inside component struct
    - ALSA: hda: cs35l41: Add initial DSP support and firmware loading
    - ALSA: hda: cs35l41: Save Subsystem ID inside CS35L41 Driver
    - ALSA: hda: cs35l41: Support reading subsystem id from ACPI
    - ALSA: hda: cs35l41: Support multiple load paths for firmware
    - ALSA: hda: cs35l41: Support Speaker ID for laptops
    - ALSA: hda: cs35l41: Support Hibernation during Suspend
    - ALSA: hda: cs35l41: Read Speaker Calibration data from UEFI variables
    - ALSA: hda: hda_cs_dsp_ctl: Add fw id strings
    - ALSA: hda: cs35l41: Add defaulted values into dsp bypass config sequence
    - ALSA: hda: cs35l41: Support Firmware switching and reloading
    - ALSA: hda: cs35l41: Add module parameter to control firmware load
    - Revert "ALSA: hda: cs35l41: Allow compilation test on non-ACPI
      configurations"
    - ALSA: hda/realtek: More robust component matching for CS35L41
    - [Config] updateconfigs for SND_HDA_CS_DSP_CONTROLS

  * Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
    - net: wwan: t7xx: Add AP CLDMA

  * Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
    (LP: #1995573)
    - drm/mgag200: Optimize damage clips
    - drm/mgag200: Add FB_DAMAGE_CLIPS support
    - drm/mgag200: Enable atomic gamma lut update

  * TEE Support for CCP driver (LP: #1991608)
    - crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * AMD Cezanne takes 5 minutes to wake up from suspend (LP: #1993715)
    - platform/x86/amd: pmc: Read...

Changed in linux (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-ibm
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.19.0-1018.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.19.0-1017.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-lowlatency-hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.