X-Git-Url: http://pilppa.org/gitweb/?a=blobdiff_plain;f=Documentation%2Foops-tracing.txt;h=2503404ae5c26bce481d56daecb008588e86102e;hb=6b4b78fed47e7380dfe9280b154e8b9bfcd4c86c;hp=05960f8a748e6169822b1954530150502135cde0;hpb=7ae8c5ec122e4e909193dbbdb2ad2de349e307c9;p=linux-2.6-omap-h63xx.git

diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt
index 05960f8a748..2503404ae5c 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