The system locks up with processes contending a spinlock in ExAcquireResourceExclusiveLite() function of [sisips] kernel module
Issue
The system locks up with 100% system CPU usage. The intentional crashdump shows the processes on all CPUs contending the same spinlock in ExAcquireResourceExclusiveLite() function of [sisips] kernel module with the calltrace like this:
PID: 10722 TASK: 100e616a7f0 CPU: 0 COMMAND: "ifxmonitor.ksh"
#2 [100e4bbbcd8] call_function_interrupt at ffffffff80110be1
[exception RIP: __write_lock_failed+0x9]
RIP: ffffffff801f30b1 RSP: 00000100e4bbbd88 RFLAGS: 00000287
RAX: 00000100ee6d7d60 RBX: 00000100ee6d7d60 RCX: 0000000000000003
RDX: 0000000000000001 RSI: 0000000000000001 RDI: 00000100ee6d7d60
RBP: 00000100e4bbbed8 R8: 0000000000000000 R9: 0000002a9557104e
R10: 0000000000000003 R11: 0000000000000246 R12: 00000100e4bbbea8
R13: 00000100e4bbbe18 R14: 0000000000000001 R15: 0000002a9557104e
ORIG_RAX: fffffffffffffffa CS: 0010 SS: 0018
#3 [100e4bbbd88] .text.lock.spinlock at ffffffff80316bcb (via _write_lock)
#4 [100e4bbbd90] ExAcquireResourceExclusiveLite at ffffffffa0136e0c [sisips]
#5 [100e4bbbda0] _Z10GetProcessi at ffffffffa013af9d [sisips]
#6 [100e4bbbe60] hook_open at ffffffffa013bacf [sisips]
#7 [100e4bbbf80] system_call at ffffffff801102de
Environment
Red Hat Enterprise Linux 4
Symantec Critical System Protection agent
[sisips] kernel module, as a part of SCSP
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.