Black screen on boot after stable update

[Marcin Slusarz]

After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-18-generic 5.11.0-18.19
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: marcin 1374 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 26 11:55:00 2021
InstallationDate: Installed on 2021-05-02 (55 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: HP HP Pavilion Laptop 15-eg0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-18-generic N/A
 linux-backports-modules-5.11.0-18-generic N/A
 linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/2021
dmi.bios.release: 15.12
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 87CB
dmi.board.vendor: HP
dmi.board.version: 34.27
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 34.27
dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-eg0xxx
dmi.product.sku: 2Q2T4EA#AKD
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Dylan Stephano-Shachter (dylanstathis)]

I have hit this bug as well. Please let me know if there is any information I can provide.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Heinz Burgstaller (heinz-burgstaller)]

I have this bug as well. With an HP Probook 450 G7 (Core i7 10thGen)

[Heinz Burgstaller (heinz-burgstaller)]

The Laptops display is blank (shut off), but external monitors work (HDMI and USB-C). The only workaround is to boot kernel 5.11.0-18.

[Heinz Burgstaller (heinz-burgstaller)]

@Dylan please mark in the header that you are affected as well. Thank you

[Heinz Burgstaller (heinz-burgstaller)]

Did a BIOS update to 01.09.00 Rev.A. Did not solve the problem

[Dylan Stephano-Shachter (dylanstathis)]

After reading the above comment, I checked if there was a BIOS update. I updated to the latest BIOS and now I can boot fine.

[Aleksandr Rytov (arytov)]

This bug in kernel bugtracker
https://bugzilla.kernel.org/show_bug.cgi?id=213615

[Marcin Slusarz (marcin-slusarz)]

This is NOT a duplicate of bug #1934647 - there's no Nvidia or AMD card in this laptop (it's Intel-only) and regressing kernel version is different. If I connect an external monitor I can see the purple background on it, but the login window is on the internal one and I can't blindly login because of another bug, where keyboard input is ignored in ~80% of cases until I click on the username and back button a couple of times.

[Marcin Slusarz (marcin-slusarz)]

f6f30065b430ef670e5a163577634941c20f8855 is the first bad commit
commit f6f30065b430ef670e5a163577634941c20f8855
Author: Ville Syrj�l� <email address hidden>
Date: Thu May 6 17:44:00 2021 +0200

    drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure

    BugLink: https://bugs.launchpad.net/bugs/1925685

    Some new eDP panels don't like to operate at the max parameters, and
    instead we need to go for an optimal confiugration. That unfortunately
    doesn't work with older eDP panels which are generally only guaranteed
    to work at the max parameters.

    To solve these two conflicting requirements let's start with the optimal
    setup, and if that fails we start again with the max parameters. The
    downside is probably an extra modeset when we switch strategies but
    I don't see a good way to avoid that.

    For a bit of history we first tried to go for the fast+narrow in
    commit 7769db588384 ("drm/i915/dp: optimize eDP 1.4+ link config
    fast and narrow"). but that had to be reverted due to regression
    on older panels in commit f11cb1c19ad0 ("drm/i915/dp: revert back
    to max link rate and lane count on eDP"). So now we try to get
    the best of both worlds by using both strategies.

    v2: Deal with output_bpp and uapi vs. hw state split
        Reword some comments
    v3: Rebase

    Cc: Jani Nikula <email address hidden>
    Cc: Rodrigo Vivi <email address hidden>
    Cc: Albert Astals Cid <email address hidden> # v5.0 backport
    Cc: Emanuele Panigati <email address hidden> # v5.0 backport
    Cc: Matteo Iervasi <email address hidden> # v5.0 backport
    Cc: Timo Aaltonen <email address hidden>
    Cc: Kai-Heng Feng <email address hidden>
    Reviewed-by: Manasi Navare <email address hidden>
    References: https://bugs.freedesktop.org/show_bug.cgi?id=105267
    References: https://bugs.freedesktop.org/show_bug.cgi?id=109959
    References: https://gitlab.freedesktop.org/drm/intel/issues/272
    Signed-off-by: Ville Syrj�l� <email address hidden>
    Link: https://patchwork.<email address hidden>
    (cherry picked from commit 2bbd6dba84d44219387df051a1c799b7bac46099)
    Signed-off-by: Kai-Heng Feng <email address hidden>
    Acked-by: Tim Gardner <email address hidden>
    Acked-by: Stefan Bader <email address hidden>
    Signed-off-by: Kleber Sacilotto de Souza <email address hidden>

 drivers/gpu/drm/i915/display/intel_display_types.h | 1 +
 drivers/gpu/drm/i915/display/intel_dp.c | 75 +++++++++++++++++++---
 2 files changed, 67 insertions(+), 9 deletions(-)

[Marcin Slusarz (marcin-slusarz)]

Reverting this commit on top of Ubuntu-5.11.0-22.23 tag (with a minor conflict in a comment) yields a working system.

[z1231561656 (michal1702-deactivatedaccount-deactivatedaccount)]

Hi,
I have the same problem. I am currently using Ubuntu 21.04 and 5.11.0-16-generic, because newer versions cause the internal monitor to not work (HDMI and displayport work).

Is it normal that on a new laptop (with Intel Tiger Lake and Intel Xe) new versions of the Kernel cause the internal monitor to fail?

I can't even install Ubuntu 21.10 daily builds (unless in Safe Graphics mode), because Kernel 5.13 is probably there by default, which does not work at all on the HP Pavilion laptop with Intel i5-1135G7 and Intel Xe (internal monitor).

I updated my laptop firmware to F.20, but the problem persists.

The problem has been around for several weeks and I don't know who I can ask to solve this problem, because I don't know if it's an Ubuntu or Kernel problem?

[Heinz Burgstaller (heinz-burgstaller)]

It's a kernel problem, I think. There is another thread for Arch Linux: https://bugs.archlinux.org/task/71003

[Mike E. (melkevizth)]

Just to add a little more information, I have the same issue with a HP ProBook 450 G6 with an i7-8565U processor. I am running 20.04 and have had to stick with the 5.8.0-55-generic kernel because anything newer (e.g. 5.8.0-59-generic) causes this bug to rear its ugly head. I can set GRUB_CMDLINE_LINUX_DEFAULT="nomodeset" in the /etc/default/grub file and get the main monitor to display, but then external monitors no longer work.

[Aleksandr Rytov (arytov)]

In freedesktop
https://gitlab.freedesktop.org/drm/intel/-/issues/3440

[Aaron Peromsik (aperomsik)]

Still happens on 21.10's 5.13.16-051316-generic with a fairly new HP Pavilion 15. The workaround from Arch doesn't quite help -- internal monitor did work after that but external display is not detected.

[Aaron Peromsik (aperomsik)]

Tried some recent mainline kernels again. No luck with 5.13.19, but 5.14.13 is using both displays just fine. (Earlier I had tried 5.14.3 with no luck.)

[Mike E. (melkevizth)]

Just updated to 5.11.0-38-generic on my ProBook 450 G6 with an i7-8565U processor and both displays are back to working again. On 20.04 focal. 5.11.0-37-generic did not work, so it was something that was part of the -38 update that fixed the issue for me.

[Marcin Slusarz (marcin-slusarz)]

5.11.0-38-generic also works for me.