Skip to content

Commit

Permalink
[PATCH] doc: refer to kdump in oops-tracing.txt
Browse files Browse the repository at this point in the history
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>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  • Loading branch information
Akinobu Mita authored and Linus Torvalds committed Jan 12, 2006
1 parent 8428cfe commit 75ba086
Showing 1 changed file with 3 additions and 5 deletions.
8 changes: 3 additions & 5 deletions Documentation/oops-tracing.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 75ba086

Please sign in to comment.