ksymoops.8

kdb-v4.3-2.4.20-common-1.bz2 键盘的驱动啊 克里斯蒂警方可死了地方军

.TH KSYMOOPS 8 "August 20, 2004"
.hy 0
.UC 4
.SH NAME
ksymoops \- a utility to decode Linux kernel Oops
.SH SYNOPSIS
.B ksymoops
.br
[\ \fB-v\ \fIvmlinux\fR\ ]
[\ \fB--vmlinux=\fIvmlinux\fR\ ]
[\ \fB-V\fR\ ]
[\ \fB--no-vmlinux\fR\ ]
.br
[\ \fB-k\ \fIksyms\fR\ ]
[\ \fB--ksyms=\fIksyms\fR\ ]
[\ \fB-K\fR\ ]
[\ \fB--no-ksyms\fR\ ]
.br
[\ \fB-l\ \fIlsmod\fR\ ]
[\ \fB--lsmod=\fIlsmod\fR\ ]
[\ \fB-L\fR\ ]
[\ \fB--no-lsmod\fR\ ]
.br
[\ \fB-o\ \fIobject\fR\ ]
[\ \fB--object=\fIobject\fR\ ]
[\ \fB-O\fR\ ]
[\ \fB--no-object\fR\ ]
.br
[\ \fB-m\ \fIsystem.map\fR\ ]
[\ \fB--system-map=\fIsystem.map\fR\ ]
[\ \fB-M\fR\ ]
[\ \fB--no-system-map\fR\ ]
.br
[\ \fB-s\ \fIsave.map\fR\ ]
[\ \fB--save-map=\fIsave.map\fR\ ]
.br
[\ \fB-S\fR\ ]
[\ \fB--short-lines\fR\ ]
.br
[\ \fB-e\fR\ ]
[\ \fB--endian-swap\fR\ ]
.br
[\ \fB-x\fR\ ]
[\ \fB--hex\fR\ ]
.br
[\ \fB-1\fR\ ]
[\ \fB--one-shot\fR\ ]
.br
[\ \fB-i\fR\ ]
[\ \fB--ignore-insmod-path\fR\ ]
.br
[\ \fB-I\fR\ ]
[\ \fB--ignore-insmod-all\fR\ ]
.br
[\ \fB-T\ \fItruncate\fR\ ]
[\ \fB--truncate=\fItruncate\fR\ ]
.br
[\ \fB-d\fR\ ]
[\ \fB--debug\fR\ ]
.br
[\ \fB-h\fR\ ]
[\ \fB--help\fR\ ]
.br
[\ \fB-t\ \fItarget\fR\ ]
[\ \fB--target=\fItarget\fR\ ]
.br
[\ \fB-a\ \fIarchitecture\fR\ ]
[\ \fB--architecture=\fIarchitecture\fR\ ]
.br
[\ \fB-A\ \fI"address list"\fR\ ]
[\ \fB--addresses=\fI"address list"\fR\ ]
.br
[\ \fIOops.file\ ...\fR\ ]
.SH DESCRIPTION
ksymoops extracts kernel Oops reports from the Oops.file and uses
various sources of symbol information to convert the addresses and code
to meaningful text.  Reporting a kernel Oops is meaningless on its own
because other people do not know what your kernel looks like, you need
to feed the Oops text through ksymoops then send the ksymoops output as
part of your bug report.
.P
The ksymoops executable is meant to be run whenever you have Oops to
report.  The original Oops text can come from anywhere.  Typically it
is in a file created by your syslogd(8).  If syslogd is not available,
the log might be available via dmesg(8).  If you are running a serial
console (see linux/Documentation/serial-console.txt) then you can
capture the Oops text on another machine.  If all else fails, copy the
Oops by hand from the screen, reboot and enter it by hand.
.P
ksymoops can be run by anybody who has read access to the various input
files.  It does not have to be run as root.
.SH OPTIONS
.P
Some of the options have default values that are set in the Makefile.
The text below describes the standard defaults but your distribution
may have been modified to use different defaults.  If in doubt,
\fIksymoops\ -h\fR will list the current defaults.
.P
The first 10 options (\fB-v\fR, \fB-V\fR, \fB-k\fR, \fB-K\fR, \fB-l\fR,
\fB-L\fR, \fB-o\fR, \fB-O\fR, \fB-m\fR, \fB-M\fR or the corresponding
long forms) are 5 pairs.  The lower case options (vklom) take a value
and turn the option on, the upper case options (VKLOM) take no value
and turn the option off.  If you specify both lower and upper case
versions of the same option then the last one is used but you are
warned that it may not be what you intended.
.P
.ne 5
ksymoops will run quite happily with no options.  However there is a
risk that the default values for the symbol sources may not be
suitable.  Therefore if none of
\fB-v\ \fIvmlinux\fR, \fB-V\fR,
\fB-k\ \fIksyms\fR, \fB-K\fR,
\fB-l\ \fIlsmod\fR, \fB-L\fR,
\fB-o\ \fIobject\fR, \fB-O\fR,
\fB-m\ \fIsystem.map\fR or \fB-M\fR
are specified, ksymoops prints a warning message.
.IP "" 4
You did not tell me where to find symbol information.  I will assume
that the log matches the kernel and modules that are running right now
and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops\ -h explains the options.
.P
If any of the
\fB-v\ \fIvmlinux\fR,
\fB-k\ \fIksyms\fR,
\fB-l\ \fIlsmod\fR,
\fB-o\ \fIobject\fR or
\fB-m\ \fIsystem.map\fR
options contain the string *r (*m, *n, *s) then the string is replaced
at run time by the current value of `uname\ -r` (-m, -n, -s).  This is
mainly intended to let ksymoops automatically pick up version dependent
files using its default parameters, however it could be used by bug
reporting scripts to automatically pick up files whose name or
directory depends on the current kernel.
.TP
\fB-v\ \fIvmlinux\fR\ \fB--vmlinux=\fIvmlinux\fR
Name of the vmlinux file that corresponds to the failing kernel.
\fBNote:\fR\ This is the vmlinux file, not zImage, bzImage, vmlinuz
etc.  Typically this would be /usr/src/linux/vmlinux.  If you specify
\fB-v\fR, you should only specify it once.
.TP
\fB-V\fR\ \fB--no-vmlinux\fR
Do not read any vmlinux file.
.P
Default is \fB-V\fR.
.TP
\fB-k\ \fIksyms\fR\ \fB--ksyms=\fIksyms\fR
Where to find the list of kernel symbols at the time of the failure.
Unfortunately the kernel symbol list in /proc/ksyms is volatile, it is
updated as modules are loaded and removed.  Try to copy /proc/ksyms to
a normal file as soon as possible after the Oops and point ksymoops at
that copy using \fB-k\fR.  Modutils has support for automatically
copying ksyms and lsmod data, see insmod(8).  If you had to reboot
after the Oops and you do not have a copy of /proc/ksyms at the time of
the Oops, try to reload the same modules in the same order before
running ksymoops.  If you specify \fB-k\fR, you should only specify it
once.
.TP
\fB-K\fR\ \fB--no-ksyms\fR
Do not read any kernel symbols.
.P
Default is \fB-k\ \fI/proc/ksyms\fR.
.TP
\fB-l\ \fIlsmod\fR\ \fB--lsmod=\fIlsmod\fR
Where to find the list of loaded modules at the time of the failure.
Unfortunately the list in /proc/modules is volatile, it is updated as
modules are loaded and removed.  Try to copy /proc/modules to a normal
file as soon as possible after the Oops and point ksymoops at that copy
using \fB-l\fR.  Modutils has support for automatically copying ksyms
and lsmod data, see insmod(8).  If you had to reboot after the Oops and
you do not have a copy of /proc/modules at the time of the Oops, try to
reload the same modules in the same order before running ksymoops.  If
you specify \fB-l\fR, you should only specify it once.
.TP
\fB-L\fR\ \fB--no-lsmod\fR
Do not read any list of loaded modules.
.P
Default is \fB-l\ \fI/proc/modules\fR.
.TP
\fB-o\ \fIobject\fR\ \fB--object=\fIobject\fR
Where to find the objects for modules used by the failing kernel.  This
can be a directory name or an individual file.  If it is a directory
then ksymoops does a recursive find(1) in that directory for all files
matching '*.o'.  \fB-o\fR can be specified more than once, the list is
cumulative and can contain a mixture of directories and files.

