From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Arendt Subject: Re: kernel 4.18.5 Realtek 8111G network adapter stops responding under high system load Date: Wed, 19 Sep 2018 06:12:54 +0200 Message-ID: <0e865e74-e587-61b7-d319-9afe0a5e8828@prnet.org> References: <20180918102349.Horde.yHctatUod-_SC696oYKmySa@cloud.luxmemories.lu> <039cc66f-13b0-e745-b6ec-68f4580e90ef@maciej.szmigiero.name> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, nic_swsd@realtek.com, netdev@vger.kernel.org, Heiner Kallweit To: "Maciej S. Szmigiero" Return-path: In-Reply-To: <039cc66f-13b0-e745-b6ec-68f4580e90ef@maciej.szmigiero.name> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi, Thanks for the patch. I just applied it and the TxConfig register now contains 0x4f000f80. The next day will show if it really solves the problem. Thanks in advance, David Arendt On 9/19/18 12:30 AM, Maciej S. Szmigiero wrote: > Hi, > > On 18.09.2018 12:23, David Arendt wrote: >> Hi, >> >> Today I had the network adapter problems again. >> So the patch doesn't seem to change anything regarding this problem. >> This week my time is unfortunately very limited, but I will try to >> find some time next weekend to look a bit more into the issue. > If the problem is caused by missing TXCFG_AUTO_FIFO bit in TxConfig, > as the register difference would suggest, then you can try applying > the following patch (hack) on top of 4.18.8 that is already patched > with commit f74dd480cf4e: > --- a/drivers/net/ethernet/realtek/r8169.c > +++ b/drivers/net/ethernet/realtek/r8169.c > @@ -5043,7 +5043,8 @@ > { > /* Set DMA burst size and Interframe Gap Time */ > RTL_W32(tp, TxConfig, (TX_DMA_BURST << TxDMAShift) | > - (InterFrameGap << TxInterFrameGapShift)); > + (InterFrameGap << TxInterFrameGapShift) > + | TXCFG_AUTO_FIFO); > } > > static void rtl_set_rx_max_size(struct rtl8169_private *tp) > > This hack will probably only work properly on RTL_GIGA_MAC_VER_40 or > later NICs. > > Before running any tests please verify with "ethtool -d enp3s0" that > TxConfig register now contains 0x4f000f80, as it did in the old, > working driver version. > > If this does not help then a bisection will most likely be needed. > >> Thanks in advance, >> David Arendt > Maciej