-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm confused about what the oops file is...is it /proc/ksyms, or what? If I
don't put in a file for it to read from, it wants the information from STDIN,
right?
Thanks!
Russell
On Wednesday 27 February 2002 11:09 am, you wrote:
> On Wed, 2002-02-27 at 08:57, Russell Hires wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hello everyone,
> >
> > I've got a buggy kernel. Or buggy hardware. But, for now, every so often
> > I crash, and I want to capture the info reported by ksymoops. ksymoops
> > uses the defaults to get information, but the thing I don't understand is
> > that after it displays the information, ksymoops tells me that it's
> > reading information from the terminal. Why would it do that? Do I need to
> > give it some information? The man pages don't have anything to say about
> > this, unfortunately...
>
> Yep, you need to give it the OOPS that the kernel spits out when
> something goes pear-shaped. It's usually somewhere in /var/log/messages
> or /var/log/kern.log or /var/log/syslog. It depends on how you have
> your syslog setup.
>
> The stuff in /var/log/ksymoops is "snapshot" information that ksymoops
> might like to know about. For ksymoops to work effectively, it has to
> know exactly which modules are/were loaded at the time of the OOPS, and
> where in memory they were loaded, which is usually problematic because
> generally speaking, if your kernel panics, you have to reboot and now
> your modules may be loaded differently... A Debian box periodically
> "snapshots" this information to logfiles in /var/log/ksymoops so you can
> refer back to that information closest to the time of the oops.
>
> The "Kernel Crash Dump" project tries to deal with the current
> not-very-good post-mortem kernel OOPS/panic situation by including some
> more instrumentation in the kernel for spitting out more useful
> information at the time of the oops rather than trying to deal with
> everything post facto when you have the system actually running again,
> by which time all the useful diagnostic information has been lost. If
> you're having serious problems, you might want to look into the KCD
> patch. I've forgotten where it is but a google search aught to turn it
> up pretty quickly.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8faqfAqKGrvVshJQRAlMhAJ9kLZlvicSpa5T12PLvsPmfPd/w+ACgohbs
beMBpPshR6X7c/uv0VaGgv8=
=8IBJ
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:52:37 EDT