Symptom
After install BusinessObjects XI Enterprise, when starting the CMS, the BOXI environment is unstable.
The BOXI environment restarts several time a day with the following error messages in the Linux system log :
Sep 1 15:57:42 <Server Name> kernel: ------------[ cut here ]------------
Sep 1 15:57:42 <Server Name> kernel: kernel BUG at kernel/exit.c:904!
Sep 1 15:57:42 <Server Name> kernel: invalid operand: 0000 [#1]
Sep 1 15:57:42 <Server Name> kernel: SMP
Sep 1 15:57:42 <Server Name> kernel: Modules linked in: md5 ipv6 parport_pc lp parport autofs4 i2c_dev i2c_core cpufreq_powersave loop joydev button battery ac ehci_hcd uhci_hcd bnx2 sr_mod ata_piix libata dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod cciss(U) sd_mod scsi_mod
Sep 1 15:57:42 <Server Name> kernel: CPU: 2
Sep 1 15:57:42 <Server Name> kernel: EIP: 0060:[<c0124cc5>] Not tainted VLI
Sep 1 15:57:42 <Server Name> kernel: EFLAGS: 00010046 (2.6.9-78.ELsmp)
Sep 1 15:57:42 <Server Name> kernel: EIP is at next_thread+0xc/0x3f
Sep 1 15:57:42 <Server Name> kernel: eax: 00000000 ebx: e474e6f0 ecx: 00000000 edx: d4f9b0b0
Sep 1 15:57:42 <Server Name> kernel: esi: 000000da edi: 0000002d ebp: 41bedc50 esp: e4dc6f8c
Sep 1 15:57:42 <Server Name> kernel: ds: 007b es: 007b ss: 0068
Sep 1 15:57:42 <Server Name> kernel: Process boe_jobsd (pid: 17812, threadinfo=e4dc6000 task=e474e6f0)
Sep 1 15:57:42 <Server Name> kernel: Stack: c012f536 9bbe81c0 000f5479 00000014 00000043 0000001f 00000009 00000006
Sep 1 15:57:42 <Server Name> kernel: 00000001 41bedc50 00000000 0131c386 e4dc6000 c02e09db 41bedc50 00000000
Sep 1 15:57:42 <Server Name> kernel: 081869e4 00000000 0131c386 41bedcd8 0000002b c02e007b 0000007b 0000002b
Sep 1 15:57:42 <Server Name> kernel: Call Trace:
Sep 1 15:57:42 <Server Name> kernel: [<c012f536>] sys_times+0x56/0x1c5
Sep 1 15:57:42 <Server Name> kernel: [<c02e09db>] syscall_call+0x7/0xb
Sep 1 15:57:42 <Server Name> kernel: [<c02e007b>] __lock_text_end+0x880/0x107d
Sep 1 15:57:42 <Server Name> kernel: Code: 85 c0 89 d3 74 05 e8 53 9c ff ff 53 e8 b9 fb ff ff 0f b6 44 24 04 c1 e0 08 50 e8 ab fb ff ff 89 c2 8b 80 f0 04 00 00 85 c0 75 08 <0f> 0b 88 03 ae 25 2f c0 0f b6 80 04 05 00 00 84 c0 7e 14 a1 80
Sep 1 15:57:42 <Server Name> sshd(pam_unix)[17814]: session opened for user gptoadm by (uid=0)
Sep 1 15:57:42 <Server Name> kernel: <0>Fatal exception: panic in 5 seconds
Sep 7 11:39:07 <Server Name> kernel: ------------[ cut here ]------------
Sep 7 11:39:07 <Server Name> kernel: kernel BUG at kernel/exit.c:904!
Sep 7 11:39:07 <Server Name> kernel: invalid operand: 0000 [#1]
Sep 7 11:39:07 <Server Name> kernel: SMP
Sep 7 11:39:07 <Server Name> kernel: Modules linked in: ipmi_devintf ipmi_si ipmi_msghandler md5 ipv6 parport_pc lp parport autofs4 i2c_dev i2c_core cpufreq_powersave loop joydev button battery ac ehci_hcd uhci_hcd bnx2 sr_mod ata_piix libata dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod cciss(U) sd_mod scsi_mod
Sep 7 11:39:07 <Server Name> kernel: CPU: 4
Sep 7 11:39:07 <Server Name> kernel: EIP: 0060:[<c0124cc5>] Not tainted VLI
Sep 7 11:39:07 <Server Name> kernel: EFLAGS: 00210046 (2.6.9-78.ELsmp)
Sep 7 11:39:07 <Server Name> kernel: EIP is at next_thread+0xc/0x3f
Sep 7 11:39:07 <Server Name> kernel: eax: 00000000 ebx: f4e38cf0 ecx: 00000000 edx: f4686730
Sep 7 11:39:07 <Server Name> kernel: esi: 00000367 edi: 0000005a ebp: 42fea000 esp: f4e09f8c
Sep 7 11:39:07 <Server Name> kernel: ds: 007b es: 007b ss: 0068
Sep 7 11:39:07 <Server Name> kernel: Process boe_cmsd (pid: 31209, threadinfo=f4e09000 task=f4e38cf0)
Sep 7 11:39:07 <Server Name> kernel: Stack: c012f536 c0135f4e 7fffffff 08461c2c 00000000 42fe9f28 00000000 00000000
Sep 7 11:39:07 <Server Name> kernel: 00000000 42fea000 08417098 08461c28 f4e09000 c02e09db 42fea000 00000000
Sep 7 11:39:07 <Server Name> kernel: 406cf5ac 08417098 08461c28 42fea038 0000002b c02e007b 0000007b 0000002b
Sep 7 11:39:07 <Server Name> kernel: Call Trace:
Sep 7 11:39:07 <Server Name> kernel: [<c012f536>] sys_times+0x56/0x1c5
Sep 7 11:39:07 <Server Name> kernel: [<c0135f4e>] sys_futex+0x101/0x10c
Sep 7 11:39:07 <Server Name> kernel: [<c02e09db>] syscall_call+0x7/0xb
Sep 7 11:39:07 <Server Name> kernel: [<c02e007b>] __lock_text_end+0x880/0x107d
Sep 7 11:39:07 <Server Name> kernel: Code: 85 c0 89 d3 74 05 e8 53 9c ff ff 53 e8 b9 fb ff ff 0f b6 44 24 04 c1 e0 08 50 e8 ab fb ff ff 89 c2 8b 80 f0 04 00 00 85 c0 75 08 <0f> 0b 88 03 ae 25 2f c0 0f b6 80 04 05 00 00 84 c0 7e 14 a1 80
Sep 7 11:39:07 <Server Name> kernel: <0>Fatal exception: panic in 5 seconds
Read more...
Product
Keywords
Kernel panic , KBA , BI , Business intelligence solutions , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.