Comment # 11 on bug 1170822 from Anthony Iliopoulos

(In reply to Ismail D�nmez from comment #9)
>
> I can (un)fortunately can reproduce this still :-) I guess you want me to
> checkout kernel-source for our packages from github and do a git bisect,
> starting from v5.4?

You mentioned this being reproducible on vanilla too, correct? In that case,
once your machine is back online, I'd first check if this is reproducible still
on our latest vanilla build. If you can still trigger it there, it would
certainly indicate an upstream bug and would probably be easier to bisect
directly on the mainline upstream tree, as our vanilla tree isn't updated on
every upstream commit (so a single kernel-source/vanilla commit will contain
multiple upstream commits).

I suppose we can easily build a vanilla 5.4 or so in ibs and also check if this
works or not, to have a starting point for a bisection (unless you remember any
older specific version that this wasn't reproducible). I'd probably restrict
the bisection to fs and mm (hopefully the bug is contained there) to minimize
the steps. I wonder if this would be reproducible in a large VM on top of the
same machine, so that you could automate the bisect and save you some time.

Ping me if you want before you start bisection to discuss any details.