netdev - Re: Issue with r8169 (using r8168 for now) driving 8111E

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Yt25TiVImcnpnuAE@blisses.org>
Date:   Sun, 24 Jul 2022 17:27:42 -0400
From:   Mason Loring Bliss <mason@...sses.org>
To:     Francois Romieu <romieu@...zoreil.com>
Cc:     Realtek linux nic maintainers <nic_swsd@...ltek.com>,
        netdev@...r.kernel.org, hkallweit1@...il.com
Subject: Re: Issue with r8169 (using r8168 for now) driving 8111E

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@...sses.org
They also surf, who only stand on waves.

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)