On 4 February 2023 22:28:05 CET, Salvatore Bonaccorso <car...@debian.org> wrote: >Hi, > >On Fri, Feb 03, 2023 at 09:31:01AM +0000, RattusRattus wrote: >> Dear team, >> >> - Did I submit to the correct location? >> - Is there anything additional information that you require? > >It is okay, but even better if the issue can be brough upstream. But >that said, I would not expect really any progress, in fact upstream it >is discussed if it might be removed in future, cf. >https://lwn.net/Articles/920259/ . > >It seems to be a hard to tackle problem if it's not really >reproducible and machine dependent. But if reproduces for you quite >consistently, a bisect between the last known working version and >kernel in recent bullseye point release which started failing might >pin point us to the relevant change causing this. > >Dave, adding you to CC, this is about report >https://bugs.debian.org/1026259 in Debian. This was noted with at >least 5.10.158 based stable kernel in Debian. My understanding is that >at least 5.10.127 was still fine. > >Regards, >Salvatore >
I can certainly reproduce the problem repeatedly, perhaps 50% of the time, maybe more. Will happily bisect versions to see if I can identify if this is a regression or has always been present. I may have some time available in a weeks time to investigate (half term) I may be able to automate the process too Best wishes /Andy
