I added a background task to dump out new dmesg messages and I now see messages such as the following *before* any stress-ng tests run. I think we can therefore assume the damage to the kernel occurred in prior ADT tests.
11:02:46 DEBUG| [stdout] [ 3093.210307] unregister_netdevice: waiting for lo to become free. Usage count = 1
Current hypothesis is that corruption is happening with the bpf kernel regression tests.
I added a background task to dump out new dmesg messages and I now see messages such as the following *before* any stress-ng tests run. I think we can therefore assume the damage to the kernel occurred in prior ADT tests.
11:02:46 DEBUG| [stdout] [ 3093.210307] unregister_ netdevice: waiting for lo to become free. Usage count = 1
Current hypothesis is that corruption is happening with the bpf kernel regression tests.