Hi Krystian,

Correction to my previous update - I misread the timing on srv06's
crash.

srv06 (mainline v6.14.0, commit 1 only) was actually stable for **~6
days** before the issue appeared, not 39 hours. The "141006s" (~39.2
hours) in the watchdog message is how long that specific CPU had been
stuck *by the time the watchdog detected and reported it* - not the
host's total uptime. So the sequence was: ~6 days stable uptime, then a
soft lockup that had apparently been building for ~39 hours before the
watchdog flagged it, which then escalated into the host becoming fully
unresponsive.

Sorry for the confusion - wanted to get that timeline right since it
changes how this compares to the other hosts (e.g. srv07 with the
identical commit configuration was still stable well past 6 days at that
point).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163642

Title:
  Kernel panic "Attempted to kill the idle task" on AMD Opteron multi-
  node NUMA under KVM (6.8.0-137)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163642/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to