From: "Stephane Charette" <scharette@packeteer.com>
To: "LKML" <linux-kernel@vger.kernel.org>
Subject: kernel panic not causing a reboot!?
Date: Wed, 06 Nov 2002 12:35:04 -0800 [thread overview]
Message-ID: <20021106202826Z265960-32597+17098@vger.kernel.org> (raw)
MY QUESTIONS ARE:
1) Why did these boxes not reboot after the kernel panic?
2) Are there 2 kinds of kernel panic? A "mini-panic-don't-reboot" as
well as a full-out kernel panic?
3) Is the "file-max limit 4096 reached" error indicative of the reason
why the kernel for some reason couldn't reboot?
----------------------------------
DETAILS & EXPLANATION:
I have a number of 2.2.14 boxes running some custom software. The
loadlin bootup parameters include:
[...] panic=1
And to be extra certain, rc.local calls 'echo "1"
>/proc/sys/kernel/panic'. I can confirm the value of "panic":
[root@localhost /root]# cat /proc/sys/kernel/panic
1
So all seems fine ***EXCEPT*** that recently I've observed the
following situation twice on these boxes:
[root@localhost /root]# Kernel panic: Free list corrupted
VFS: file-max limit 4096 reached
This box had been sitting mostly idle for a few days before I got
around to checking the console. Doing a usenet search on "Kernel
panic: Free list corrupted" returns much information, but not much that
seems to be helpful.
The first question is why did these boxes not reboot after the kernel
panic?
Strangely enough, I found that even after this kernel panic I still had
access to the console. However, I couldn't run anything, as evidenced
by this cut-and-paste:
[root@localhost /root]# cat /proc/sys/kernel/panic
bash: fork: Resource temporarily unavailable
[root@localhost /root]# ls -la
bash: fork: Resource temporarily unavailable
Are there 2 kinds of kernel panic? A "mini-panic-don't-reboot" as well
as a full-out kernel panic? Or is the "file-max limit 4096 reached"
error indicative of the reason why the kernel for some reason couldn't
reboot?
A few technical details:
- vanilla 2.2.14 kernel
- FAT fs on 1st hard disk (mounted periodically to backup some files)
- ext2 on 2nd hard disk (Linux on this drive)
- 512 MB ram
- PCnet/FAST III (pcnet32.c) ethernet
Thanks in advance for any assistance provided,
Stéphane Charette
reply other threads:[~2002-11-06 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021106202826Z265960-32597+17098@vger.kernel.org \
--to=scharette@packeteer.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®