On Fri, Jun 9, 2023 at 11:42 AM Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
>
> I managed to revise my bisect script sufficiently enough to get reliable
> results. It looks like the culprit is commit 503e554782c9 (" debugobject:
> Ensure pool refill (again)"); see bisect log below. Bisect on four
> different systems all have the same result. After reverting this patch,
> I do not see the problem anymore (again, confirmed on four different
> systems).
Does this happen on mainline too? It's commit 0af462f19e63 in the upstream tree.
It was in 6.4-rc1, and I see a clean result from you at least for
-rc2, so for some reason it sounds like upstream is ok. But I don't
really see why that would be the case...
Linus
