Ubuntu
linux package

  1. Bug #1845797
  2. Comment #57

Comment 57 for bug 1845797

Revision history for this message
In , freedman.joshua (freedman.joshua-linux-kernel-bugs) wrote :

(In reply to C Sights from comment #30)
> (In reply to Josh from comment #29)
>
> If you could git bisect the kernel and find out which commit breaks between
> 5.16.11 and 5.16.13 you might get some attention and keep the gains.

Ok, so 5.16.11 is good, 5.16.12 is bad. I looked at the git bisect tool, but I don't know enough to say what commits are relevant and or bad/good.