** Description changed:

  [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.
  
  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).
+     amdgpu 0000:05:00.0: amdgpu: initializing kernel modesetting (YELLOW_CARP 
0x1002:0x1681 0x103C:0x8F3E 0x0B).
  
  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.
  
  [Fix]
  Update DMCUB firmware for yellow_carp and other AMD display ASICs to match
  upstream linux-firmware.
  
- Cherry-picked 65 DMCUB firmware update commits from the upstream 
linux-firmware
+ 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).
  
- 1e2c15348 amdgpu: DMCUB updates for various ASICs
+ The latest two commits are:
+ 
+ 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
+ 
+ 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
  
- Firmware version range: 0.0.202.0 (current noble) → 0.1.43.0 (latest
- upstream).
+ 17 firmware binary files changed in total.
  
  [Test Plan]
  1. Install the updated linux-firmware package
  2. Run update-initramfs:
-    $ sudo update-initramfs -u
+    $ sudo update-initramfs -u
  3. Reboot:
-    $ sudo reboot
+    $ sudo reboot
  4. Run suspend test:
-    $ sudo rtcwake -m mem -s 30
+    $ sudo rtcwake -m mem -s 30
  5. Repeat 5 times
  
  Without patch: system hangs on resume, requires power cable unplug
  With patch: system resumes normally, no hang
  
  [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.
  
  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 risk is higher than a single-ASIC update because 16 firmware files are
+ 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).
+ 
+ [Other Info]
+ All 67 commits are cherry-picked from the upstream linux-firmware repository.
+ The two newest upstream commits are tagged 20260410 and 20260519 respectively.
+ SRU for noble linux-firmware.

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

Reply via email to