\fBNote:\fR When you specify a directory, ksymoops only uses files that
end in '.o'.  Any modules with non-standard names are ignored unless
you specify those files explicitly.  For example, if vmnet and vmmon
modules do not end in '.o', you need something like this to pick up all
the normal modules plus the non-standard names.

.nf
  \fB-o\ \fI/lib/modules/*r/\fB\ \\\fR
  \fB-o\ \fI/lib/modules/*r/misc/vmnet\fB\ \\\fR
  \fB-o\ \fI/lib/modules/*r/misc/vmmon\fR
.fi

If you are using a version of insmod(8) that stores the module filename
in /proc/ksyms, ksymoops can go directly to that file, it does not need
\fB-o\fR.  The \fB-o\fR option is only used when ksyms contains at
least one module whose filename is not explicitly listed in ksyms.
.TP
\fB-O\fR\ \fB--no-object\fR
Do not scan for any objects.  If /proc/ksyms is supplied and insmod
added the ksymoops assistance symbols (starting with __insmod) then
those symbols are used to access the objects, no directory scanning is
done so neither -o nor -O have any effect.  To completely disable the
use of module objects when ksyms contains __insmod symbols, specify -O
\fBand\fR one of -i or -I.
.P
Default is \fB-o\ \fI/lib/modules/*r/\fR.  For example, if
uname\ -r reports 2.2.7, ksymoops uses
\fB-o\ \fI/lib/modules/2.2.7/\fR, but only if it does not already know
where the objects are.
.TP
\fB-m\ \fIsystem.map\fR\ \fB--system-map=\fIsystem.map\fR
Where to find the System.map corresponding to the failing kernel.
.TP
\fB-M\fR\ \fB--no-system-map\fR
Do not read any System.map.
.P
Default is \fB-m\ \fI/usr/src/linux/System.map\fR.
.TP
\fB-s\ \fIsave.map\fR\ \fB--save-map=\fIsave.map\fR
After ksymoops reads all its sources of symbols, it generates an
internal system map which contains everything from System.map plus a
best attempt to extract all symbols from all the loaded modules.  If
you want to see that consolidated map, specify \fB-s\ \fIsave.map\fR to
write it out to \fIsave.map\fR.  You do not need to save the map for
normal bug reporting.
.P
Default is no saved map.
.TP
\fB-S\fR\ \fB--short-lines\fR
Some of the ksymoops output lines can be quite long, especially in the
code disassembly, but if you have a wide screen the ksymoops output is
easier to read as long lines.  The \fB-S\fR toggle switches between
short and long lines.  Note that lines printed by the kernel and
extracted from the Oops.file are not affected by \fB-S\fR, problem text
is printed as is.
.P
Default is short lines.
.TP
\fB-e\fR\ \fB--endian-swap\fR
ksymoops extracts code bytes from the reports and converts them to
instructions.  All kernels print code bytes in hex but unfortunately
some systems print multiple bytes using the native machine endianess.
This only causes a problem if the code is printed in anything other
than 1 byte chunks.  For example, i386 prints one byte at a time which
is machine portable, alpha prints 4 bytes at a time in native endianess
and the report is not machine portable.

If you are doing cross system Oops diagnosis (say for a new system or
an embedded version of Linux), then the failing system and the
reporting system can have different endianess.  On systems that support
little and big endianess at the same time, ksymoops could be compiled
with one endianess but the kernel dump could be using another.  If your
code disassembly is wrong, specify \fB-e\fR.  The \fB-e\fR toggles
between native and reverse endianess when reading the bytes in each
chunk of code.  In this context, a chunk of code is 4 or 8 hex digits
(2 or 4 bytes of code), \fB-e\fR has no effect on code that is printed
as 2 hex digits (one byte at a time).

.ne 4
\fBNote:\fR Earlier versions of ksymoops used a
\fB-c\ \fIcode_bytes\fR option.  That is now obsolete, use \fB-e\fR
instead, but only when the code disassembly is incorrect.
.P
The default is to read code bytes using the endianess that ksymoops was
compiled with.
.TP
\fB-x\fR\ \fB--hex\fR
Normally, ksymoops prints offsets and lengths in hex.  If you want
offsets and lengths to be printed in decimal, use the \fB-x\fR toggle.
.P
Default is hex.
.TP
\fB-1\fR\ \fB--one-shot\fR