spinlock Errors?

[jmcknight]

I get fairly regular errors output to the console when running Zimbra. I did some research and suspect it is related to spinlock problems.

Any ideas if this is Zimbra related or just my hardware and POSIX threads?

This is an older Dell 6400 PowerEdge with 4 Xeon Processors (733 Mhz), 2 gigs of ram.

FC4 (fully patched)

Zimbra installed perfectly and the server does not go down, it just causes everything to seem locked up for a bit.

messages output:

May 17 22:06:54 mail2 kernel: BUG: write-lock lockup on CPU#1, java/28973, c03f1a80 (Not tainted)
May 17 22:06:54 mail2 kernel: BUG: write-lock lockup on CPU#2, java/28967, c03f1a80 (Not tainted)
May 17 22:06:54 mail2 kernel: BUG: write-lock lockup on CPU#3, java/28969, c03f1a80 (Not tainted)
May 17 22:06:54 mail2 kernel:  [<c01f043b>]  [<c01f043b>] _raw_write_lock+0xf8/0x16d     [<c012764a>] _raw_write_lock+0xf8/0x16d
May 17 22:06:54 mail2 kernel:  [<c01f043b>] _raw_write_lock+0xf8/0x16d     [<c012764a>] do_exit+0x252/0x850

[Coilcore]

I'm running Zimbra on a box with dual Xeon (3.6Ghz, so a bit newer) and its using Redhat Enterprise 4. Never seen this problem.

My guess is that its something about your hardware config, the SMP Kernel, and Java that are not playing nice. The messages seem to imply that there is some kind of cross context deadlock at the kernel level.