Thanks for taking care. Of course I can not say 100% that the behaviour will never ever happen again with 6.2.0-32, because it was something like 4/10 on 5.15.0-82 with no clear pattern but I'll update this ticket if I have any news.
Perhaps you/someone can backport the fix from 6.2.0-32 to 5.15.0-83 because the latter seems to be LTS (until APR 2027) and the former rather short lived.
Hi Andreas!
Thanks for taking care. Of course I can not say 100% that the behaviour will never ever happen again with 6.2.0-32, because it was something like 4/10 on 5.15.0-82 with no clear pattern but I'll update this ticket if I have any news.
Perhaps you/someone can backport the fix from 6.2.0-32 to 5.15.0-83 because the latter seems to be LTS (until APR 2027) and the former rather short lived.