Hi, On Tue, Jul 13, 2021 at 03:26:22PM +0200, s...@gmxpro.de wrote: > > > > > thanks for confirming this as well, so adding a found version. Next > > step would be to check the latest 5.10.y upstream version. If it's an > > issue there, next to report it upstream. > > > > Just to understand that correctly - shall I wait for the next update for > the kernel in buster-backports and try that one? > > I tried 5.10.40-1~bpo10+1 amd64 which is currently the latest one in > buster-backports.
Actually I was targetting at something else (but apart that if you can fetch the unstable's kernel then you can verify as well 5.10.46-1): I meant to verify directly upstream's mainline and latest 5.10.y form upstream. How to do that, we tried to document in https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-kernel-org-package If you find the issue is still present in the most current version, my aim was that we can report it upstream as issue. One further aspect is: If you find an earlier version you known to be non-broken with the setup, bisecting could lead to the introducing commit which introduces the issue, and so enlight some further more. Does this help so far? Regards, Salvatore
