This bug was fixed in the package linux-oem-5.17 - 5.17.0-1026.27
---------------
linux-oem-5.17 (5.17.0-1026.27) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1026.27 -proposed tracker (LP:
#2001046)
* Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
(LP: #2000110)
- drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
- drm/amd/pm: disable BACO entry/exit completely on several sienna cichlid
cards
- drm/amdgpu: disable BACO on special BEIGE_GOBY card
- drm/amdgpu: disable BACO support on more cards
- drm/amdgpu: make sure to init common IP before gmc
* Fix SUT can't displayed after resume from WB/CB with dGFX
installed(FR:6/10)[RX6300][RX6500] (LP: #1999836)
- drm/amd/display: No display after resume from WB/CB
* CVE-2022-4378
- proc: proc_skip_spaces() shouldn't think it is working on C strings
- proc: avoid integer type confusion in get_proc_long
-- Timo Aaltonen <[email protected]> Wed, 04 Jan 2023
11:37:57 +0200
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1999836
Title:
Fix SUT can't displayed after resume from WB/CB with dGFX
installed(FR:6/10)[RX6300][RX6500]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
New
Status in linux-oem-6.0 source package in Kinetic:
New
Bug description:
[Impact]
SUT can't displayed after resume from WB/CB with dGFX installed.
Recovery: SUT can display when the DP cable unplug and plug .
[Fix]
Use quirk to block the affected SKUes.
[Test Case]
1.Install Ubuntu 22.04 on SUT with dGFX card.
2.Connect the DP cable to the dGFX port.
3.SUT do power off/restart.
4.SUT can display.
[Where problems could occur]
Add SKU's id to a quirk table, the impact would be small.
[Other Info]
* For the pure Jammy, Confronted the error of compilation.
1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work
~~~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error:
implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you
mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration]
18848 1449 | adev->dm.hpd_rx_offload_wq =
hpd_rx_irq_create_workqueue(adev->dm.dc);
18849 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
18850 | hdcp_create_workqueue
~~~
2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter
~~~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error:
implicit declaration of function 'dm_should_disable_ stutter'
[-Werror=implicit-function-declaration]
18838 1505 | if (dm_should_disable_stutter(adev->pdev))
~~~
* hpd_disconnect_quirk_table is placed to the different location on
J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all.
* Result from CBD
~~~
Jammy,
remote: *** kernel-cbd
*********************************************************
remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt
remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2
remote: * 192/672 cores busy (2/7 hosts), 0 builds queued
remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK
remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK
remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK
remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK
remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK
remote:
************************************************************************
To 54.69.112.110:jammy.git
~~~
Kinetic
remote: *** kernel-cbd
*********************************************************
remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt
remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz
remote: * 0/672 cores busy (0/7 hosts), 0 builds queued
remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK
remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK
remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK
remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK
remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK
remote:
************************************************************************
To 54.69.112.110:kinetic.git
~~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
