I tried OpenJDK 1.7 and Oracle JDK with same results. Changing the JVM allocated memory helped a bit by reducing the blocked phase duration. BTW, on Fedora, some users experience the same issue : http://forums.fedoraforum.org/showthrea … 246&page=2
]]>65.84% [kernel] [k] _raw_spin_lock_irqsave
strace:
[pid 24947] futex(0x7f52702edd28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 24947] futex(0x7f52702edd54, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1357409542, 1448000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 24947] futex(0x7f52702edd28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 24947] futex(0x7f52702edd54, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1357409542, 11552000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 24947] futex(0x7f52702edd28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 24947] futex(0x7f52702edd54, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1357409542, 21683000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 24947] futex(0x7f52702edd28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 24947] futex(0x7f52702edd54, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1357409542, 31788000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 24947] futex(0x7f52702edd28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 24947] futex(0x7f52702edd54, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1357409542, 41914000}, ffffffff <unfinished ...>
[pid 24938] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 24938] futex(0x7f5270102428, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 24938] futex(0x7f5270102454, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1357409542, 89241000}, ffffffff <unfinished ...>
[pid 24947] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
This happens sporadically but far too often to ignore. When running java (1.7.0_10, x64, standard kernel) I notice full utilization of all cores; and it's kernel time.
The machine quickly freezes so it's kind of hard to investigate...
$ strace -p 15775
Process 15775 attached
futex(0x7f6e7b8ca9d0, FUTEX_WAIT, 15776, NULL) =
Somebody else having this issue?
thx
tcn