Kernel panic with Hard LOCKUP on __write_lock_failed when using CA ControlMinder software

Solution Verified - Updated -

Issue

  • The server is unexpectedly rebooted with a kernel panic due to a process reporting a Hard LOCKUP
       PANIC: "Kernel panic - not syncing: Hard LOCKUP"
  • The offending process can be any running process
  • The panic trace shows __write_lock_failed as the exception RIP:
crash> bt
PID: 8338   TASK: ffff88205fae2ab0  CPU: 19  COMMAND: "multipathd"
[...]
    [exception RIP: __write_lock_failed+9]
[...]
  • This trace is similar to a previously reported BZ 1229196 on older kernel versions, however the suggested errata RHSA-2016-0855 was already applied
  • Issue is not reproduced when the [seos] module is not loaded

Environment

  • Red Hat Enterprise Linux 6
  • CA ControlMinder software, also known as eTrust, and represented by a external module called [seos]

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.