From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: magnade@gmail.com, jesper.juhl@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Doc: update oops-tracing.txt (Tainted flags)
Date: Thu, 8 Sep 2005 21:56:06 -0700 [thread overview]
Message-ID: <20050908215606.6c31790f.rdunlap@xenotime.net> (raw)
In-Reply-To: <20050906183008.GG10632@fieldses.org>
From: Randy Dunlap <rdunlap@xenotime.net>
Update Documentation/oops-tracing.txt:
- add descriptions of 3 more "Tainted" flags;
- fix some typos;
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
Documentation/oops-tracing.txt | 25 +++++++++++++++++--------
1 files changed, 17 insertions(+), 8 deletions(-)
diff -Naurp linux-2613-work/Documentation/oops-tracing.txt~doc_taint_update linux-2613-work/Documentation/oops-tracing.txt
--- linux-2613-work/Documentation/oops-tracing.txt~doc_taint_update 2005-08-28 16:41:01.000000000 -0700
+++ linux-2613-work/Documentation/oops-tracing.txt 2005-09-08 21:43:02.000000000 -0700
@@ -205,8 +205,8 @@ Phone: 701-234-7556
Tainted kernels:
Some oops reports contain the string 'Tainted: ' after the program
-counter, this indicates that the kernel has been tainted by some
-mechanism. The string is followed by a series of position sensitive
+counter. This indicates that the kernel has been tainted by some
+mechanism. The string is followed by a series of position-sensitive
characters, each representing a particular tainted value.
1: 'G' if all modules loaded have a GPL or compatible license, 'P' if
@@ -214,16 +214,25 @@ characters, each representing a particul
MODULE_LICENSE or with a MODULE_LICENSE that is not recognised by
insmod as GPL compatible are assumed to be proprietary.
- 2: 'F' if any module was force loaded by insmod -f, ' ' if all
+ 2: 'F' if any module was force loaded by "insmod -f", ' ' if all
modules were loaded normally.
3: 'S' if the oops occurred on an SMP kernel running on hardware that
- hasn't been certified as safe to run multiprocessor.
- Currently this occurs only on various Athlons that are not
- SMP capable.
+ hasn't been certified as safe to run multiprocessor.
+ Currently this occurs only on various Athlons that are not
+ SMP capable.
+
+ 4: 'R' if a module was force unloaded by "rmmod -f", ' ' if all
+ modules were unloaded normally.
+
+ 5: 'M' if any processor has reported a Machine Check Exception,
+ ' ' if no Machine Check Exceptions have occurred.
+
+ 6: 'B' if a page-release function has found a bad page reference or
+ some unexpected page flags.
The primary reason for the 'Tainted: ' string is to tell kernel
debuggers if this is a clean kernel or if anything unusual has
-occurred. Tainting is permanent, even if an offending module is
-unloading the tainted value remains to indicate that the kernel is not
+occurred. Tainting is permanent: even if an offending module is
+unloaded, the tainted value remains to indicate that the kernel is not
trustworthy.
---
next prev parent reply other threads:[~2005-09-09 4:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 0:15 nfs4 client bug Bret Towe
2005-09-04 3:05 ` Bret Towe
2005-09-04 10:35 ` Francois Romieu
2005-09-04 19:44 ` Bret Towe
2005-09-04 20:51 ` Bret Towe
2005-09-04 21:52 ` J. Bruce Fields
2005-09-05 3:08 ` Bret Towe
2005-09-05 3:18 ` J. Bruce Fields
2005-09-05 20:44 ` Bret Towe
2005-09-05 20:48 ` Jesper Juhl
2005-09-06 3:40 ` Bret Towe
2005-09-06 18:13 ` J. Bruce Fields
2005-09-06 18:21 ` Randy.Dunlap
2005-09-06 18:30 ` J. Bruce Fields
2005-09-06 18:40 ` Randy.Dunlap
2005-09-06 18:53 ` Valdis.Kletnieks
2005-09-09 4:56 ` Randy.Dunlap [this message]
2005-09-09 6:55 ` Bret Towe
2005-09-12 18:27 ` Bret Towe
2005-09-12 18:29 ` J. Bruce Fields
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=20050908215606.6c31790f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bfields@fieldses.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®