> kysmoops is not made by make zImage, but at least it has a line
> how to compile it as one of the first comment lines.
> (BTW: I compiled it with -lg++ instead of -liostrems and it seemed to work too)
>
> But how to use it?
> It does not react on -h or any other well known switch.
It's all in the first page of comments.
// This is a simple filter to resolve EIP and call-trace symbols from
// a Linux kernel "Oops" log. Supply the symbol-map file name as a
// command-line argument, and redirect the oops-log into stdin. Out
// will come the EIP and call-trace in symbolic form.
So, typical use would be
"ksymoops /boot/System.map <oops-07-01-97 >oops-07-01-97.out"
assuming /boot/System.map is the System.map that was generated with the
kernel that Oops'd. If you use a System.map that doesn't "go with" the
kernel that Oops'd, the results from ksymoops are likely to be confusing
and worthless.
Then email the contents of oops-07-01-97 and oops-07-01-97.out to the
kernel list mentioning the kernel version you used as well as any
patches...and if possible a description of what has happening when the
Oops happened.
> I want to start testing kernel with a little more system than before, and
> I would like to know
> - how to prepare myself
> (logfile setup any special way? Keeping the System map? Where?
> I have three different kernel trees I want to run (2.0.latest, 2.1.latest,
> 2.0.ggi, and of course something meant to be stable :-) and
> currently copy the zImages to /some-name and the System maps to
> /System.map.some-name, but what is it good for?)
> - what to test
> -what to look for
I generally copy kernels to /kernels/vmlinuz-version-description, and do
the same with .config and System.map. So I end up with a large collection
of kernel in /kernels. Then, just add kernels to lilo.conf to upgrade:
# End LILO global section
# Linux bootable partition config begins
#
image = /kernels/vmlinuz-2.0.31-pre1-3
root = /dev/sda1
label = 2.0.31-pre1-3
read-only
image = /kernels/vmlinuz-2.0.30-fdt3
root = /dev/sda1
label = 2.0.30-fdt3
read-only
Then, if I get an Oops, I know which System.map to use, and if I get lots
of Oops's, I can downgrade by just commenting out the top kernel entry in
lilo.conf or typing in the kernel lable at the lilo prompt.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
________Finger jlewis@inorganic5.fdt.net for PGP public key_______