FS#72134 - linux 5.14.* gpu bug with i915 DRM
Attached to Project:
Arch Linux
Opened by Nicolas Joyard (njoyard) - Tuesday, 14 September 2021, 16:07 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 06 June 2023, 04:01 GMT
Opened by Nicolas Joyard (njoyard) - Tuesday, 14 September 2021, 16:07 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 06 June 2023, 04:01 GMT
|
Details
Bug is present both in linux-5.14.2arch1-2 and
linux-5.14.3arch1-1.
Fixed by reverting to linux-5.13.13.arch1-1 Hardware: Dell XPS15 2-in-1 9575 with Intel UHD 630 iGPU and AMD Vega M dGPU > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) > 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XL [Radeon RX Vega M GL] (rev c0) Symptoms: on first reboot after upgrade to 5.14.2, after a few (normal) boot messages display flickers with graphical glitches all over the place (mostly blank screen, blueish lines sweeping from the top of the screen). Ruled out plymouth, gdm and sway: same issue with those removed and booting to a tty. Ruled out a hardware failure: Ubuntu live USB boots fine. Both GPUs are usable. Boot to tty is possible when using i915.modeset=0 (or nomodeset) but then no DRM is available and I cannot run sway. The only relevant thing I noticed is the following kernel message (not present with 5.13): > i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Attaching the output of lspci -vvnn and a full journalctl dump for the kernel in a failing boot. Not sure which other details are relevant, feel free to ask for more. |
This task depends upon
Closed by Toolybird (Toolybird)
Tuesday, 06 June 2023, 04:01 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Tuesday, 06 June 2023, 04:01 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
@Lee's workaround (adding i915.fastboot=0) fixes the problem.
Until now I had stayed on 5.12.x because of https://bugzilla.kernel.org/show_bug.cgi?id=213823 (don’t/didn’t you had this issue too?), but I wanted to check whether it might have been fixed at some point. Instead, I ended up with a non-booting 5.14 kernel with exactly the same symptoms as you describe. I’ve moved to LTS for now on since I lack time to investigate this.
However this is not the right place to report this issue, it should be at the linked above bug tracker. I’ll try to do this in ~2 weeks if you don’t do it before.
I wanted to do a git bisect on the kernel but this takes a lot of time, so I haven't got to it yet. Plus I'm less motivated now because my laptop is getting replaced with a 9500 soon (due to keyboard keys breaking every 6 months on the 9575). Maybe I'll find the motivation back and make a nice bug report.
P.S.: On my side, no issue with the keyboard whatsoever.