“Kernel regressions” was a little bit too generalizing in this meme. Technically drivers that became part of the kernel can also regress, as recently seen by users of Corsair Void wireless headsets (an unpatched 6.13 kernel is panicing once the headset adapter is plugged in).
Broken driver. It now seemingly attempts to read the current battery status, and while doing so literally locks up (not sure what “locking” means in context of a Kernel, but it’s somehow involved).
Interesting! Do you have checked the kernel log (there should be a backup from last session somehow iirc) , and do you know the name of the kernel module as well as your kernel version?
I want to check that code out if I see where it fails exactly
Or have you documented that issue already somewhere?
“Kernel regressions” was a little bit too generalizing in this meme. Technically drivers that became part of the kernel can also regress, as recently seen by users of Corsair Void wireless headsets (an unpatched 6.13 kernel is panicing once the headset adapter is plugged in).
Does the headphone use bad vendor/product ID? Or how does a wireless dongle without driver panicking a kernel?
Or is there just a broken driver in the kernel?
Broken driver. It now seemingly attempts to read the current battery status, and while doing so literally locks up (not sure what “locking” means in context of a Kernel, but it’s somehow involved).
Interesting! Do you have checked the kernel log (there should be a backup from last session somehow iirc) , and do you know the name of the kernel module as well as your kernel version?
I want to check that code out if I see where it fails exactly
Or have you documented that issue already somewhere?
Already reported with a patch incoming.
😍🫡thank you for your service