From: "Ortwin Glück" <odi@odi.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>,
David Arendt <admin@prnet.org>,
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
Gabriel C <nix.or.die@gmail.com>
Cc: linux-kernel@vger.kernel.org, nic_swsd@realtek.com,
netdev@vger.kernel.org
Subject: Re: kernel 4.18.5 Realtek 8111G network adapter stops responding under high system load
Date: Thu, 27 Sep 2018 17:48:17 +0200 [thread overview]
Message-ID: <b91cbc27-4dcb-2260-00ed-cc7328798670@odi.ch> (raw)
In-Reply-To: <968f03ee-a271-242b-d90a-5c70ea72ce3b@gmail.com>
On 25.09.18 23:03, Heiner Kallweit wrote:
> It seems that all chip versions from 34 (= RTL8168E-VL) with the
> exception of version 39 (= RTL8106E, first sub-version) need
> bit TXCFG_AUTO_FIFO.
>
> And indeed, due to reordering of calls this bit is overwritten.
> Following patch moves setting the bit from the chip-specific
> hw_start function to rtl_set_tx_config_registers().
>
> Whoever is hit by the issue and has the option to build a kernel,
> could you please test whether the patch fixes the issue for you?
Hi,
Looks good so far! No problems for almost 24 hours. This is on a router/firewall that links various
sites via IPSec and other VPNs and has >10 network interfaces, 5 of which are Realtek ones.
Thanks,
Ortwin
# uname -a
Linux lofw 4.18.10+ #72 SMP PREEMPT Wed Sep 26 17:07:07 CEST 2018 x86_64 Intel(R) Core(TM) i5-7500
CPU @ 3.40GHz GenuineIntel GNU/Linux
# uptime
17:42:37 up 22:54, 1 user, load average: 0.48, 0.38, 0.30
# ifconfig wan
wan: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 81.7.230.226 netmask 255.255.255.248 broadcast 81.7.230.231
inet6 fe80::529a:4cff:fe2e:92be prefixlen 64 scopeid 0x20<link>
ether 50:9a:4c:2e:92:be txqueuelen 100 (Ethernet)
RX packets 56342905 bytes 40589502599 (37.8 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 54032328 bytes 44607761646 (41.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
# ifconfig lan
lan: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.11.1.1 netmask 255.255.255.0 broadcast 10.11.1.255
inet6 fe80::20a:cdff:fe31:6022 prefixlen 64 scopeid 0x20<link>
ether 00:0a:cd:31:60:22 txqueuelen 100 (Ethernet)
RX packets 54799469 bytes 43111097607 (40.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 55158558 bytes 35746992802 (33.2 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
next prev parent reply other threads:[~2018-09-27 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 6:19 kernel 4.18.5 Realtek 8111G network adapter stops responding under high system load David Arendt
2018-09-15 21:23 ` David Arendt
2018-09-15 23:54 ` Maciej S. Szmigiero
2018-09-16 12:38 ` David Arendt
2018-09-16 23:11 ` Maciej S. Szmigiero
2018-09-18 10:23 ` David Arendt
2018-09-18 22:30 ` Maciej S. Szmigiero
2018-09-19 4:12 ` David Arendt
2018-09-25 21:03 ` Heiner Kallweit
2018-09-26 16:44 ` David Arendt
2018-09-27 15:48 ` Ortwin Glück [this message]
2018-09-27 19:33 ` David Arendt
2018-09-19 16:34 ` David Arendt
2018-09-21 22:28 ` Maciej S. Szmigiero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b91cbc27-4dcb-2260-00ed-cc7328798670@odi.ch \
--to=odi@odi.ch \
--cc=admin@prnet.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=nix.or.die@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).