From: Keith Owens <kaos@ocs.com.au>
To: Lee Leahu <lee@ricis.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic: VFS: LRU block list corrupted
Date: Sat, 16 Dec 2000 22:43:22 +1100 [thread overview]
Message-ID: <15486.976967002@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 16 Dec 2000 05:32:51 MDT." <5.0.0.25.2.20001216051043.00a6b008@mail.ricis.com>
On Sat, 16 Dec 2000 05:32:51 -0600,
Lee Leahu <lee@ricis.com> wrote:
>i'm not very familiar with klog, but i'll go with klogd.
>do i append a '-x' to the line that calls klogs in the startup scripts or
>is there some other better way of preventing klogd from destroying
>the Oops information.
Edit the script that starts klogd, probably /etc/rc.d/init.d/syslog.
Find the line that starts klogd, add '-x' to the options then restart
klogd (probably /etc/rc.d/init.d/syslog restart).
>Then i guess ksymoops. decodes the oops info
Absolutely. See linux/Documentation/oops-tracing.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-16 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 3:04 Kernel panic: VFS: LRU block list corrupted Lee Leahu
2000-12-16 11:08 ` David Weinehall
2000-12-16 11:32 ` Lee Leahu
2000-12-16 11:43 ` Keith Owens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15486.976967002@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=lee@ricis.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox