"BUG: soft lockup - CPU#0 stuck for Xs!" with "unix_state_double_lock" in backtrace

Solution Verified - Updated -

Issue

  • RHEL 6.7 performs a BUG: soft lockup - CPU#0 stuck for Xs! with the following backtrace:
    [exception RIP: _spin_lock+0x21]
#10 [ffff8808edf27e20] unix_state_double_lock at ffffffff815047a0
#11 [ffff8808edf27e50] unix_dgram_connect at ffffffff815073cd
#12 [ffff8808edf27eb0] sys_connect at ffffffff814572a7
#13 [ffff8808edf27f80] system_call_fastpath at ffffffff8100b0d2
  • System hang after display in system console the following message 'BUG: soft lockup - CPU#0 stuck for Xs!'

Environment

  • Red Hat Enterprise Linux 6.7
  • kernel-2.6.32-573.15.1.el6 or kernel-2.6.32-573.16.1.el6 or kernel-2.6.32-573.17.1.el6 or kernel-2.6.32-573.18.1.el6
  • AF_UNIX sockets

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content