|author||Jesper Juhl <firstname.lastname@example.org>||2005-11-07 01:01:03 -0800|
|committer||Linus Torvalds <email@example.com>||2005-11-07 07:53:54 -0800|
[PATCH] ksymoops related docs update
Update ksymoops related documentation to reflect current 2.6 reality. Signed-off-by: Jesper Juhl <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Diffstat (limited to 'Documentation/Changes')
1 files changed, 8 insertions, 3 deletions
diff --git a/Documentation/Changes b/Documentation/Changes
index 783ddc3ce4e..86b86399d61 100644
@@ -139,9 +139,14 @@ You'll probably want to upgrade.
-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.