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] [thread-next>] [day] [month] [year] [list]

Message-ID: <68983671-039d-ce1c-e5c2-33e0d03e6a5f@gmail.com>
Date:   Sat, 23 Jul 2022 22:48:27 +0200
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Mason Loring Bliss <mason@...sses.org>
Cc:     netdev@...r.kernel.org, Francois Romieu <romieu@...zoreil.com>,
        Realtek linux nic maintainers <nic_swsd@...ltek.com>
Subject: Re: Issue with r8169 (using r8168 for now) driving 8111E

On 23.07.2022 21:15, Mason Loring Bliss wrote:
> Hi all. I was happily running Debian Buster with Linux 4.19.194 driving a
> pair of 8111E NICs as included on this board:
> 
>     https://www.aaeon.com/en/p/mini-itx-emb-cv1
> 
> I upgraded to Debian Bullseye running 5.10.127 and started seeing this
> popping up regularly in dmesg, with the status varying:
> 
>     r8169 0000:03:00.0 eth1: Rx ERROR. status = 3529c123
> 
> As this box is being used as a firewall, I didn't want to leave it with an
> obvious issue, so I installed r8168-dkms and it appears to function with no
> issues.
> 
> If it matters, I was not seeing the error against eth0, just eth1, and in
> this case eth1 is used for PPPoE to the world, while eth0 talks to my
> internal network.
> 
> I've not yet tried the Debian-backports kernel to see if the r8169 there
> works, but I can do so given some scheduled downtime. I'm writing in
> advance of that in case the nature of the issue jogs a memory of something
> already seen and addressed.
> 
> If you tell me what debugging data might be useful, I can supply it.
> 

The error message indicates an incoming packet CRC error.
4.19 doesn't report rx errors per default whilst more recent
kernel versions do.