Drm_panic is a new feature in the Linux kernel that displays a panic screen when a kernel panic occurs. This proposal is to enable DRM_PANIC in the Fedora kernel, to improve the kernel panic user experience.
Owners, do not implement this work until the FESCo vote has explicitly ended. The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.
REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the devel list thread linked above.
+1
+1 and many thanks to @jfalempe for incorporating the discussion feedback.
looks great! +1
+1 and yes, thanks for improving the proposal during the feedback!
I have no interest in a mandate to turn this on until such time as the proposed patches have been accepted and merged upstream.
Fortunately, this is targeting Fedora 42, so there's plenty of time.
+1, but certainly not a "mandate" if upstream work isn't completed in time. The Change already states the contingency to revert the configuration.
I've also made a proof of concept to add a panic screen with a QR code with debugging information,
I also want to call out that this extension would be the first Rust requirement in the Fedora kernel. There are some risks in how Rust-for-Linux still relies on unstable features (as in "subject to change", not quality), but QR can be dropped if that becomes problematic.
This should not be an issue anymore starting with Linux 6.11, as the forked alloc crate is gone and the kernel now has a widening range of Rust compilers supported (1.78, 1.79, and 1.80). I expect that going forward, they will be much more proactive about ensuring that newer Rust compilers are supported.
alloc
Rust is less of an issue without forked alloc, and upstream Rust is also testing R4L in CI now -- not necessarily blocking but at least making it louder when things do change. Rust might also come in as a kernel requirement for other driver enablement anyway, before this QR change.
+1.
I still have some doubts how this will play out, in particular wrt. to debugging. But I think we should enable this and see how things play out. If it's not ready to be the default for F42, we can always postpone. Or we can curtail the scope to e.g. only Workstation or something like that. So I think we should keep an eye out to reports from users and developers.
After a week (and a few days): APPROVED (+7, 0, 0)
Metadata Update from @zbyszek: - Issue tagged with: pending announcement
Announced.
Metadata Update from @jistone: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
@amoloney This change has not been updated in the wiki and there's no F42 ChangeSet page. Can you please look into this?
Yep will take care of it today.
Log in to comment on this ticket.