This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --------------- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen <timo.aalto...@canonical.com> Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955790 Title: Got black screen when resume from s2idle with AMD dGPU Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] On Dell AIO with AMD dGPU platforms, it looks like AMD dGPU can't be waken up after s2idle and got black screen. [Fix] AMD provides us 2 commits to fix this issue. https://patchwork.freedesktop.org/patch/463002/ https://patchwork.freedesktop.org/series/98338/ [Test] Verified by AMD. [Where problems could occur] It should be fine to reset the asic and set to the proper state while entering suspended. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp