Latest revision as of 15:05, 2 September 2024

Enable Drm Panic

Summary

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.

Owner

Name: Jocelyn Falempe, Javier Martinez Canillas
Email: <jfalempe@redhat.com>, <javierm@redhat.com>

Current status

Targeted release: Fedora Linux 42
Last updated: 2024-09-02
Announced
Discussion thread
FESCo issue: #3254
Tracker bug: #2309205
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

When the linux kernel panics in Fedora 40, in most cases, the screen just freezes. If you're in a VT console, you'll be able to see the kernel debug information, but that is pretty hard to understand for users that are not kernel developers. With this feature, they will see a message saying the computer has crashed, and they need to reboot the computer. Drm_panic has been introduced in kernel v6.10, but is still under active development.

Supported drivers are simpledrm, mgag200, ast, (and imx, tidss, on aarch64). I'm working on nouveau support, and I hope i915 and amdgpu will add support too. If the driver is not supported, you won't see the panic screen, but it won't be worse than what you have today.

Drm panic provides different panic screens. The default is "user" which will display a simple friendly message telling the user to reboot the computer. But for kernel developers, you can also set it to "kmsg", to see the last kmsg lines (so this is equivalent to the current fbcon). You can select the panic screen in Kconfig, or as a module parameter (drm.panic_screen=user) or at runtime with "echo -n kmsg > /sys/module/drm/parameters/panic_screen"

I've also made a proof of concept to add a panic screen with a QR code with debugging information, which will make it easier for users to report kernel panic in Fedora. An example can be seen here: https://github.com/kdj0c/panic_report/issues/1

Feedback

Benefit to Fedora

This change will improve the user experience when a kernel panic occurs. And it will help to report and debug kernel panics.

It's also a first step to switch to userspace console, and being able to disable CONFIG_VT in the kernel. VT and fbcon are legacy part of the kernel, that would reduce maintenance burden if we can disable them. It will also reduce CVE impact, as userspace vulnerabilities are usually less critical.

Scope

Proposal owners:

No changes are required to the boot process.

Other developers:

Release engineering: #Releng issue number

There should be no impact on the installer.

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with the Fedora Strategy:

I think it perfectly fit the "Fedora is for everyone" goal, as the current kernel panic (either UI freeze or kmsg output in VT) is not user-friendly.

Upgrade/compatibility impact

Enabling DRM_PANIC should be transparent to user. If your graphic driver doesn't support drm_panic, you will still see the old kernel panic message if you're in a VT, or it will freeze in graphic mode. If your graphic driver supports drm_panic, you will see the new panic screen.

Early Testing (Optional)

Do you require 'QA Blueprint' support? Y/N

How To Test

Currently the easiest way to test, is to use the simpledrm driver, as it can run on all hardware. So first blacklist your driver (i915, amdgpu or nouveau), and then boot and check that you're using simpledrm. then you can trigger a kernel panic with: echo c > /proc/sysrq-trigger

As it will crash your machine, it's also possible to do this in a VM (so disabling virtio-gpu, or vmwgfx)

Also to check that you can still see the kernel messages at boot, in the grub menu, remove the "quiet" kernel command argument, and you should still see the kernel boot messages on the plymouth screen.

User Experience

With DRM panic, users will be notified that their computer crashed, instead of it being unresponsive.

With v6.10, it's only for a few GPU drivers (simpledrm, mgag200, ast), but with simpledrm, it will already catch some common kernel panic cases, like root filesystem not found, or ramdisk corruption. (simpledrm is used at boot, and is later replaced with i915/amdgpu/nouveau ...)

It also prepares for future drm panic improvements, like having a kmsg panic screen, (should be available in v6.11) or also have better debugging information, using QR code. A test sample is shown at https://github.com/kdj0c/panic_report/issues/1

The panic screen can be customized, (background/foreground colors). And a Fedora logo can be added too, but probably with an out-of-tree patch. Maybe UI or Marketing experts can help make it better fit the Fedora design.

Dependencies

The main dependency, is to have a kernel v6.11 or later.

You will also need this patch to make drm_panic works with fbcon/vt_console: https://patchwork.freedesktop.org/series/136182/ that will land in v6.12

Contingency Plan

Contingency mechanism: Revert the kernel configuration changes.
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

Kernel Kconfig for DRM_PANIC: https://elixir.bootlin.com/linux/v6.10-rc7/source/drivers/gpu/drm/Kconfig#L107

Release Notes

