Initially this looked similar to bug 1413540. This bug patched 3.13 with 9242b5b to _mitigate_ the issue, but this patch is already present in 3.16. So perhaps we're hitting another failure mode. It would be good to know if the smp_call_function_* path in the backtrace is actually leading up to an IPI call that gets lost, and thus we spin in csd_lock_wait.
Are you running nested KVM instances? How often does this lockup occur? Can you get crashdumps of this issue? Thanks, --chris j arges -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
