[SRU] Graphics issues at 4K video playback on AMD Krackan Point 2

Bug #2123814 reported by You-Sheng Yang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Fix Released
High
You-Sheng Yang
Noble
Fix Released
High
You-Sheng Yang
Plucky
Fix Released
High
You-Sheng Yang
Questing
Fix Committed
High
You-Sheng Yang

Bug Description

[ SRU Template ]

[ Impact ]

Abnormal GUI behaviours like window freeze at 4K video playback on AMD Krackan Point 2 machines.

[ Fix ]
Proposed fix is commit ba7d706f9cf6 ("amdgpu: DMCUB updates for various ASICs"), which is only in upstream main branch, no any date based tag.

[ Test Plan ]

1. Install proposed linux-firmware package from -proposed pocket,

2. Verification done by manual exam through reported symptoms.

   Test on: Sentry MLK 14 AMD and Sentry MLK 16 AMD KRK platforms with QHD panel
   Package version: linux-firmware 20240318.git3b128b60-0ubuntu2.19

   Steps:
   1. Launch Firefox browser from the desktop or taskbar.
   2. In the Firefox address bar, type www.youtube.com and press Enter.
   3. Wait for the YouTube homepage to load completely.
   4. Click on the YouTube search bar and type 4K video, then press Enter.
   5. Browse the search results and select a video labeled as 4K.
   6. Click the video thumbnail to start playback.
   7. Click the gear icon on the video player to open quality settings.
   8. Select 2160p (4K) resolution from the available options.
   9. Observe the video playback for at least 30 seconds to verify smooth performance and accurate display.
   10. Open the Snapshot camera application from the Start menu or search bar.
   22. Confirm the camera preview is displayed correctly on the QHD panel.
   12. Check for proper brightness, contrast, and responsiveness in the camera preview.
   13. Record the result as PASS if both video playback and camera preview are successful.

   Expected results: All tests passed. video playback normally. Camera function normally.

[ Where problems could occur ]

Opaque binary firmware. Per discussion internally, the original convention to SRU only minimum set of blobs have caused maintenance efforts every time we need to update AMD GPU fw blobs. This time, we pull the commits, along with their history, as well as the histories of the blobs ever involved. This adds many more commits, which either have been partially backported following the SRU convention, or the prerequisites of them. This mean many updates to existing fw have not received further verification.

[ Other Info ]

Nominate for Questing, Plucky and Noble. For Questing, full commit is cherry picked.

========== original bug report ==========

Known symptoms include:
1. VP on F6/F7 Key no function
2. VP on HDMI/Type-c Monitor connected can't recognized
3. VP on Caps' LED can't turn on when enter into Suspend
4. VP on video can't play normally
5. VP on display Resolution/Refresh Rate can't change
6. VP on taskbar UI lacks Night light icon
7. VP on pointer will delay when move pointer
8. VP on Camera will show garbage with lid closed/opened

Proposed fix: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/ba7d706f9cf6e65e9956e65ac44906a78a790a02 ("amdgpu: DMCUB updates for various ASICs")
- Firmware release 0.1.27.0
- Tested with DC 3.2.350

You-Sheng Yang (vicamo)
tags: added: jira-wtn-281
Changed in linux-firmware (Ubuntu Noble):
status: New → In Progress
Changed in linux-firmware (Ubuntu Plucky):
status: New → In Progress
Changed in linux-firmware (Ubuntu Questing):
status: New → In Progress
Changed in linux-firmware (Ubuntu Noble):
importance: Undecided → High
Changed in linux-firmware (Ubuntu Plucky):
importance: Undecided → High
Changed in linux-firmware (Ubuntu Questing):
importance: Undecided → High
Changed in linux-firmware (Ubuntu Noble):
assignee: nobody → You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu Plucky):
assignee: nobody → You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu Questing):
assignee: nobody → You-Sheng Yang (vicamo)
Revision history for this message
You-Sheng Yang (vicamo) wrote :
You-Sheng Yang (vicamo)
description: updated
summary: - multiple functions in GUI unusable, stall with AMD Krackan 2
+ [SRU] multiple functions in GUI unusable, stall with AMD Krackan 2

From OEM bug report this doesn't only affect DCN on KRK2, it is also reported on DCN for STX/KRK.

From AMD investigation the issue could reproduce on DCN for 2 other ASIC as well (HPT and STXH) so all should be updated for this issue. That's why single commit upstream covers all of them.

You-Sheng Yang (vicamo)
description: updated
tags: added: kernel-daily-bug
Juerg Haefliger (juergh)
Changed in linux-firmware (Ubuntu Plucky):
status: In Progress → Fix Committed
Changed in linux-firmware (Ubuntu Noble):
status: In Progress → Fix Committed
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into plucky-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20250317.git1d4c88ee-0ubuntu1.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-plucky to verification-done-plucky. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-plucky. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20240318.git3b128b60-0ubuntu2.18 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into plucky-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20250317.git1d4c88ee-0ubuntu1.9 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-plucky to verification-done-plucky. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-plucky. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20240318.git3b128b60-0ubuntu2.19 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted linux-firmware (20250317.git1d4c88ee-0ubuntu1.9) for plucky have finished running.
The following regressions have been reported in tests triggered by the package:

linux-firmware-raspi/unknown (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/plucky/update_excuses.html#linux-firmware

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted linux-firmware (20240318.git3b128b60-0ubuntu2.19) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

linux-firmware-raspi/unknown (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#linux-firmware

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Juerg Haefliger (juergh)
Changed in linux-firmware (Ubuntu Questing):
status: In Progress → Fix Committed

Verified from ODM.

tags: added: verification-done-noble verification-done-plucky
Revision history for this message
Julian Andres Klode (juliank) wrote :

"Verified from ODM." is not an acceptable verification statement for an SRU.

Per https://documentation.ubuntu.com/sru/en/latest/reference/requirements/:
> All referenced bugs have a QA report in a bug comment explaining how the Test Plan was performed, what package version was tested, and what the overall result was (pass or fail).

This is missing "how" and "what ... version".

tags: added: verification-needed-noble verification-needed-plucky
removed: verification-done-noble verification-done-plucky
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Updated test steps in the SRU justification.

description: updated
tags: added: verification-done-noble verification-done-plucky
removed: verification-needed-noble verification-needed-plucky
description: updated
Revision history for this message
AceLan Kao (acelankao) wrote :

Verified with linux-firmware 20250317.git1d4c88ee-0ubuntu1.9/plucky, can't see any graphics issue with 4k youtube video playback and snapshot camera preview.

ODM helps to do the same test with linux-firmware 20240318.git3b128b60-0ubuntu2.19/noble, all tests passed.

Revision history for this message
Anthony Wong (anthonywong) wrote :

This OEM platform went through a long period of behind-the-scenes debugging, which made some information outdated. I have updated the bug title and description to reflect the current state.

description: updated
summary: - [SRU] multiple functions in GUI unusable, stall with AMD Krackan 2
+ [SRU] Graphics issues at 4K video playback on AMD Krackan Point 2
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into questing-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20250901.git993ff19b-0ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-questing to verification-done-questing. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-questing. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message