Kernel panic

This article does not cite any references or sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2009)

Linux kernel panic caused by a hard disk hardware failure.

A kernel panic in FreeBSD, forced by sending SIGSEGV to init.

Mac OS X kernel panic alert. Debugging information is saved in NVRAM and written to a log file on reboot. This version is present in Mac OS X 10.3 and above (Mac OS X 10.1 and 10.2 had a white background).

A kernel panic is an action taken by an operating system upon detecting an internal fatal error from which it cannot safely recover. The term is largely specific to Unix and Unix-like systems; for Microsoft Windows operating systems the equivalent term is "Stop error" (or, colloquially, "Blue Screen of Death").

The kernel routines that handle panics (in AT&T-derived and BSD Unix source code, a routine known as panic()) are generally designed to output an error message to the console, dump an image of kernel memory to disk for post-mortem debugging and then either wait for the system to be manually rebooted, or initiate an automatic reboot. The information provided is of highly technical nature and aims to assist a system administrator or software developer in diagnosing the problem.

Attempts by the operating system to read an invalid or non-permitted memory address are a common source of kernel panics. A panic may also occur as a result of a hardware failure or a bug in the operating system. In many cases, the operating system could continue operation after memory violations have occurred. However, the system is in an unstable state and rather than risking security breaches and data corruption, the operating system stops to prevent further damage and facilitate diagnosis of the error.

The kernel panic was introduced in an early version of Unix and demonstrated a major difference between the design philosophies of Unix and its predecessor Multics. Multics developer Tom van Vleck recalls a discussion of this change with Unix developer Dennis Ritchie:

I remarked to Dennis that easily half the code I was writing in Multics was error recovery code. He said, "We left all that stuff out. If there's an error, we have this routine called panic, and when it is called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"^[1]

The original panic() function was essentially unchanged from Fifth Edition UNIX to the VAX-based UNIX 32V and output only an error message with no other information, then dropped the system into an endless idle loop. As the Unix codebase was enhanced, the panic() function was also enhanced to dump various forms of debugging information to the console.

See also

• Bug check
• Screens of death
• Linux kernel OOPS

References

External links

Wikimedia Commons has media related to: Screens of death

• The Solaris Operating System on x86 Platforms: Crashdump Analysis Operating System Internals
• "Panic! Unix System Crash Dump Analysis" (SunSoft Press / Prentice Hall book by Chris Drake & Kimberley Brown
• The file prf.c from Version 6 Unix and the Lions Book, containing the panic() routine as implemented on early Unix systems (will not compile with modern C compilers)
• Kernel panic source code examples from OpenSolaris, Darwin/Mac OS X, Minix, and Linux

v • d • e Screens of death Colors Black · Blue · Red · White Other screens Kernel panic · Sad Mac · Bomb · Red Ring of Death · Row of bombs · Guru Meditation · Kill screen

This Unix-related article is a stub. You can help Wikipedia by expanding it. v • d • e