[deployment-guide/comm-rel: 251/727] Extended the Analyzing the Core Dump section.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:45:38 UTC 2010
commit bd3e80289ed4d219bf54a4628892ef2ba3992bb3
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Aug 3 18:55:29 2010 +0200
Extended the Analyzing the Core Dump section.
I have added the following sections:
* Displaying the Backtrace
* Displaying the Message Buffer
* Displaying Virtual Memory Information
* Displaying Open Files
I have selected these as after consulting the documentation, these four
seem to be the most frequent commands.
en-US/The_kdump_Crash_Recovery_Service.xml | 105 ++++++++++++++++++++++++++++
1 files changed, 105 insertions(+), 0 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 4cd50fd..88747f2 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -477,6 +477,111 @@ crash></screen>
<para>
To exit the interactive prompt and terminate <application>Crash</application>, type <command>exit</command>.
</para>
+ <section id="s2-kdump-crash-backtrace">
+ <title>Displaying the Backtrace</title>
+ <para>
+ To display the kernel stack trace, type the <command>bt</command> command at the interactive prompt.
+ </para>
+ <example id="ex-kdump-crash-backtrace">
+ <title>Displaying the kernel stack trace</title>
+ <screen>crash> <command>bt</command>
+PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
+ #0 [eeabfde8] ia32_sysenter_target at c0465b5c
+ #1 [eeabfe3c] oops_end at c077209b
+ #2 [eeabfe50] ia32_sysenter_target at c04206ac
+ EAX: 00000000 EBX: c08833f3 ECX: 00000000 EDX: 00000046
+ DS: fffffed8 ESI: 00000002 ES: fffffe8c EDI: c076ee9d
+ SS: 0001 ESP: c04207f4 EBP: ee939980 GS: 0002
+ CS: ffff8210 EIP: 00000000 ERR: eeabfed8 EFLAGS: eeabfea4</screen>
+ </example>
+ </section>
+ <section id="s2-kdump-crash-log">
+ <title>Displaying the Message Buffer</title>
+ <para>
+ To display the kernel message buffer, type the <command>log</command> command at the interactive prompt.
+ </para>
+ <example id="ex-kdump-crash-log">
+ <title>Displaying the kernel message buffer</title>
+ <screen>crash> <command>log</command>
+<emphasis>... several lines omitted ...</emphasis>
+EIP is at sysrq_handle_crash+0x12/0x1b
+EAX: 00000063 EBX: 00000063 ECX: c0a44e00 EDX: 00000000
+ESI: c0983774 EDI: 00000003 EBP: eeabff14 ESP: eeabff14
+ DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
+Process bash (pid: 5108, ti=eeabe000 task=ee939980 task.ti=eeabe000)
+Stack:
+ eeabff3c c0614c95 c08bf8bd c08c8799 00000000 00000000 00000296 00000002
+<0> 00000000 fffffffb eeabff4c c0614d4b f6cbb580 ee88d700 eeabff70 c04fe318
+<0> eeabff98 00000002 b78d0000 c0614d0a ee88d700 b78d0000 c04fe2bc eeabff8c
+Call Trace:
+ [<c0614c95>] ? __handle_sysrq+0x9c/0x111
+ [<c0614d4b>] ? write_sysrq_trigger+0x41/0x47
+ [<c04fe318>] ? proc_reg_write+0x5c/0x70
+ [<c0614d0a>] ? write_sysrq_trigger+0x0/0x47
+ [<c04fe2bc>] ? proc_reg_write+0x0/0x70
+ [<c04c88d0>] ? vfs_write+0x80/0xdf
+ [<c04c89c3>] ? sys_write+0x3b/0x5d
+ [<c0771034>] ? syscall_call+0x7/0xb
+Code: c0 01 8a 41 03 19 d2 f7 d2 83 e2 03 83 e0 cf c1 e2 04 09 d0 88 41 03 5d c3
+ 55 89 e5 c7 05 b8 49 a4 c0 01 00 00 00 0f ae f8 89 f6 <c6> 05 00 00 00 00 01 5d
+ c3 8d 50 d0 55 83 fa 09 89 e5 76 0d 8d
+EIP: [<c0614951>] sysrq_handle_crash+0x12/0x1b SS:ESP 0068:eeabff14
+CR2: 0000000000000000</screen>
+ </example>
+ </section>
+ <section id="s2-kdump-crash-memory">
+ <title>Displaying Virtual Memory Information</title>
+ <para>
+ To display basic virtual memory information, type the <command>vm</command> command at the interactive prompt.
+ </para>
+ <example id="ex-kdump-crash-memory">
+ <title>Displaying virtual memory information of the current context</title>
+ <screen>crash> <command>vm</command>
+PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
+ MM PGD RSS TOTAL_VM
+eea33540 ee90e000 1716k 5220k
+ VMA START END FLAGS FILE
+eea68210 145000 146000 4040075
+ee9f5d10 6b7000 6c3000 8000075 /lib/libnss_files-2.12.so
+ee9f5e18 6c3000 6c4000 8100071 /lib/libnss_files-2.12.so
+ee9f5e18 6c4000 6c5000 8100073 /lib/libnss_files-2.12.so
+eea68160 80e000 82c000 8000875 /lib/ld-2.12.so
+eea684d0 82c000 82d000 8100871 /lib/ld-2.12.so
+ee9f5f20 82d000 82e000 8100873 /lib/ld-2.12.so
+eea68108 d18000 e9d000 8000075 /lib/libc-2.12.so
+eea68c60 e9d000 e9e000 8000070 /lib/libc-2.12.so
+eea68318 e9e000 ea0000 8100071 /lib/libc-2.12.so
+eea68528 ea0000 ea1000 8100073 /lib/libc-2.12.so
+eea68738 ea1000 ea4000 100073
+eea681b8 f0a000 f0d000 8000075 /lib/libdl-2.12.so
+eea68790 f0d000 f0e000 8100071 /lib/libdl-2.12.so
+ee9f5d68 f0e000 f0f000 8100073 /lib/libdl-2.12.so
+eea68688 f7f000 f9d000 8000075 /lib/libtinfo.so.5.7
+eea68478 f9d000 fa0000 8100073 /lib/libtinfo.so.5.7
+eea68370 8048000 8118000 8001875 /bin/bash
+eea686e0 8118000 811d000 8101873 /bin/bash
+eea68420 811d000 8122000 100073
+<emphasis>... several lines omitted ...</emphasis></screen>
+ </example>
+ </section>
+ <section id="s2-kdump-crash-files">
+ <title>Displaying Open Files</title>
+ <para>
+ To display information about open files, type the <command>files</command> command at the interactive prompt.
+ </para>
+ <example id="ex-kdump-crash-files">
+ <title>Displaying information about open files of the current context</title>
+ <screen>crash> <command>files</command>
+PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
+ROOT: / CWD: /root
+ FD FILE DENTRY INODE TYPE PATH
+ 0 ee8ae580 ed147110 f4396708 CHR /dev/pts/1
+ 1 ee88d700 ed166dd0 ed185798 REG /proc/sysrq-trigger
+ 2 ee8ae580 ed147110 f4396708 CHR /dev/pts/1
+ 10 ee8ae580 ed147110 f4396708 CHR /dev/pts/1
+255 ee8ae580 ed147110 f4396708 CHR /dev/pts/1</screen>
+ </example>
+ </section>
</section>
<section id="s1-kdump-resources">
<title>Additional Resources</title>
More information about the docs-commits
mailing list