summaryrefslogtreecommitdiff
path: root/Documentation/oops-tracing.txt
diff options
context:
space:
mode:
authorAkinobu Mita <mita@miraclelinux.com>2006-01-11 23:17:31 +0300
committerLinus Torvalds <torvalds@g5.osdl.org>2006-01-12 05:42:10 +0300
commit75ba0861bcc64634166124f164dcc05b6393c0ee (patch)
tree1104e77b8de54f5dbf875291b154c0845e80a17e /Documentation/oops-tracing.txt
parent8428cfe893c1f13eb22cd879669f12b65900738f (diff)
downloadlinux-75ba0861bcc64634166124f164dcc05b6393c0ee.tar.xz
[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 <mita@miraclelinux.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/oops-tracing.txt')
-rw-r--r--Documentation/oops-tracing.txt8
1 files changed, 3 insertions, 5 deletions
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt
index 05960f8a748e..2503404ae5c2 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