summaryrefslogtreecommitdiff
path: root/Documentation/Changes
diff options
context:
space:
mode:
authorJesper Juhl <jesper.juhl@gmail.com>2005-11-07 12:01:03 +0300
committerLinus Torvalds <torvalds@g5.osdl.org>2005-11-07 18:53:54 +0300
commit62a07e6e9e93eda88a6eeb5009fc46d44ca60281 (patch)
tree6e5a0891a46b1d9864d5591a5961c63e1b818bea /Documentation/Changes
parent55032eacdb3acf54f5ba2e4dd9205db2c5c0bce2 (diff)
downloadlinux-62a07e6e9e93eda88a6eeb5009fc46d44ca60281.tar.xz
[PATCH] ksymoops related docs update
Update ksymoops related documentation to reflect current 2.6 reality. Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/Changes')
-rw-r--r--Documentation/Changes11
1 files changed, 8 insertions, 3 deletions
diff --git a/Documentation/Changes b/Documentation/Changes
index 783ddc3ce4e8..86b86399d61d 100644
--- a/Documentation/Changes
+++ b/Documentation/Changes
@@ -139,9 +139,14 @@ You'll probably want to upgrade.
Ksymoops
--------
-If the unthinkable happens and your kernel oopses, you'll need a 2.4
-version of ksymoops to decode the report; see REPORTING-BUGS in the
-root of the Linux source for more information.
+If the unthinkable happens and your kernel oopses, you may need the
+ksymoops tool to decode it, but in most cases you don't.
+In the 2.6 kernel it is generally preferred to build the kernel with
+CONFIG_KALLSYMS so that it produces readable dumps that can be used as-is
+(this also produces better output than ksymoops).
+If for some reason your kernel is not build with CONFIG_KALLSYMS and
+you have no way to rebuild and reproduce the Oops with that option, then
+you can still decode that Oops with ksymoops.
Module-Init-Tools
-----------------