On Saturday, 7 February 2026 at 17:11, Salvatore Bonaccorso <[email protected]> wrote:
> > > Hi Wolf, > > On Sat, Feb 07, 2026 at 01:38:55PM +0000, Wolf wrote: > > > On Saturday, 7 February 2026 at 14:59, Salvatore Bonaccorso > > [email protected] wrote: > > > > > Hi, > > > > > > On Sat, Feb 07, 2026 at 12:48:58PM +0000, Wolf wrote: > > > > > > > Hello, > > > > > > > > Upgrading to linux/6.18.8-1 (2026-01-31) two days ago solved the > > > > problem, so I removed udev rule. > > > > But today upgrade reintroduced it. > > > > > > This is not surprising, the proposed patch has not yet landed upstream > > > in mainline (and neither yet backported to the 6.18.y series). So > > > maybe you had still the locally patched version installed? > > > > > > Regards, > > > Salvatore > > > > Hello, Salvatore > > > > I saw the patch was proposed for 6.20. > > Also, I removed all locally patched versions. > > > > I was using linux/6.18.8-1 since I found it is working, two day ago, when I > > also removed the udev rule to catch any further error. > > > > After today's errors I thought it useful to inform this. > > > Yes sure. It is though suprising if you say 6.18.8-1 was working, > because I'm pretty sure the fix has not landed yet. > > Stay tuned for a fix :) > > Regards, > Salvatore Hello, Last upgrade to 6.18.9-1 (2026-02-07) solved the bug. So, I rebuilt initramfs (update-initramfs -u) and the errors reappeared. Regards, Wolf
