I. installation package:
1. Crash (installed through YUM)
2. kernel-debuginfo-2.6.32-358.el6.x86_64.rpm
3. kernel-debuginfo-common-x86_64-2.6.32-358.el6.x86_64.rpm
2. Enable the kdump service:/etc/init. d/kdump start
Note: The kdump service is enabled by default in the rhel6.4 system installed through Kickstart.
Confirm that the kdump service is enabled:/etc/init. d/kdump status. If the output kdump is operational, the kdump service is successfully enabled.
3. view the dump file
After the kernel crash, a dump file is generated in the/var/crash/directory, for example:
/Var/crash/127.0.0.1-2014-05-07-15:24:33/
The vmcore-dmesg.txt and vmcore-dmesg.txt files are generated in the directory:
Vmcore: memory dump during kernel crash
Vmcore-dmesg.txt: saves the dmesg information at this point during kernel crash
View the vmcore command: crash/usr/lib/debug/lib/modules/2.6.32-358. el6.x86 _ 64/vmlinux./vmcore
The output
Rhel6.4-kernel-dump1
Enter BT
Rhel6.4-kernel-dump2
In the figureCommand: "crash_test.sh"Indicates that crash is triggered by the crash_test.sh program.
Appendix:
1. Manually trigger the kernel crash method echo C>/proc/sysrq-trigger
2. Crash>Interactive Common commands:
?View help. There are many commands to view the current process, memory, module, and so on.
Help BTView BT Command help
Rhel6.4 kernel dump and view