On Tue, 2020-08-25 at 13:06 +0200, Heiner Kallweit wrote:
> I don't see how the improvement to the r8169 driver and the issues deep
> in the network stack should be related. Was the referenced r8169 commit
> result of a bisect?
Nope, just a best guess.
It takes some hours to hit the issue and mos
On 25.08.2020 11:32, Christoph Fritz wrote:
> Hello Heiner,
>
> please see the trace below.
>
> With your upstream commit applied to v4.19 I'm not getting the issue
> anymore:
>
I don't see how the improvement to the r8169 driver and the issues deep
in the network stack should be related. Was t
Hello Heiner,
please see the trace below.
With your upstream commit applied to v4.19 I'm not getting the issue
anymore:
[PATCH] r8169: handle all interrupt events in the hard irq handler
SHA1 ID: 260cfeb096f18ed8b54178d930ff5c61bf13b28b
Would you recommend this commit for stable v4.19.y branch
