Documentation: ksymoops should no longer be used to decode Oops messages
PATCH 1/1 Documentation: ksymoops should no longer be used to decode Oops messages
Document the fact that ksymoops should no longer be used to decode Oops messages.
---
Documentation/Changes | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-)
Documentation/Changes +3 -4
@@ -31,7 +31,7 @@ Eine deutsche Version dieser Datei finden Sie unter <http://www.stefan-winter.de/Changes-2.4.0.txt>. -Last updated: October 29th, 2002 +Last updated: October 05th, 2005 Chris Ricker ([email protected] or [email protected]).
@@ -139,9 +139,8 @@ 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. +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With +2.6 kernels ksymoops is no longer needed and should not be used. Module-Init-Tools -----------------
Quoted 2 lines · Jesper Juhl
Document the fact that ksymoops should no longer be used to decode Oops messages.
If it's considered harmful, better remove all references to ksymoops. 2.4 users will happily grab their copy of this file from 2.4 tree.
Quoted 8 lines
Ksymoops
--------Documentation/Changes +2
-3-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. +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With +2.6 kernels ksymoops is no longer needed and should not be used.
Quoted 7 lines · Alexey Dobriyan
Quoted 2 lines · Jesper Juhl
Document the fact that ksymoops should no longer be used to decode Oops messages.
If it's considered harmful, better remove all references to ksymoops. 2.4 users will happily grab their copy of this file from 2.4 tree.
I opted to keep the entry but make an explicit note that ksymoops should not be used for 2.6 kernels to make it clear. There are still people who use ksymoops on 2.6 Oops messages, so I thought it would make sense to keep the entry but make it clear that you should /not/ do that.
But, I'm fine with removing it as well.
Quoted 9 lines
Review
Quoted 8 lines
Ksymoops
--------(quoted diff) +2
-3-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. +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With +2.6 kernels ksymoops is no longer needed and should not be used.
Here's a patch to remove the Ksymoops entry instead.
I'll leave it up to the powers that be to sprinkle holy penguin pee on the preferred version.
Ksymoops should not be used on 2.6 Oops messages, so remove the ksymoops entry from Documentation/Changes
---
Documentation/Changes | 9 +-------- 1 files changed, 1 insertion(+), 8 deletions(-)
Documentation/Changes +1 -8
@@ -31,7 +31,7 @@ Eine deutsche Version dieser Datei finden Sie unter <http://www.stefan-winter.de/Changes-2.4.0.txt>. -Last updated: October 29th, 2002 +Last updated: October 05th, 2005 Chris Ricker ([email protected] or [email protected]).
@@ -136,13 +136,6 @@ types, have a fdformat which works with 2.4 kernels, and similar goodies. 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. - Module-Init-Tools -----------------
Quoted 23 lines · Jesper Juhl
Document the fact that ksymoops should no longer be used to decode Oops messages.
Signed-off-by Jesper Juhl <[email protected]>---
Documentation/Changes | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-)Documentation/Changes +1
-1@@ -31,7 +31,7 @@ Eine deutsche Version dieser Datei finden Sie unter <http://www.stefan-winter.de/Changes-2.4.0.txt>. -Last updated: October 29th, 2002 +Last updated: October 05th, 2005 Chris Ricker ([email protected] or [email protected]).@@ -139,9 +139,8 @@ Ksymoops
Documentation/Changes line 146
Quoted 10 lines
Documentation/Changes +2
-3-------- -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. +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With +2.6 kernels ksymoops is no longer needed and should not be used. Module-Init-Tools -----------------
OK, but what should I use then with 2.6??
And since when is ksymoops not usable with it?
I have reported quite a few times here, alaways with 2.6.x and nobody said anything about it...
Kalin.
Signature · 3 lines
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]| +-> http://ThinRope.net/ <-+ |[ ______________________ ]|
Quoted 32 lines · Kalin KOZHUHAROV
Quoted 31 lines · Jesper Juhl
Document the fact that ksymoops should no longer be used to decode Oops messages.
Signed-off-by Jesper Juhl <[email protected]>---
Documentation/Changes | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-)Documentation/Changes +3
-4@@ -31,7 +31,7 @@ Eine deutsche Version dieser Datei finden Sie unter <http://www.stefan-winter.de/Changes-2.4.0.txt>. -Last updated: October 29th, 2002 +Last updated: October 05th, 2005 Chris Ricker ([email protected] or [email protected]).@@ -139,9 +139,8 @@ 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. +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With +2.6 kernels ksymoops is no longer needed and should not be used.
Quoted 6 lines
Documentation/Changes line 146
Quoted 2 lines
Documentation/Changes +0
-0Module-Init-Tools -----------------OK, but what should I use then with 2.6??
And since when is ksymoops not usable with it?
I have reported quite a few times here, alaways with 2.6.x and nobody said anything about it...
You should just enable CONFIG_KALLSYMS so that the kernel can report (decode) the symbols with the oops message.
Yes, ksymoops will still work, but it should only be used if the kernel was not configured with CONFIG_KALLSYMS, and some people say that the kernel oops + symbols are better than the ksymoops output. I haven't compared them so can't say.
Signature · 1 line
~Randy
Quoted 4 lines · Kalin KOZHUHAROV
Quoted 3 lines · Jesper Juhl
Document the fact that ksymoops should no longer be used to decode Oops messages.
[snip]
Quoted 2 lines
OK, but what should I use then with 2.6??
Nothing at all.
Just post the raw Oops message as-is (from console or dmesg).
Quoted 1 line
And since when is ksymoops not usable with it?
At least since 2003 and the 2.5 kernel series.
The oldest reference I could find in the archives is an email by Dave Jones dating back to Mon Apr 14 2003 - 14:31:44 EST
http://www.uwsg.iu.edu/hypermail/linux/kernel/0304.1/1533.html
The interresting part of that mail is this bit
"Merging of kksymoops means that the kernel will now spit out
automatically decoded oopses (no more feeding them to ksymoops). For this reason, you should always enable the option in the kernel hacking menu labelled "Load all symbols for debugging/kksymoops".
"
Quoted 1 line
I have reported quite a few times here, alaways with 2.6.x and nobody said anything about it...
They should have.
Please read a recent Documentation/oops-tracing.txt (here's a link:
http://sosdg.org/~coywolf/lxr/source/Documentation/oops-tracing.txt?v=2.6.14-rc2
)
See the note at the top :
"NOTE: ksymoops is useless on 2.6. Please use the Oops in its original format
(from dmesg, etc). Ignore any references in this or other docs to "decoding the Oops" or "running it through ksymoops". If you post an Oops fron 2.6 that has been run through ksymoops, people will just tell you to repost it.
"
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
Quoted 10 lines · Kalin KOZHUHAROV
Documentation/Changes line 143
Quoted 8 lines
Ksymoops
--------Documentation/Changes +2
-3-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. +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With +2.6 kernels ksymoops is no longer needed and should not be used.OK, but what should I use then with 2.6??
Raw Oops output. From logs, serial console, monitor photoed with digital camera, copied to paper with pencil...