Renato Gallo <vmxevils...@gmail.com> wrote: > try with the stable 5.19.0 or directly with 6.0
I'm happy to, but how? I can't find a package of 5.19.x or 6.x anywhere in buster-backports. Searching on packages.debian.org turns up linux-image-5.19.0-trunk-arm64 in the experimental distribution, and no 6.0 at all. I'd really rather not have to _build_ a kernel on a Raspberry Pi - even on a Pi 4 that would take ages! So I guess I should try installing the experimental 5.19 alongside my buster kernels and hope nothing goes too badly wrong? Assuming I've correctly identified the upstream git commit that's the culprit, it looks as if the unwanted FLAG_SEND_ZLP is still in 5.19.1, but not in 5.19.2. If I'm reading packages.debian.org right, that means the 5.19 Debian kernel I've found is still likely to contain the bug. (And 6.0 has had the FLAG_SEND_ZLP reverted as well.) Cheers, Simon -- for k in [pow(x,37,0x1a1298d262b49c895d47f) for x in [0x50deb914257022de7fff, 0x213558f2215127d5a2d1, 0x90c99e86d08b91218630, 0x109f3d0cfbf640c0beee7, 0xc83e01379a5fbec5fdd1, 0x19d3d70a8d567e388600e, 0x534e2f6e8a4a33155123]]: print("".join([chr(32+3*((k>>x)&1))for x in range(79)])) # <ana...@pobox.com>