This bug was fixed in the package linux-oem-5.17 - 5.17.0-1027.28

---------------
linux-oem-5.17 (5.17.0-1027.28) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1027.28 -proposed tracker (LP:
#2003451)

  * CVE-2022-3545
    - nfp: fix use-after-free in area_cache_get()

  * CVE-2022-42895
    - Bluetooth: L2CAP: Fix attempting to access uninitialized memory

  * ThinkPad L14 Gen 3 blank laptop screen on bootup (LP: #2002467)
    - Revert "drm/amdgpu: make sure to init common IP before gmc"

  * CVE-2023-0179
    - netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

  [ Ubuntu: 5.17.0-15.16~22.04.8 ]

  * jammy/linux-hwe-5.17: 5.17.0-15.16~22.04.8 -proposed tracker (LP: #2003452)
  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/2023.01.02)
  * Revoke & rotate to new signing key (LP: #2002812)
    - [Packaging] Revoke and rotate to new signing key
  * CVE-2022-45934
    - Bluetooth: L2CAP: Fix u8 overflow
  * CVE-2022-42896
    - Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM
    - Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm
  * 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 <timo.aalto...@canonical.com>  Mon, 23 Jan 2023
12:37:39 +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-3545

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-42895

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-42896

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-45934

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0179

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The commit in 5.17.0.1026.27 introduce an regression that leads to the panel 
of ThinkPad L14 Gen 3 becomes blank after bootup
  224dffc89a957 drm/amdgpu: make sure to init common IP before gmc

  [Fix]
  Revert this commit as it looks like it requires some other commits to work 
together, and from the discussion of the 5.10 stable, this commit has been 
reverted, too.
  https://gitlab.freedesktop.org/drm/amd/-/issues/2216

  BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with
  this commit, so no need to revert it.

  [Test]
  Verified by Aaron Ma and the bug reporter.

  [Where problems could occur]
  Revert this commit will lead to the keep rebooting issue be re-opened(bug 
2000110), I'll check the issue again and submit another solution for it.

  ================

  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
  blank shortly after bootup.

  As far as I can tell (the screen blanks pretty quickly, so I'm not
  100% sure), the last message before the screen disappears is this one:

  Jan  9 07:58:30 work kernel: [    1.321487] fb0: switching to amdgpu
  from EFI VGA

  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in
  the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
  5.17.0.1026.27.

  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.

  If I type the encryption password, it seems to progress to starting
  the system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+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

Reply via email to