The way to get useful information out of the intel kernel driver is to
add “drm.debug=0x04” to the kernel boot commandline, which will cause
the kernel module to print out a bunch of modesetting debugging
information. Since this problem goes back to boot with the plymouth
splash screen, it's clearly a problem in the kernel module's
modesetting.
It's very strange that it appears non-deterministic!
The way to get useful information out of the intel kernel driver is to
add “drm.debug=0x04” to the kernel boot commandline, which will cause
the kernel module to print out a bunch of modesetting debugging
information. Since this problem goes back to boot with the plymouth
splash screen, it's clearly a problem in the kernel module's
modesetting.
It's very strange that it appears non-deterministic!