** Description changed: =================== SRU for Questing/Resolute ================= [Impact] System hangs after suspend on HP systems (CID: 202603-38534) with AMD Ryzen (Rembrandt Refresh / Yellow Carp APU). The hang is hard — power button does not respond, requires unplugging the power cable. LP#2144530 reverted the Yellow Carp DMCUB firmware to a known good version (0x4000045) in resolute to fix a display regression on Acer systems. That revert fixed the display issue but left the suspend hang unresolved because the older firmware cannot handle suspend/resume on Rembrandt Refresh hardware. This is a follow-up: update yellow_carp_dmcub.bin to v4.0.74.0, which includes both the fix for the display regression (LP#2144530) and a workaround to disable unused PHY on certain laptops that fixes the suspend hang. [Fix] Update rembrandt DMCUB firmware to v4.0.74.0 for yellow_carp. This firmware adds a workaround to disable unused PHY on certain laptops, fixing the suspend hang while keeping the display regression fix from the earlier revert. Cherry-picked from upstream linux-firmware: 7a8ddf10f67d amdgpu: rembrandt DMCUB v4.0.74.0 (upstream tag 20260519) Only yellow_carp_dmcub.bin is changed. [Test Plan] 1. Install the updated linux-firmware package 2. Rebuild initramfs: - $ sudo update-initramfs -u + $ sudo update-initramfs -u 3. Reboot: - $ sudo reboot + $ sudo reboot 4. Verify display works (regression from LP#2144530 must not return): - $ xrandr --listmonitors + $ xrandr --listmonitors 5. Run suspend test: - $ sudo rtcwake -m mem -s 30 + $ sudo rtcwake -m mem -s 30 6. Repeat 5 times Without patch: system hangs on resume, requires power cable unplug With patch: system resumes normally, display works, no hang [Where problems could occur] This replaces the reverted-to-safe firmware (0x4000045) with a newer version (v4.0.74.0). If the new firmware reintroduces the display regression fixed by LP#2144530, Acer and other Yellow Carp systems could lose internal eDP or USB-C/DP output again — black screen on boot. The PHY disable workaround could also be too aggressive. If it disables a PHY that is actually in use, display output on a secondary port would stop working. Only yellow_carp_dmcub.bin is changed, so other AMD ASICs are not affected. =================== SRU for Noble ================= + [Impact] - System hangs after suspend on HP systems (CID: 202603-38534) with AMD Ryzen 5 150 - (Rembrandt Refresh / Yellow Carp APU). The hang is hard — power button does not - respond, requires unplugging the power cable. + System hangs after suspend/resume on HP systems with AMD Ryzen 5 150 (Rembrandt/Yellow Carp) GPU (CID: 202603-38534). After resume, the system is completely unresponsive — power button does not work, requires power cable unplug to recover. - dmesg shows the GPU is YELLOW_CARP with DMCUB (Display MicroController Unit B) - firmware loaded: - amdgpu 0000:05:00.0: amdgpu: initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681 0x103C:0x8F3E 0x0B). + Failure rate: 1/1 on affected hardware. - The noble linux-firmware package ships DMCUB version 4.0.68.0 (package 0.0.202.0) - for yellow_carp. This firmware is too old to handle suspend/resume on Rembrandt - Refresh hardware. The hang occurs during the resume path when DMCUB fails to - reinitialize display properly. - - Suspend debug test (pm_test) shows devices and platform levels resume fine, but - the full suspend path hangs. + The root cause is outdated DMCUB (Display MicroController Unit B) + firmware that does not handle power state transitions correctly during + suspend/resume. [Fix] - Update DMCUB firmware for yellow_carp and other AMD display ASICs to match - upstream linux-firmware. + Update AMDGPU DMCUB firmware binaries for multiple DCN generations (DCN314, DCN315, DCN316, DCN35, DCN351, DCN32, DCN321, Yellow Carp, Rembrandt, Green Sardine, Renoir, Sienna Cichlid). - Cherry-picked 67 DMCUB firmware update commits from the upstream linux-firmware - repository (git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git). + Key fixes across the firmware updates: + - Panel flickering during resume from S0i3 + - IPS (Idle Power State) fixes + - PSR entry fix during DPMS resume + - Power state update handling + - USB4 related fixes + - Cursor disappears after suspend fix + - Workaround to disable unused PHY on certain laptops (Rembrandt v4.0.74.0) - The latest two commits are: + Firmware versions progress from v0.0.215.0 through v0.0.246.0, plus + DCN351 v9.0.10.0 and Rembrandt v4.0.74.0. - d3a8c256bf3b amdgpu: Revert Yellow Carp DMUB fw to 0x4000045 (upstream tag 20260410) - Reverts to a known good DMUB firmware version for Yellow Carp. - Fixes: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143 + All patches cherry-picked from the upstream linux-firmware repository: - 7a8ddf10f67d amdgpu: rembrandt DMCUB v4.0.74.0 (upstream tag 20260519) - Adds a workaround to disable unused PHY on certain laptops. - - The updates cover DMCUB firmware for the following ASICs: - - Yellow Carp (Rembrandt / Rembrandt Refresh) - - DCN 3.1.4, DCN 3.1.5, DCN 3.1.6 - - DCN 3.2, DCN 3.2.1 - - DCN 3.5, DCN 3.5.1, DCN 3.6 - - DCN 4.0.1 - - Renoir, Green Sardine, Van Gogh - - Beige Goby, Navy Flounder, Dimgrey Cavefish, Sienna Cichlid - - 17 firmware binary files changed in total. + 0500ef179 amdgpu: DMCUB updates for various AMDGPU ASICs + (from upstream 2398d264f953, tag 20240513) + 4a2a44dc7 amdgpu: update DMCUB to v0.0.224.0 for Various AMDGPU Asics + (from upstream e8b09280fa5f) + 7fd83c711 amdgpu: update DMCUB to v0.0.225.0 for Various AMDGPU Asics + (from upstream ed874ed83cac) + a164c186c amdgpu: update DMCUB to v0.0.227.0 for DCN35 and DCN351 + (from upstream bcd040c21dc9) + 9fca0c375 amdgpu: DMCUB updates for various AMDGPU ASICs + (from upstream 0600ef249c32) + dcf53caba amdgpu: DMCUB updates for various AMDGPU ASICs + (from upstream bec4fd18cc57) + a6ab80429 amdgpu: update DMCUB to v0.0.232.0 for DCN314 and DCN351 + (from upstream d6c600d46981) + f3b7ad11a amdgpu: DMCUB updates for various AMDGPU ASICs + (from upstream 3d45353e1221) + 9d1656f99 amdgpu: DMCUB updates for various AMDGPU ASICs + (from upstream 987607d681cb) + 820deff63 amdgpu: update DMCUB to v9.0.10.0 for DCN351 + (from upstream c99eeb4d0e13) + 6fe7cabeb amdgpu: update dmcub 0.0.246.0 firmware + (from upstream 209c18b0e7cd) + f2a4839c1 amdgpu: rembrandt DMCUB v4.0.74.0 + (from upstream 7a8ddf10f67d, tag 20260519) [Test Plan] - 1. Install the updated linux-firmware package - 2. Run update-initramfs: - $ sudo update-initramfs -u - 3. Reboot: - $ sudo reboot - 4. Run suspend test: - $ sudo rtcwake -m mem -s 30 - 5. Repeat 5 times + Suspend and resume the system 30 times: + $ sudo rtcwake -m mem -s 20 - Without patch: system hangs on resume, requires power cable unplug - With patch: system resumes normally, no hang + Without updated firmware: system hangs on resume, requires power cable unplug. + With updated firmware: system resumes normally, no hang, no errors in dmesg. [Where problems could occur] - DMCUB firmware is loaded by the amdgpu kernel driver for all AMD display - controllers. Updating the firmware for all these ASICs at once affects a wide - range of AMD GPUs and APUs. + DMCUB firmware is shared across many AMD GPU generations. A regression in the firmware could cause display issues on any AMD system using DCN314, DCN315, DCN35, DCN351, or Yellow Carp/Rembrandt display controllers. - If the new DMCUB firmware has a bug: - - Display could fail to initialize after boot or resume. Screen stays black. - - Display flickering or corruption during mode changes. - - Suspend/resume could break on other AMD hardware that was working before. - - The Yellow Carp revert (d3a8c256bf3b) followed by a new v4.0.74.0 update - (7a8ddf10f67d) means Yellow Carp went through three firmware versions in this - series. If the PHY disable workaround in v4.0.74.0 is too aggressive, Yellow - Carp systems could lose display output on a secondary or unused port. - - The risk is higher than a single-ASIC update because 17 firmware files are - changed across many GPU generations (Renoir through DCN 4.0.1). + Possible symptoms of a firmware regression: + - Display not coming back after suspend/resume + - Panel flickering or black screen on resume + - HDMI/DP output failing to light up + - PSR (Panel Self Refresh) not working, causing higher power draw
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2147396 Title: AMD Ryzen did not response after system enter suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2147396/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
