From 8692c2f326486b8e4108e5abcc3615ca3ccdfb83 Mon Sep 17 00:00:00 2001 From: Akinobu Mita Date: Wed, 11 Jan 2006 12:17:31 -0800 Subject: [PATCH] --- yaml --- r: 17896 b: refs/heads/master c: 75ba0861bcc64634166124f164dcc05b6393c0ee h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/oops-tracing.txt | 8 +++----- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/[refs] b/[refs] index f3d4cc42e95a..2ea67c5f66b1 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 8428cfe893c1f13eb22cd879669f12b65900738f +refs/heads/master: 75ba0861bcc64634166124f164dcc05b6393c0ee diff --git a/trunk/Documentation/oops-tracing.txt b/trunk/Documentation/oops-tracing.txt index 05960f8a748e..2503404ae5c2 100644 --- a/trunk/Documentation/oops-tracing.txt +++ b/trunk/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