[deployment-guide/comm-rel: 247/727] Wrote an introduction to the Crash usage.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:45:17 UTC 2010
commit 836301907cf20398c9d1c9b3df59e29ea59969fa
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Aug 3 16:35:46 2010 +0200
Wrote an introduction to the Crash usage.
en-US/The_kdump_Crash_Recovery_Service.xml | 74 +++++++++++++++++++++++++++-
1 files changed, 73 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index c3ce82b..4f90c7a 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -404,6 +404,78 @@ Kdump is operational</screen>
</example>
</section>
</section>
+ <section id="s1-kdump-crash">
+ <title>Analyzing the Core Dump</title>
+ <note>
+ <title>Note: Make Sure You Have Relevant Packages Installed</title>
+ <para>
+ To analyze the <filename>vmcore</filename> dump file, you must have the <package>crash</package> and <package>kernel-debuginfo</package> packages installed. To do so, type the following at a shell prompt:
+ </para>
+ <screen>~]# <command>yum install --enablerepo=rhel-debuginfo \</command>
+<command>--enablerepo=updates-debuginfo crash kernel-debuginfo</command></screen>
+ <para>
+ Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+ </para>
+ </note>
+ <para>
+ To determine the cause of the system crash, you can use the <application>Crash</application> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
+ </para>
+ <para>
+ To start the utility, type the command in the following form at a shell prompt:
+ </para>
+ <screen><command>crash /var/crash/<replaceable>timestamp</replaceable>/vmcore /usr/lib/debug/lib/modules/<replaceable>kernel</replaceable>/vmlinux</command></screen>
+ <para>
+ Note that the <replaceable>kernel</replaceable> version should be the same that was captured by <systemitem class="service">kdump</systemitem>. To find out which kernel you are currently running, use the <command>uname -r</command> command.
+ </para>
+ <example id="ex-kdump-crash-running">
+ <title>Running the <command>crash</command> utility</title>
+ <screen>~]# <command>crash /usr/lib/debug/lib/modules/2.6.32-54.el6.x86_64/vmlinux \</command>
+<command>/var/crash/127.0.0.1-2010-07-28-16:58:36/vmcore</command>
+
+crash 5.0.0-21.el6
+Copyright (C) 2002-2010 Red Hat, Inc.
+Copyright (C) 2004, 2005, 2006 IBM Corporation
+Copyright (C) 1999-2006 Hewlett-Packard Co
+Copyright (C) 2005, 2006 Fujitsu Limited
+Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
+Copyright (C) 2005 NEC Corporation
+Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
+Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
+This program is free software, covered by the GNU General Public License,
+and you are welcome to change it and/or distribute copies of it under
+certain conditions. Enter "help copying" to see the conditions.
+This program has absolutely no warranty. Enter "help warranty" for details.
+
+GNU gdb (GDB) 7.0
+Copyright (C) 2009 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change it and redistribute it.
+There is NO WARRANTY, to the extent permitted by law. Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "x86_64-unknown-linux-gnu"...
+
+ KERNEL: /usr/lib/debug/lib/modules/2.6.32-54.el6.x86_64/vmlinux
+ DUMPFILE: /var/crash/127.0.0.1-2010-07-28-16:58:36/vmcore
+ CPUS: 1
+ DATE: Wed Jul 28 16:58:36 2010
+ UPTIME: 10:29:46
+LOAD AVERAGE: 0.64, 0.27, 0.12
+ TASKS: 226
+ NODENAME: hansen
+ RELEASE: 2.6.32-54.el6.x86_64
+ VERSION: #1 SMP Wed Jul 28 00:06:54 EDT 2010
+ MACHINE: x86_64
+ MEMORY: 4 GB
+ PANIC: "Oops: 0002 [#1] SMP " (check log for details)
+ PID: 5108
+ COMMAND: "bash"
+ TASK: ee939980 [THREAD_INFO: eeabe0000]
+ CPU: 0
+ STATE: TASK_RUNNING (PANIC)
+
+crash></screen>
+ </example>
+ </section>
<section id="s1-kdump-resources">
<title>Additional Resources</title>
<section id="s2-kdump-resources-installed">
@@ -437,7 +509,7 @@ Kdump is operational</screen>
<term><command>man crash</command></term>
<listitem>
<para>
- The manual page for the <command>crash</command> utility containing the full documentation on its usage.
+ The manual page for the <application>Crash</application> utility containing the full documentation on its usage.
</para>
</listitem>
</varlistentry>
More information about the docs-commits
mailing list