Linux kernel oops
 |
An oops is a deviation from correct behavior of the Linux kernel which produces a certain error log. The better-known kernel panic condition results from many kinds of oops, but others may allow continued operation with compromised reliability. The term does not stand for anything, other than a simple mistake.
When the kernel detects a problem, it prints an oops message and kills any offending process. The message is used by Linux kernel engineers to debug the condition which created the oops and fix the programming error which caused it.
Once a system has experienced an oops, some internal resources may no longer be in service. Even if the system appears to work correctly, undesirable side effects may have resulted from the active task being killed. A kernel oops often leads on to a kernel panic once the system attempts to use resources which have been lost.
Kerneloops also refers to a software to collect and submit kernel oopses to the http://www.kerneloops.org/ website [1]. Kerneloops.org provides statistics of oopses .[2]
Further reading
- John Bradford (2003-03-08). "Re: what's an OOPS". LKML (Mailing list). Retrieved 2006-05-22.
{{cite mailing list}}: Unknown parameter|mailinglist=ignored (|mailing-list=suggested) (help) - Szakacsits Szabolcs (2003-03-08). "Re: what's an OOPS". LKML (Mailing list). Retrieved 2006-05-22.
{{cite mailing list}}: Unknown parameter|mailinglist=ignored (|mailing-list=suggested) (help) - Al Viro (2008-01-14). "OOPS report analysis". LKML (Mailing list). Retrieved 2008-01-14.
{{cite mailing list}}: Unknown parameter|mailinglist=ignored (|mailing-list=suggested) (help)
References
See also
System.map How to interpret oopses