@@ Line 2: / Line 2: @@
 = Enable Drm Panic <!-- The name of your change proposal --> =
-{{Change_Proposal_Banner}}
 == Summary ==
@@ Line 24: / Line 22: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF42]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 31: / Line 29: @@
 <!-- Select proper category, default is Self Contained Change -->
-[[Category:SystemWideChange]]
+[[Category:SelfContainedChange]]
-* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f<VERSION>/ Fedora Linux <VERSION>]
+* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f42/ Fedora Linux 42]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 41: / Line 39: @@
 ON_QA -> change is fully code complete
 -->
-* [Announced]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/OMAPEK63F3MTT3F4YELEIEOJHHC5BPXF/ Announced]
-* [<will be assigned by the Wrangler> Discussion thread]
+* [https://discussion.fedoraproject.org/t/f42-change-proposal-enable-drm-panic-system-wide/125542 Discussion thread]
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/3254 #3254]
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2309205 #2309205]
 * Release notes tracker: <will be assigned by the Wrangler>
@@ Line 54: / Line 52: @@
 With this feature, they will see a message saying the computer has crashed, and they need to reboot the computer.
 Drm_panic has been introduced in kernel v6.10, but is still under active development.
-In order to enable DRM_PANIC, you need to disable VT_CONSOLE in the kernel, this is to prevent a race condition, that if you are in a VT console when the panic occurs, both fbcon and drm_panic will write to the framebuffer at the same time, leading to corrupted output.
-https://patchwork.freedesktop.org/series/134831/
-The drawback is that tty0 won't show the kernel kmsg, and it can be harder to debug boot issues. But plymouth already takes care of this, and can display the boot kmsg when no VT console is present. https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/224
-And the user experience would be better, because plymouth has better font and color support than fbcon.
 Supported drivers are simpledrm, mgag200, ast, (and imx, tidss, on aarch64). I'm working on nouveau support, and I hope i915 and amdgpu will add support too.
@@ Line 100: / Line 93: @@
 -->
-This change will improve the user experience when a kernel panic occurs.
+This change will improve the user experience when a kernel panic occurs. And it will help to report and debug kernel panics.
 It's also a first step to switch to userspace console, and being able to disable CONFIG_VT in the kernel.
-VT and fbcon are legacy part of the kernel, that would reduce maintenance burden if we can disable them, and
+VT and fbcon are legacy part of the kernel, that would reduce maintenance burden if we can disable them.
 It will also reduce CVE impact, as userspace vulnerabilities are usually less critical.
@@ Line 110: / Line 103: @@
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-Write documentation on how-to debug boot issues without VT_CONSOLE.
+No changes are required to the boot process.
-Maybe also change the systemd log configuration, so that it default to writing the log to the console.
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 123: / Line 115: @@
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
-I'm unsure if it has impact on the installer.
+There should be no impact on the installer.
 * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 139: / Line 131: @@
 <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
-Enabling DRM_PANIC should be transparent to user, but disabling VT_CONSOLE may have a visible impact.
+Enabling DRM_PANIC should be transparent to user.
-Fortunately since Fedora 40, plymouth is able to display the kmsg messages.
+If your graphic driver doesn't support drm_panic, you will still see the old kernel panic message if you're in a VT, or it will freeze in graphic mode.
+If your graphic driver supports drm_panic, you will see the new panic screen.
-For non-graphical boot, you can use systemd.log_target=console systemd.log_level=info and remove rhgb and quiet to see the kernel boot message.
-But this needs to be documented, and communicated, so that users that debug boot issues, know about this change.
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 195: / Line 184: @@
 It also prepares for future drm panic improvements, like having a kmsg panic screen, (should  be available in v6.11) or also have better debugging information, using QR code. A test sample is shown at https://github.com/kdj0c/panic_report/issues/1
+The panic screen can be customized, (background/foreground colors). And a Fedora logo can be added too, but probably with an out-of-tree patch. Maybe UI or Marketing experts can help make it better fit the Fedora design.
 == Dependencies ==
@@ Line 201: / Line 192: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-The main dependency, is to have a kernel v6.10 or later.
+The main dependency, is to have a kernel v6.11 or later.
-To still see the kernel boot messages, there is also a dependency on plymouth and systemd, but the versions in F40 are already good.
+You will also need this patch to make drm_panic works with fbcon/vt_console: https://patchwork.freedesktop.org/series/136182/ that will land in v6.12
 == Contingency Plan ==

Search

Changes/EnableDrmPanic: Difference between revisions