From: mita@miraclelinux.com (Akinobu Mita)
To: fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] doc: refer to kdump in oops-tracing.txt
Date: Fri, 6 Jan 2006 11:34:30 +0900 [thread overview]
Message-ID: <20060106023429.GC18912@miraclelinux.com> (raw)
In-Reply-To: <20060106023306.GB18912@miraclelinux.com>
Kdump has been merged and supported on several architectures.
It is better to encourage to use kdump rather than non standard
kernel crash dump patches.
Signed-off-by: Akinobu Mita <mita@miraclelinux.com>
--- 2.6/Documentation/oops-tracing.txt.orig 2006-01-06 10:55:53.000000000 +0900
+++ 2.6/Documentation/oops-tracing.txt 2006-01-06 10:58:30.000000000 +0900
@@ -41,11 +41,9 @@ the disk is not available then you have
run a null modem to a second machine and capture the output there
using your favourite communication program. Minicom works well.
-(3) Patch the kernel with one of the crash dump patches. These save
- data to a floppy disk or video rom or a swap partition. None of
- these are standard kernel patches so you have to find and apply
- them yourself. Search kernel archives for kmsgdump, lkcd and
- oops+smram.
+(3) Use Kdump (see Documentation/kdump/kdump.txt),
+ extract the kernel ring buffer from old memory with using dmesg
+ gdbmacro in Documentation/kdump/gdbmacros.txt.
Full Information
prev parent reply other threads:[~2006-01-06 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 2:33 [PATCH 1/2] kdump: add dmesg gdbmacro into document Akinobu Mita
2006-01-06 2:34 ` Akinobu Mita [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=20060106023429.GC18912@miraclelinux.com \
--to=mita@miraclelinux.com \
--cc=fastboot@lists.osdl.org \
--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