** Description changed:
Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to
linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots
with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8,
Public bug reported:
Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to
linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots
with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means
Note that this is not limited to containerd; we're running an upstream
version of the prometheus `node_exporter` on several hosts that is also
seeing spurious hangs that started after upgrading to the -132 kernel.
Rebooting into -131 fixes it.
--
You received this bug notification because you are
We're seeing a similar crash on a 16.04 based machine running
4.15.0-66-generic ; downgrading to 4.15.0-51-generic appears to prevent
it.
Appended kernel log with very similar entries.
** Attachment added: "kernel log from loading ceph to reboot"
https://bugs.launchpad.net/ubuntu/+source/linu
4 matches
Mail list logo