From: Akinobu Mita Date: Wed, 11 Jan 2006 20:17:31 +0000 (-0800) Subject: [PATCH] doc: refer to kdump in oops-tracing.txt X-Git-Tag: v2.6.16-rc1~410 X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=75ba0861bcc64634166124f164dcc05b6393c0ee;p=linux-2.6 [PATCH] doc: refer to kdump in oops-tracing.txt 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 Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt index 05960f8a74..2503404ae5 100644 --- a/Documentation/oops-tracing.txt +++ b/Documentation/oops-tracing.txt @@ -41,11 +41,9 @@ the disk is not available then you have three options :- 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