Commit 987bf6fe3b1409b1cdf4352b3c421260c95d52f2

Authored by Zhang Yanfei
Committed by Linus Torvalds
1 parent a11edb59a0

Documentation/kdump/kdump.txt: remove /dev/oldmem description

Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Dave Hansen <dave@sr71.net>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Matt Fleming <matt.fleming@intel.com>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Tony Luck <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 1 changed file with 6 additions and 25 deletions Side-by-side Diff

Documentation/kdump/kdump.txt
... ... @@ -47,21 +47,14 @@
47 47 when using the elfcorehdr=[size[KMG]@]offset[KMG] syntax.
48 48  
49 49  
50   -With the dump-capture kernel, you can access the memory image, or "old
51   -memory," in two ways:
  50 +With the dump-capture kernel, you can access the memory image through
  51 +/proc/vmcore. This exports the dump as an ELF-format file that you can
  52 +write out using file copy commands such as cp or scp. Further, you can
  53 +use analysis tools such as the GNU Debugger (GDB) and the Crash tool to
  54 +debug the dump file. This method ensures that the dump pages are correctly
  55 +ordered.
52 56  
53   -- Through a /dev/oldmem device interface. A capture utility can read the
54   - device file and write out the memory in raw format. This is a raw dump
55   - of memory. Analysis and capture tools must be intelligent enough to
56   - determine where to look for the right information.
57 57  
58   -- Through /proc/vmcore. This exports the dump as an ELF-format file that
59   - you can write out using file copy commands such as cp or scp. Further,
60   - you can use analysis tools such as the GNU Debugger (GDB) and the Crash
61   - tool to debug the dump file. This method ensures that the dump pages are
62   - correctly ordered.
63   -
64   -
65 58 Setup and Installation
66 59 ======================
67 60  
... ... @@ -422,18 +415,6 @@
422 415 the following command:
423 416  
424 417 cp /proc/vmcore <dump-file>
425   -
426   -You can also access dumped memory as a /dev/oldmem device for a linear
427   -and raw view. To create the device, use the following command:
428   -
429   - mknod /dev/oldmem c 1 12
430   -
431   -Use the dd command with suitable options for count, bs, and skip to
432   -access specific portions of the dump.
433   -
434   -To see the entire memory, use the following command:
435   -
436   - dd if=/dev/oldmem of=oldmem.001
437 418  
438 419  
439 420 Analysis