From: Brian Hall <brianw.hall@compaq.com>
To: willy@meta-x.org, x-linux-kernel@vger.rutgers.edu
Subject: kmsgdump-0.3.1 and kernel 2.2.12
Date: Wed, 01 Sep 1999 10:39:12 -0600 (MDT) [thread overview]
Message-ID: <XFMail.990901103912.brianw.hall@compaq.com> (raw)
I am currently working on a crash dump processing tool, so I have been very
interested in your kmsgdump patch. I have applied it against the 2.2.12 kernel,
and it works fine if invoked manually. Since my main interest was the automatic
mode, I tried that. Basically the automatic mode doesn't work for me. System is
RedHat 6/Intel.
I have created two kernel modules, one to cause a recoverable oops, and one to
force a panic. Invoking those two in sequence causes the automatic dump
sequence to trigger, but only garbage is written(?) to the floppy (drive light
never comes on like it does when I invoke the dump manually). I am using the FAT
format and automatic reboot options. Also, I get an error written to the console
exactly when I think it should start writing to the floppy:
Unable to handle kernel paging request at virtual address 3cc01987
of course the address varies. Doesn't seem to cause an oops (only oopses in
the log are from insmod'ding my modules). I'm not sure if this is a problem with
kmsgdump or the way I am trying to trigger it. Do you have a good method of
triggering automatic operation?
I set the delay to 30 seconds, and did my method for trigging the autodump.
Before the timer reached 30 seconds, I did a manual dump. This did not give the
error message, and appeared to work (drive light came on), but there was only
garbage in the messages.txt file.
One other comment I have is about the floppy format. Years ago when I used
OS/2, there was a floppy formatting program that formatted the floppy with a
standard FAT filesystem, but modified the boot block in such a way that if the
system tried to boot from the floppy, control would be transferred to the hard
drive. This worked very well for accidentally leaving a floppy in the drive on
a reboot. I would suggest doing this to the kmsgdump floppies, so that the disk
can be left in the drive all the time, and any data written to it could be
processed automatically, i.e. by the tool I'm working on ;-) .
--
Brian Hall <brianw.hall@compaq.com>
Linux Consultant
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~1999-09-01 17:15 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=XFMail.990901103912.brianw.hall@compaq.com \
--to=brianw.hall@compaq.com \
--cc=willy@meta-x.org \
--cc=x-linux-kernel@vger.rutgers.edu \
/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®