Commit 75ba0861 authored by Akinobu Mita's avatar Akinobu Mita Committed by Linus Torvalds

[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: default avatarAkinobu Mita <mita@miraclelinux.com>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent 8428cfe8
...@@ -41,11 +41,9 @@ the disk is not available then you have three options :- ...@@ -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 run a null modem to a second machine and capture the output there
using your favourite communication program. Minicom works well. using your favourite communication program. Minicom works well.
(3) Patch the kernel with one of the crash dump patches. These save (3) Use Kdump (see Documentation/kdump/kdump.txt),
data to a floppy disk or video rom or a swap partition. None of extract the kernel ring buffer from old memory with using dmesg
these are standard kernel patches so you have to find and apply gdbmacro in Documentation/kdump/gdbmacros.txt.
them yourself. Search kernel archives for kmsgdump, lkcd and
oops+smram.
Full Information Full Information
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment