Linux: Kernel Panic
A kernel panic is a message displayed by an operating system upon detecting an internal system error from which it cannot recover; the term is largely specific to Unix and Unix-like systems, as well as the Unix successor Plan 9. The kernel routines that handle panics (in AT&T-derived Unix source code, a routine known as panic()) are generally designed to dump debugging information to either the screen or a specified file and then freeze the computer. The information provided is not always useful to the end user, but can sometimes provide troubleshooting data for a system developer or tech support personnel.
Attempts by the operating system to read an invalid or unpermitted 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.
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.’”
The original panic() function was essentially unchanged from V5 to the VAX-based 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 terminal.
A kernel panic usually takes the form of a text dump to the main screen of the computer, sometimes overwriting any graphical content on the screen. A notable exception is that of later versions of Mac OS X, which generally hide the text dump behind a message to reboot the system; the debugging information is still available as a logfile.
I miss so much the Amiga’s Guru Meditation, at least the computer crashed with games and not in the middle of an important task or in a real production enviroment…
BTW, I don’t remember the last time that my XP PRO Workstation or any of the WINDOWS 2003 Servers I have at work crashed….
3 Comments so far
Leave a reply
Nice try!
buen intento … pero Microsoft juega su ultima carta con Windows Bosta y a partir de ahi se hunde como el Titanic… empieza a vender SUSE-Linux o que llame a James Bond, una de dos, el tiempo dira. W2003 SErver ? … no comment
ah .. tambien me gusta mucho mas la WII de nintendo ! , grosaaaa, innovadora y baratita !
jeje, me vas a decir que soy el contra , pero asi es el mundo,cada uno con sus gustos, si no seriamos todos iguales y seria feo , no?
saludos
FernandO no seas paranoico… intento de que?
El windows 2003 server anda realmente bien, y de verdad no recuerdo cuando fue la ultima vez que se cayeron.
tengo unos cuantos con mysql, ms sql, oracle, weblogic, websphere, j-boss, ISS, Exchange, ISA y nunca un problema… me resulta muy reliable.
a mi entender Linux como idea esta bueno, como OS apesta.
No solo porque sea gratis lo voy a usar, yo busco calidad,
edito video, hago musica, uso photoshop , Linux no es valido como workstation para mi
a nivel server, ya dije todo “Kernel Panic” y mis amigos todos con el apache hackeado!
Respecto a mi XBOX, como lo tengo con un modchip, el OS que le puse es el EVO-X
De nuevo no estamos de acuerdo con el tema WII, jamas compraria una consola porque es mas barata, simplemente evaluaria los juegos que existen, que estan por salir y que saldran plus, las prestaciones que me da la consola.
Si mal no recuerdo el Nintendo CUBE era barato pero nintendo se lo metio en el culo.
Si el WII tiene buenos juegos, no dudaria en compralo, la verdad no creo que los juegos sean grosos, mi mente va hacia PS3 a pesar de tener un XBOX ahora.