Editing Kernel panic (section)

===Linux===
{{See also|kdump (Linux)}}
[[File:Kernel panic message.png|thumb|Kernel panic as seen on an iKVM console]]
[[File:Drm panic message.png|thumb|Kernel panic with drm_panic enabled]]
[[File:Drm panic with qr code.png|thumb|Kernel Panic with drm_panic enabled supporting logging to QR Codes]]

Kernel panics appear in [[Linux]] like in other [[Unix-like]] systems; however, serious but non-fatal errors can generate another kind of error condition, known as a [[Linux kernel oops|kernel oops]].<ref>{{cite web|url=https://lwn.net/images/pdf/LDD3/ch04.pdf|title=''Linux Device Drivers'', Chapter 4|access-date=July 21, 2016|archive-date=November 14, 2014|archive-url=https://web.archive.org/web/20141114011920/http://lwn.net/images/pdf/LDD3/ch04.pdf|url-status=live}}</ref> In this case, the kernel normally continues to run after [[kill (Unix)|killing]] the offending [[process (computing)|process]]. As an oops could cause some subsystems or resources to become unavailable, they can later lead to a full kernel panic.

On Linux, a kernel panic causes keyboard LEDs to blink as a visual indication of a critical condition.<ref>{{cite book
 | url = https://books.google.com/books?id=FyRhZJ3h3VQC&q=linux+kernel+panic+keyboard+led+blinking&pg=PA62
 | title = Linux Troubleshooting for System Administrators and Power Users
 | date = May 2006
 | access-date = 2016-02-05
 | author1 = James Kirkland
 | author2 = David Carmichael
 | author3 = Christopher L. Tinker
 | author4 = Gregory L. Tinker
 | publisher = [[Prentice Hall]]
 | page = 62
 | isbn = 9780132797399
 | archive-date = April 1, 2024
 | archive-url = https://web.archive.org/web/20240401232239/https://books.google.com/books?id=FyRhZJ3h3VQC&q=linux+kernel+panic+keyboard+led+blinking&pg=PA62#v=snippet&q=linux%20kernel%20panic%20keyboard%20led%20blinking&f=false
 | url-status = live
 }}</ref>

As of Linux 6.10, drm_panic was merged allowing [[Direct Rendering Manager|DRM]] drivers to support drawing a panic screen to inform the user that a panic occurred. This allows a panic screen to appear even when a display server was running when the panic occurred.<ref>{{cite web |url=https://fedoraproject.org/wiki/Changes/EnableDrmPanic |title=Changes/EnableDrmPanic |work=Fedora Project Wiki}}</ref>

As of Linux 6.12, drm_panic was extended where the stack trace can be encoded as a [[QR code]].<ref>{{cite mailing list |url=https://lore.kernel.org/dri-devel/20240829144654.GA145538@linux.fritz.box/ |title=[PULL] drm-misc-next |author=Thomas Zimmermann |date=29 August 2024 |mailing-list=dri-devel}}</ref>