Sungju's Slow Life

Personal journal

Jump into a vmcore analysis – Step 2

As I had mentioned in the previous article, you can launch crash analysis by running the below command

$ crash vmcore vmlinux

The order of the file doesn’t matter as far as the file exist there. But, there’s a time that crash command fails as a vmcore is highly incomplete. In that case, you can try below command which at least provide ‘log’ of the system.

$ crash vmcore vmlinux --minimal

Now you are ready to start vmcore analysis. Here are some tips commonly used to check basic information.

Checking the kernel command line

crash> p saved_command_line
saved_command_line = $1 = 0xffffffff804659a0 "ro root=LABEL=/1 console=tty0"

Checking the kernel version and build information

crash> p linux_banner
linux_banner = $3 = 0xc0624000 "Linux version 2.6.18-238.9.1.el5PAE ( (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Fri Mar 18 12:50:00 EDT 2011n"
crash> p linux_banner
linux_banner = $2 = "Linux version 2.6.18-308.13.1.el5 ( (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Aug 21 17:10:18 EDT 2012n 00 00 00 00 00 00 00 00"

Some sysctl parameters

crash> p sysctl_panic_on_oom

crash> p panic_on_oops

crash> p sysctl_hung_task_panic

crash> p sysctl_hung_task_check_count

crash> p sysctl_hung_task_timeout_secs

crash> p watchdog_enabled

crash> p softlockup_thresh

crash> p softlockup_panic

crash> p unknown_nmi_panic

crash> p panic_on_unrecovered_nmi

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: