Created attachment 134416 [details]
plymouth start corrupted and the corruption stays in both gdm(wayland) and vt consoles
the systems works OK (other than warning in #101937) when it boots linux 4.12.14
Please boot with drm.debug=14 module parameter when adding dmesg.
Please take a picture, hard to assess what the corruption looks like.
If you can, please bisect.
Created attachment 134507 [details]
Created attachment 134509 [details]
corrupted gdm screen
captured screenshots are not corrupted, just the display.
I am also experiencing this issue with Archlinux 4.13.3, 4.13.4 and 4.13.5 running LightDM. Corruption happens on the console during boot and remains during LightDM and when logging in to XFCE.
Like you mentioned, on 4.12.x I also received the drm_atomic_helper_update_legacy_modeset_state calltrace but display worked OK. I now receive this error and the following:
[ 7.829242] plane B assertion failure, should be off on pipe B but is still active
[ 7.829292] ------------[ cut here ]------------
[ 7.829480] WARNING: CPU: 0 PID: 215 at drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915]
A quick search has bought up this bug report as well as the following from 4.3 which produces the same corruption and warning message:
Also experiencing this after upgrade, the same "plane B assertion failure, should be off on pipe B but is still active".
Adding i915.modeset=0 does not corrupt the screen but also sets the lowest resolution.
*** Bug 103223 has been marked as a duplicate of this bug. ***
There is a comment at
that commits at
should solve the issue.
*** This bug has been marked as a duplicate of bug 102929 ***