Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

RedHat 5.0 32 bits kernel panic - [sisips]

Created: 14 Feb 2013 • Updated: 16 Feb 2013 | 2 comments
JackyChen's picture

I Have four Redhat Linux 5.0 32 Bit is VMware Virtual Machine and  installed  SCSP Agent 5.2.9 MP1.

The Virtual Macine  hvae some error messages and hold the start boot machine.

I have some picture and some messages.

 Error Picture :

Error Messages:

在日誌中顯示sisips是3rd party的模組
var/log/messages:Jan 21 13:15:19 ndoc1 kernel: sisips: module license
'Proprietary' taints kernel

在系統的calltrace中,也能發現sisips在其中,因此能夠合理推測與系統panic有關
var/log/messages:Jan 23 16:24:08 ndoc1 kernel: [<f8be4877>]
_ZN20ProcessHashInterface10keyCompareEP11_LIST_ENTRYPv+0x37/0x90 [sisips]
var/log/messages:Jan 23 16:24:08 ndoc1 kernel: [<f8be7bd1>]
_ZN8HashList4findEPv+0x71/0x80 [sisips]
var/log/messages:Jan 23 16:24:08 ndoc1 kernel: [<f8be5146>]
_ZN7Process4findEi+0x16/0x20 [sisips]
var/log/messages:Jan 23 16:24:08 ndoc1 kernel: [<f8bd2fe1>]
hook_stat64+0xc1/0x1d0 [sisips]
var/log/messages:Jan 23 16:24:09 ndoc1 kernel: [<f8be7bd1>]
_ZN8HashList4findEPv+0x71/0x80 [sisips]
var/log/messages:Jan 23 16:24:10 ndoc1 kernel: [<f8be5241>]
_ZN7Process24checkNetworkAcceptAccessEP4PSETiRK11IPV6AddresstS4_tR15NetworkResponse+0x91/0xd0
[sisips]
var/log/messages:Jan 23 16:24:10 ndoc1 kernel: [<f8be5146>]
_ZN7Process4findEi+0x16/0x20 [sisips]
var/log/messages:Jan 23 16:24:10 ndoc1 kernel: [<f8bd2fe1>]
hook_stat64+0xc1/0x1d0 [sisips]
var/log/messages:Jan 23 16:24:11 ndoc1 kernel: [<f8bd4d35>]
hook_open+0xf5/0x200 [sisips]
var/log/messages:Jan 23 16:24:11 ndoc1 kernel: [<f8bca68d>]
hook_accept+0x1d/0xa0 [sisips]
var/log/messages:Jan 23 16:24:11 ndoc1 kernel: [<f8bca68d>]
hook_accept+0x1d/0xa0 [sisips]
var/log/messages:Jan 23 16:24:16 ndoc1 kernel: [<f8be5779>]
_ZN7Process15releaseInternalEv+0x29/0x50 [sisips]
var/log/messages:Jan 23 16:24:18 ndoc1 kernel: [<f8bd5831>]
_ZN7AppFire10getProcessEi+0x11/0x50 [sisips]
var/log/messages:Jan 23 16:24:18 ndoc1 kernel: [<f8be4a2a>]
_ZN7Process17acquireAssignLockEv+0xa/0x10 [sisips]
var/log/messages:Jan 23 16:24:18 ndoc1 kernel: [<f8bd035c>]
_Z10GetProcessi+0x1bc/0x270 [sisips]
var/log/messages:Jan 23 16:24:18 ndoc1 kernel: [<f8be5779>]
_ZN7Process15releaseInternalEv+0x29/0x50 [sisips]
var/log/messages:Jan 23 16:24:18 ndoc1 kernel: [<f8bd3587>]
hook_rename+0x107/0x2a0 [sisips]
var/log/messages:Jan 23 16:24:19 ndoc1 kernel: [<f8be5779>]
_ZN7Process15releaseInternalEv+0x29/0x50 [sisips]
var/log/messages:Jan 23 16:24:19 ndoc1 kernel: [<f8bcaaca>]
hook_dgram_recvmsg+0xba/0xe0 [sisips]
var/log/messages:Jan 23 16:24:20 ndoc1 kernel: [<f8be5241>]
_ZN7Process24checkNetworkAcceptAccessEP4PSETiRK11IPV6AddresstS4_tR15NetworkResponse+0x91/0xd0
[sisips]
var/log/messages:Jan 23 16:24:20 ndoc1 kernel: [<f8bd5831>]
_ZN7AppFire10getProcessEi+0x11/0x50 [sisips]
var/log/messages:Jan 23 16:24:20 ndoc1 kernel: [<f8be4a2a>]
_ZN7Process17acquireAssignLockEv+0xa/0x10 [sisips]
ges:

 

 

 

Comments 2 CommentsJump to latest comment

Will V's picture

Can you please provide additional information?

I'm unclear what your question is.

 

Please mark posts as the solution if they solve your problem!

JackyChen's picture

Error Messages  is RedHat Solution Architect provide information .

Redhat Solution Architect  :

Current image can only show
panic happened when running 3rd software "Symantec Critical System
Protection", Customer can stop
"Symantec Critical System Protection" and remove module sisips and try
again
.
 

I have one virtual machine error log .