From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What is the difference between a kernel BUG and a kernel Oops?
Date: Sat, 3 Mar 2012 11:55:47 +0100 [thread overview]
Message-ID: <20120303105546.GA2324@grml> (raw)
In-Reply-To: <COL115-DS56D596A072C201517B023BC520@phx.gbl>
Hi!
On 17:38 Sat 03 Mar , hujun_hotmail wrote:
> I want to know what is the difference between a kernel BUG and a kernel Oops , who can tell me?
A BUG() is something like an assertion. Basically this means that a developer
thought that a certain situation should never be happen and if it does,
execution should stop. It is possible to ignore this and continue executing:
config BUG
bool "BUG() support" if EXPERT
default y
help
Disabling this option eliminates support for BUG and WARN, reducing
the size of your kernel image and potentially quietly ignoring
numerous fatal conditions. You should only consider disabling this
option for embedded systems with no facilities for reporting errors.
Just say Y.
A kernel oops is basically a crash. This can be caused by bad memory accesses
and things like that.
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2012-03-03 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 9:38 What is the difference between a kernel BUG and a kernel Oops? hujun_hotmail
2012-03-03 10:55 ` michi1 at michaelblizek.twilightparadox.com [this message]
2012-03-03 13:49 ` hujun_hotmail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120303105546.GA2324@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.