Just wanted to mention that kernel 5.19.0-41 is still affected.
In my case the problem does happen much less often on 5.19.0-41 than when it was introduced in 5.19.0-35 or so, but to be honest it is still frustrating. For the time being I'm reverting back to 5.19.0-32.
Hi all,
Just wanted to mention that kernel 5.19.0-41 is still affected.
In my case the problem does happen much less often on 5.19.0-41 than when it was introduced in 5.19.0-35 or so, but to be honest it is still frustrating. For the time being I'm reverting back to 5.19.0-32.