Hi!
On Tue, 2022-07-19 at 08:28:09 +0200, Paul Gevers wrote: > On 18-07-2022 23:44, Guillem Jover wrote: > > While only having skimmed over the logs, the first suspect for me would > > be the Linux kernel, where liburing might be triggering some kernel bug. > > Were the systems upgraded around that time with a newer kernel version > > (is that a 5.18.x from bpo)? > > In Debian we did have a point release on 2022-07-09, I upgraded that evening > (UTC). So this seems to confirm that the problem lays elsewhere. :) > > The only other options if that would not > > have been the case that seem plausible would be glibc (which was uploaded > > on the 10th, and could be a suspect), or lxc itself or similar, but that > > has not been uploaded for a while in sid. > > lxc comes from stable. Everything in it is either unstable or testing. > > I'm not totally sure about the Ubuntu setup. Maybe Brian can comment on > that. The liburing test suite works on the buildds, I just uploaded a new release and it built fine locally with Linux 5.19.0-trunk-amd64, and on the buildds. I think this needs to be reassigned, I'd assume to the kernel (but I'm not entirely sure). Also could a newer kernel be tried on the infra? Thanks, Guillem
