On Sun, Apr 14, 2019 at 09:53:12AM +0200, Ralf Jung wrote:
> Hi Salvatore,
>
> >> A self-compiled upstream 4.20.14 kernel does not show this problem, but the
> >> latest kernel in testing still does.
> >
> > have you tried to isolate the fixing commit for this issue?
>
> No, I have not.
> We are having a string of weird issues in our network (that we run in our free
> time) so far this year so all the time I had went into debugging this and
> other
> issues.
>
> Would it be helpful for you to know the fixing commit?
If the fixing commit can be identified and if it's not too intrusive to
backport, it could be considered for the 4.19 stable backports and would
thus be fixed in Buster (as buster is following the 4.19.x kernels both
in the freeze and during the lifetime of the buster stable release.
Cheers,
Moritz
