
Troubleshooting 76
Saving Kernel Fault (OOPS)
You can use the following command to check for the kernel messages that should be decoded
and reported to OpenVZ developers:
grep -E "Call Trace|Code" /var/log/messages*
Then you should find these lines in the correspondent log file and figure out what kernel was
booted when the oops occurred. Search backward for the "Linux" string, look for strings like
that:
May 23 16:55:00 ts13 Linux version 2.6.8-022stab026.1 ([email protected]) (gcc
version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Fri Jul 8 17:31:10 MSD 2005
An oops usually starts with some description of what happened and ends with the Code string.
Here is an example:
May 24 15:12:07 ts13 Unable to handle kernel paging request at virtual address d0d48b08
May 24 15:12:07 ts13 printing eip:
May 24 15:12:07 ts13 c01b4049
May 24 15:12:07 ts13 *pde = 00044063
May 24 15:12:07 ts13 *pte = 10d48000
May 24 15:12:07 ts13 Oops: 0000 [#1]
May 24 15:12:07 ts13 SMP DEBUG_PAGEALLOC
May 24 15:12:07 ts13 Modules linked in: e100 mii af_packet ip_nat_ftp ip_nat_irc
ipt_helper ip_conntrack_irc ip_conntrack_ftp ipt_TOS ipt_LOG ipt_conntrack ipt_state
iptable_nat ip_conntrack ipt_length ipt_ttl ipt_tcpmss ipt_TCPMSS iptable_mangle
iptable_filter ipt_multiport ipt_limit ipt_tos ipt_REJECT ip_tables
May 24 15:12:07 ts13 CPU: 0, VCPU: 2147483647:0
May 24 15:12:07 ts13 EIP: 0060:[<c01b4049>] Not tainted
May 24 15:12:07 ts13 EFLAGS: 00010206
May 24 15:12:07 ts13 EIP is at proc_p0x289/0x5b0
May 24 15:12:07 ts13 eax: d0d48a70 ebx: 00000000 ecx: 00000000 edx: c0128962
May 24 15:12:07 ts13 esi: 00000000 edi: c599fa70 ebp: d93f2f34 esp: d93f2e04
May 24 15:12:07 ts13 ds: 007b es: 007b ss: 0068
May 24 15:12:07 ts13 Process top (pid: 19753, threadinfo=d93f2000 task=d93f1a70)
May 24 15:12:07 ts13 Stack: c599fa70 00000000 c041b980 d93f2e50 c018e7bd cc752f58
c041b980 d8b4df58
May 24 15:12:07 ts13 d93f2e4c c01b0cea c599fa70 c627a00c 00000004 df1c3f58
00000000 d8b4df58
May 24 15:12:07 ts13 cc752f58 00000000 c0d97e94 d93f2e6c c018eb9e 04837000
00000000 d93f2e84
May 24 15:12:07 ts13 Call Trace:
May 24 15:12:07 ts13 [<c010650f>] sho0x7f/0xa0
May 24 15:12:07 ts13 [<c01066df>] show_re0x17f/0x220
May 24 15:12:07 ts13 [<c01068c7>] die+0xa7/0x170
May 24 15:12:07 ts13 [<c01188ea>] do_pag0x2fa/0x59e
May 24 15:12:07 ts13 [<c034576f>] err0x2f/0x38
May 24 15:12:07 ts13 [<c01afe71>] proc_in0x51/0x160
May 24 15:12:07 ts13 [<c0171dea>] v0xaa/0x130
May 24 15:12:07 ts13 [<c017208b>] s0x4b/0x80
May 24 15:12:07 ts13 [<c0344cda>] sysenter_p0x43/0x61
May 24 15:12:07 ts13 Code: 8b 80 98 00 00 00 89 45 b0 f0 ff 05 c0 b7 41 c0 8b 87 88 01
All you need is to put the oops into a file.