From: David Weinehall <tao@acc.umu.se>
To: Lee Leahu <lee@ricis.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic: VFS: LRU block list corrupted
Date: Sat, 16 Dec 2000 12:08:42 +0100 [thread overview]
Message-ID: <20001216120842.A1851@khan.acc.umu.se> (raw)
In-Reply-To: <5.0.0.25.2.20001215205029.00a8a688@mail.ricis.com>
In-Reply-To: <5.0.0.25.2.20001215205029.00a8a688@mail.ricis.com>; from lee@ricis.com on Fri, Dec 15, 2000 at 09:04:31PM -0600
On Fri, Dec 15, 2000 at 09:04:31PM -0600, Lee Leahu wrote:
> Hello all,
>
> One of my linux servers crash with a 'kernal panic: VFS: LRU block list
> corrupted' message on my screen.
> I reboot with a boot disk - it was find, then rebooted of the hard drive
> and it was fine. The systems is runing fine
> now, but i thought maybe someone on this list could explain to me what
> exactly happend there.
Uhm. First of all, you really need to supply information on what
kernel-version this is. Any hardware information is useful too. And
the oops seem to come from klogd, right? klogd has a horrific tendency
of destroying all information in the oops, thus it's recommended to
call klogd with the '-x' argument to tell it not to decode oops:es.
Then, when you get an oops, run it through ksymoops.
Regards: David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
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/
next prev parent reply other threads:[~2000-12-16 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 3:04 Lee Leahu
2000-12-16 11:08 ` David Weinehall [this message]
2000-12-16 11:32 ` Lee Leahu
2000-12-16 11:43 ` Keith Owens
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=20001216120842.A1851@khan.acc.umu.se \
--to=tao@acc.umu.se \
--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
all inboxes | Powered by JetHome®