Hi,This looks a lot similar to what we saw here, on Gitlab runner Docker hosts, building various internal things.
The build jobs would *sometimes* have the containerized runner deadlock on io_uring, timeout, and the build fail. Then another build would start a fresh container, leaving the old one still hanging. Almost like old-school NFS unkillable deadlocks - these too were unable to receive even a SIGKILL, and the system "load" numbers gradually increased.
This only happened on linux-image-6.1.0-27 (Built-Using: linux (= 6.1.115-1). No such problem on 6.1.0-26.
We currently no longer have a runner host on 6.1.0-27.Would this be fixed by commit 9e8debb8e51354b201db494689198078ec2c1e75 in upstream https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.116 ?
-- Ystävällisin terveisin Mikko Nahkola System Engineer mikko.nahk...@trivore.fi +358 415 569 026 Trivore Oy www.trivore.com Helsinginkatu 15, 20500 Turku
OpenPGP_0x0148C3A897C53DC0.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
