Hi Krystian,

I'm back from vacation - here's the long-run result for the three test
hosts, which ran unattended for the entire period:

```
root@srv05:~# uptime; uname -r
 10:05:28 up 14 days, 17:45, 1 user, load average: 3.98, 4.44, 4.78
7.0.0-29-generic

root@srv07:~# uptime; uname -r
 10:05:28 up 12 days, 23:20, 2 users, load average: 6.85, 6.84, 7.00
6.15.11-061511-generic

root@srv06:~# uptime; uname -r
 10:05:28 up 12 days, 22:30, 1 user, load average: 8.72, 8.25, 7.94
6.16.0-061600-generic
```

All three hosts (srv05 on HWE 7.0.0-29, srv06 on mainline 6.16.0, and
srv07 on mainline 6.15.11) have now been running for 13-15 days straight
with their full production VM load (20/16/13 guest VMs respectively, all
still running) and zero kernel panics.

Given that srv07 on 6.15.11 - which I believe predates commit 9709eb0f845b (no 
`Cc: [email protected]` tag, merged after the 6.15 release) - has now 
survived 13 days without a single panic, I don't think we can attribute the fix 
to that commit alone. The original panics occurred non-deterministically within 
a 1-24 hour window across all 5 affected hosts on 6.8.0-137, so 13 days of 
stability on a kernel that (as far as I can tell) doesn't have the fix suggests 
either:
- the bug is far more stochastic/load-dependent than we initially thought, or
- something else changed between 6.8.0-137 and 6.15.11 that resolved it, 
unrelated to the commit you flagged

As you suggested, I think the next useful step would be to bisect-test a
few kernels in the 6.8-6.15 range to narrow down where the actual
behavior changed. Let me know which specific versions/commits you'd like
me to prioritize, and I'll set up the tests on the remaining affected
hosts (srv04, srv08 are still available for testing).

-- 
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