The infra for a "blue screen of death" in the #LinuxKernel has landed in #linux-next[1] and thus is slated for inclusion in #kernel 6.10:
https://lore.kernel.org/all/20240409163432.352518-1-jfalempe@redhat.com/
"'This introduces a new drm panic handler, which displays a message when a panic occurs. So when fbcon is disabled, you can still see a kernel panic.
[…]
It works with simpledrm, mgag200, ast, and imx.
[…]
Even if this is not yet useful, it will allows to work on more driver support, […]"'
[¹] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=grep&q=drm%2Fpanic
@pavel @kernellogger Nah, they're now on the same boat with us, being chased by the other big fish…
because it was hard to realize given the graphics stack and its history; you get a brief idea here:
https://dri.freedesktop.org/docs/drm/gpu/todo.html#make-panic-handling-work
Who speaks there?
An employee of a well known company that has something like that for many years now or the maintainer of a software that later implemented something like that? ;-)
/me runs and hides
@kernellogger i think the underlying goal of "make it possible to run linux systems without VTs/fbcon (and, if necessary, use wayland to provide a recovery console)" is kinda interesting
personally gonna miss the ol' reliable framebuffer console, but the fact it's so full of hard-to-maintain code that a security vulnerability had to be fixed by just disabling scrollback kinda proves that its time is way past
yeah!
Somehow I lost track what will serve as replacement(s) for systems that want/need one. Kmscon seems kinda stalled. Or is there something else in the works?
@kernellogger it was supposed to be a very meta comment.