On Tue, Mar 05, 2024 at 05:42:45PM +0200, Adrian Bunk wrote: > liburing is Not-For-Us on Alpha since 2022, and if I saw it correctly > imago was recently twice killed by bfs (which now uses io_uring). > > Recent kernels do contain io_uring fixes (e.g. in 5.10.186), > which might or might not be related.
Still running a 5.8.y kernel on Imago because of rare random memory corruption issues with later kernels, but have recently tracked that down to the use of CONFIG_COMPACTION, so will work on getting a newer kernel installed and can test io_uring. > Blacklisting liburing and packages build depending on it on imago might > be a (not necessarily complete) short-term workaround, currently these > would be: > > Reverse-Build-Depends > ===================== > * bfs (for liburing-dev) > * ceph (for liburing-dev) > * libdex (for liburing-dev) > * mariadb (for liburing-dev) > * mpd (for liburing-dev) > * plocate (for liburing-dev) > > This is not necessarily a complete workaround since libdex and > libmariadbd are linked with liburing, but it might be a short-term > workaround. Yeah, I put bfs into the no-auto-build list on Imago because it kept crashing the machine hard. It does seem to build on the qemu instances which I think are running newer kernels, so that might be an indication that getting a newer kernel onto Imago might be the solution. Cheers Michael.