This bug was fixed in the package linux - 6.1.0-16.16

---------------
linux (6.1.0-16.16) lunar; urgency=medium

  * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- temporarily drop broken dkms

 -- Andrea Righi <andrea.ri...@canonical.com>  Fri, 24 Feb 2023 14:24:48
+0100

** Changed in: linux (Ubuntu Lunar)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2003524

Title:
  amdgpu: framebuffer is destroyed and the screen freezes with
  unsupported IP blocks

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  From "Mario Limonciello mario.limonciello at amd.com"
  https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html.

  There is a problem in amdgpu that if not all of IP blocks are
  supported or not all of the firmware is present then the framebuffer
  is destroyed and the screen freezes.  In more recent kernels the
  amdgpu driver loads for all PCI VGA class AMD devices.

  This effectively means that unless you have all the pieces you need to
  support a GPU then the installer freezes unless you do nomodeset.

  This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that 
is currently in drm-next.  This does two basic things:
  1) If the IP blocks isn't supported, don't destroy the framebuffer.
  2) If firmware for any IP blocks aren't present, don't destroy the 
framebuffer.

  The whole patch series still needs more time to back in drm-next, but
  the most important part of the series is the first patch which
  accomplishes "1".

  This patch went out to stable 6.1.y as well:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y&id=dcfeba477b3e3df526e0f543b58fa71c045dff8b

  My reasoning is that it will ensure that if someone picks up a newer
  GPU such as Ryzen 7000 desktop or RDNA3 based they can at least
  install Ubuntu without needing to use "Safe Graphics Mode" at the
  installer.

  Sure; they won't have hardware acceleration without the rest of the
  kernel and framework, but that's a separate problem to a basic
  display.

  [Fix]
  Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a 
"drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 
kernel.

  [Test case]
  Boot kernel in a system with one of the amdgpu affected adapters.

  [Where problems can occur]
  The aforementioned commit could introduce other regressions on the support 
for AMD GPUs.

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