As Alessandro alluded to in comment #24, Plymouth using a "framebuffer"
(or rather 'fbdev') is probably what's happening. Such raw framebuffers
could be overwritten by other processes without the exclusive rights
over the display that a full DRM driver gives you.
The thing is, using fbdev ("framebuffer") is by design. We only want
simple framebuffer drivers in early boot because full DRM drivers are
getting too big and too slow to load (like 10 seconds to initialize).
The only non-compromising solution I can think of here is to prevent the
crash from happening in the first place. As a second choice, the log
level used for such crashes could be lowered so as to stay under the
"quiet" threshold and never written to the console.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
