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

Message-ID: <YtxI7HedPjWCvuVm@blisses.org>
Date:   Sat, 23 Jul 2022 15:15:56 -0400
From:   Mason Loring Bliss <mason@...sses.org>
To:     Realtek linux nic maintainers <nic_swsd@...ltek.com>,
        Francois Romieu <romieu@...zoreil.com>
Cc:     netdev@...r.kernel.org
Subject: Issue with r8169 (using r8168 for now) driving 8111E

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.

-- 
Mason Loring Bliss  ((   If I have not seen as far as others, it is because
 mason@...sses.org   ))   giants were standing on my shoulders. - Hal Abelson

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