From: "John Chris Wren" <jcwren@jcwren.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Problems with ac12 kernels and up
Date: Sun, 27 May 2001 14:24:03 -0400 [thread overview]
Message-ID: <NDBBKBJHGFJMEMHPOPEGOEEGCHAA.jcwren@jcwren.com> (raw)
In-Reply-To: <E1544Cy-00027I-00@the-village.bc.nu>
>
>> Checking root filesystem. /dev/hde13 is mounted.
>> Cannot continue, aboorting.
>> *** An error occurred during the file system check.
>> *** Dropping you to a shell; the system will reboot
>> *** when you leave the shell.
>
>That means the file system was mounted read/write at boot time. That
normally
>indicates a lilo misconfiguration however your lilo.conf looks
>correct.
>
>Alan
I've built the ac18 kernel with the serial console enabled, and dumped the
results (this is the one that kernel panics).
http://jcwren.com/linux/ac18.txt - ac18 dmesg dump
http://jcwren.com/linux/build.txt - sequence I'm using to build
The apparent interleaved garbage closer to the bottom is exactly what came
out on the console. (Is linking to the dumps perferred over including it in
the mail, or would folks prefer to have the text included? Since I'm not a
judge of exactly what you need to see, I'm not sure if 200 lines of dump
would be appropriate or not).
Just for good measure, I've installed the latest RH 7.1 LILO, mkinitrd, and
associated tools.
I also rebuilt the ac12 kernel, and tried again. Same results as the quoted
text above.
--John
next prev parent reply other threads:[~2001-05-27 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 14:44 John Chris Wren
2001-05-27 17:20 ` Alan Cox
2001-05-27 18:24 ` John Chris Wren [this message]
2001-05-27 18:32 ` Alan Cox
2001-05-27 21:51 ` Jeff Garzik
2001-05-27 21:54 ` Alan Cox
2001-05-28 1:52 ` John Chris Wren
2001-05-27 18:59 problems " John Chris Wren
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=NDBBKBJHGFJMEMHPOPEGOEEGCHAA.jcwren@jcwren.com \
--to=jcwren@jcwren.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®