Re: Oopses not using to translate

Bryn Paul Arnold Jones (
Fri, 15 Nov 1996 14:56:22 +0000 (GMT)

On Fri, 15 Nov 1996, Joseph Wade Breu wrote:

> Hi all!
> How do I get my kernel to use the file for the kernel
> translations? The oops that I reported earlier did not use the file and
> therefore I could not translate the buggy command.
> Thanks!

Ok, there are three ways to translate them:

1. By hand: look up the EIP, and call trace in the and put
them in the mail after the oops.

2. With ksymoops: it's a c++ program, it's source is in (the linux source
tree in) linux/scripts, read the first few lines to see how to build
it. To use it get the oops, and strip off the syslog stuff (if it's
got it on), and then do:

ksymoops / <oops.txt >decoded.txt

post the oops, and ksymoops output.

3. Automagically: Well klogd will do it for you if it's a farly resent
version, it has to be able to find the when it starts (you
can tell it to reload them, see klogd(8) ;), and it looks in
/boot/, /, and /usr/src/linux/ If it
can't find the, make a symbolic link to it in "/" (ie as
root 'cd /; ln -s <path to>/').

You can usally find the oops in /var/log/messages (that's where syslog
should log it, decoded or otherwise ;)


PGP key pass phrase forgotten,   \ Overload -- core meltdown sequence 
again :( and I don't care ;)      |            initiated.
                                 / This space is intentionally left   
                                |  blank, apart from this text ;-)