i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic

[Tomas Zemek]

This is a regression introduced with the latest kernel (linux-image-5.8.0-49-generic).

Kubuntu 20.04, since upgrading kernel from version 5.8.0-48.54 to version 5.8.0-49.55 the system boots properly but the GUI often hangs, either immediately after user login to GUI or any time after that (screen stops updating with various artifacts and UI no longer responds) and computer has to be restarted. Messages like these appear in dmesg:

Apr 13 08:43:24 kubuntu kernel: [47776.927523] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Apr 13 08:43:24 kubuntu kernel: [47777.029098] i915 0000:00:02.0: [drm] VMSVGA FIFO[222240] context reset due to GPU hang

Apr 13 11:25:37 kubuntu kernel: [ 45.168120] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85fffffc, in plasmashell [2918]
Apr 13 11:25:37 kubuntu kernel: [ 45.168166] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Apr 13 11:25:37 kubuntu kernel: [ 45.270406] i915 0000:00:02.0: [drm] plasmashell[2918] context reset due to GPU hang
Apr 13 11:25:41 kubuntu kernel: [ 47.984475] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85fffffc, in plasmashell [2918]
Apr 13 11:25:41 kubuntu kernel: [ 47.984520] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Apr 13 11:25:41 kubuntu kernel: [ 48.088097] i915 0000:00:02.0: [drm] plasmashell[2918] context reset due to GPU hang
Apr 13 11:25:47 kubuntu kernel: [ 54.128068] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85fffffc, in plasmashell [2918]
Apr 13 11:25:47 kubuntu kernel: [ 54.128111] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Apr 13 11:25:47 kubuntu kernel: [ 54.230401] i915 0000:00:02.0: [drm] plasmashell[2918] context reset due to GPU hang

Apr 14 14:35:53 kubuntu kernel: [ 32.106297] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:c07fffff, in ksplashqml [3096]
Apr 14 14:35:53 kubuntu kernel: [ 32.106341] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Apr 14 14:35:53 kubuntu kernel: [ 32.207704] i915 0000:00:02.0: [drm] ksplashqml[3096] context reset due to GPU hang

With previous kernel 5.8.0-48.54 (and all other previous kernels) there was never any problem like this.

System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        DeviceName: Onboard IGD
        Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
        Flags: bus master, fast devsel, latency 0, IRQ 61
        Memory at f7400000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915
        Kernel modules: i915

Boot info with i915 and drm:
[ 0.000000] microcode: microcode updated early to revision 0x21, date = 2019-02-13
[ 0.000000] Linux version 5.8.0-49-generic (buildd@lgw01-amd64-055) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #55~20.04.1-Ubuntu SMP Fri Mar 26 01:01:07 UTC 2021 (Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18)
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.8.0-49-generic root=UUID=123 ro quiet splash vt.handoff=7
[ 0.000000] DMI: System manufacturer System Product Name/P8Z68-V PRO GEN3, BIOS 3802 01/15/2015
[ 1.083804] fb0: switching to inteldrmfb from EFI VGA
[ 1.083864] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 1.093201] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.097872] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 1.119734] [drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
[ 1.260356] fbcon: i915drmfb (fb0) is primary device
[ 1.260360] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
[ 5.070962] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[ 5.526454] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

Not blocking as I can stay on previous kernel but until this is fixed I can no longer use vulnerability fixes which makes the issue critical.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1923844/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

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

[hva (francesco-hermanitosverdes)]

maybe a duplicate:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1924624

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924624, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.