netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mason Loring Bliss <mason@blisses.org>
To: Realtek linux nic maintainers <nic_swsd@realtek.com>,
	Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Issue with r8169 (using r8168 for now) driving 8111E
Date: Sat, 23 Jul 2022 15:15:56 -0400	[thread overview]
Message-ID: <YtxI7HedPjWCvuVm@blisses.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

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@blisses.org   ))   giants were standing on my shoulders. - Hal Abelson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2022-07-23 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 19:15 Mason Loring Bliss [this message]
2022-07-23 20:48 ` Issue with r8169 (using r8168 for now) driving 8111E 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

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=YtxI7HedPjWCvuVm@blisses.org \
    --to=mason@blisses.org \
    --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).