lkml.org 
[lkml]   [2006]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
Subject[PATCH 2/2] doc: refer to kdump in oops-tracing.txt
From
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
\
 
 \ /
  Last update: 2006-01-06 03:36    [W:0.030 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site