4 ms·
To be fair, it was just a bug in 6.1.64, which was already fixed in 6.1.66. Both are "old" kernels, so it's nothing to worry about, unless you were deliberately
by d3Xt3r 3y ago
To be fair, it was just a bug in 6.1.64, which was already fixed in 6.1.66. Both are "old" kernels, so it's nothing to worry about, unless you were deliberately staying on 6.1 for some odd reason (yes, I'm aware 6.1 is LTS, but so is 6.6).
- cpach 3y agoAFAICT Debian was rolling out 6.1.66 but had to stop in order to patch the kernel (Or bump version…? Not sure.) https://micronews.debian.org/2023/1702150551.html https://micronews.debian.org/2023/1702150551.html
- clysm 3y ago> so it's nothing to worry about Except for debian bookworm stable.