From: Mason Loring Bliss <mason@blisses.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
netdev@vger.kernel.org, hkallweit1@gmail.com
Subject: Re: Issue with r8169 (using r8168 for now) driving 8111E
Date: Sun, 24 Jul 2022 17:27:42 -0400 [thread overview]
Message-ID: <Yt25TiVImcnpnuAE@blisses.org> (raw)
In-Reply-To: <Ytx7nc3FosXV6ptC@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Sun, Jul 24, 2022 at 12:52:13AM +0200, Francois Romieu wrote:
> The driver should receive and process this kind of CRC errored packet since
> 79d0c1d26e1eac0dc5b201e66b65cc5e4e706743 ("r8169: Support RX-FCS flag.")
> provided ethtool was not used to disable it (see -k/-K and rx-fcs/rx-all).
> tcpdump may thus help to identify some pattern in the packet.
Thank you for the additional detail!
It appears to be the case that having an APC surge supressor inline,
despite it being labelled as gigabit-capable, was the cause of the CRC
errors. I changed cables, and that not helping, I swapped in different APC
units, and the errors persisted until I went straight from NIC to ONT. Now
I've gone a couple hours without seeing an error, and haven't in fact seen
one since the link came back up after the most recent change.
I'm glad the driver stopped suppressing these errors, or I'd not have known
the inline surge supression was a bit flaky. Thank you.
--
Mason Loring Bliss mason@blisses.org
They also surf, who only stand on waves.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-07-24 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 19:15 Issue with r8169 (using r8168 for now) driving 8111E Mason Loring Bliss
2022-07-23 20:48 ` Heiner Kallweit
2022-07-23 21:43 ` Mason Loring Bliss
2022-07-23 22:52 ` Francois Romieu
2022-07-24 21:27 ` Mason Loring Bliss [this message]
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=Yt25TiVImcnpnuAE@blisses.org \
--to=mason@blisses.org \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.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).