[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...



On Fri, Jan 5, 2024 at 9:18 AM Albretch Mueller <lbrtchx@gmail.com> wrote:
>
>  I decided to upgrade to Bookworm because I needed to use some NVRAM
> memory supposedly available in my computer, but then my wireless
> Ethernet started to "complain". I initially thought those errors might
> be related to the lazy use of the Ethernet drivers from Bullseye but
> when I started to use Bookworm's drivers the errors became more
> complicated. Following some hints from:
>
>  https://askubuntu.com/questions/863150/pcie-bus-error-severity-corrected-type-physical-layer-id-00e5receiver-id
>
> [290569.588458] pcieport 0000:00:1d.0: AER: Multiple Corrected error
> received: 0000:01:00.0
> [290569.588488] r8169 0000:01:00.0: PCIe Bus Error:
> severity=Corrected, type=Physical Layer, (Receiver ID)
> [290569.588489] r8169 0000:01:00.0:   device [10ec:8136] error
> status/mask=00000001/00006000
> [290569.588491] r8169 0000:01:00.0:    [ 0] RxErr                  (First)
>
>  I found out it was the Realtek RTL810xE PCI Express Fast Ethernet controller:
>
> $ lspci -nn | grep PCIe
> 00:1d.1 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCIe Port
> [8086:34b1] (rev 30)
>
> $ sudo hwinfo --pci
> ...
> 14: PCI 100.0: 0200 Ethernet controller
>   [Created at pci.386]
>   Unique ID: lkKU.j9EpqGNzpV9
>   Parent ID: 1GTX.j6F4IaHYGk7
>   SysFS ID: /devices/pci0000:00/0000:00:1d.0/0000:01:00.0
>   SysFS BusID: 0000:01:00.0
>   Hardware Class: network
>   Model: "Realtek RTL810xE PCI Express Fast Ethernet controller"
>   Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
>   Device: pci 0x8136 "RTL810xE PCI Express Fast Ethernet controller"
>   SubVendor: pci 0x1028 "Dell"
>   SubDevice: pci 0x097c
>   Revision: 0x07
>   Driver: "r8169"
>   Driver Modules: "r8169"
>   Device File: enp1s0
>   I/O Ports: 0x3000-0x3fff (rw)
>   Memory Range: 0x91400000-0x91400fff (rw,non-prefetchable)
>   Memory Range: 0x91200000-0x91203fff (ro,non-prefetchable)
>   IRQ: 16 (2575859 events)
>   HW Address: c0:3e:ba:26:aa:93
>   Permanent HW Address: c0:3e:ba:26:aa:93
>   Link detected: no
>   Module Alias: "pci:v000010ECd00008136sv00001028sd0000097Cbc02sc00i00"
>   Driver Info #0:
>     Driver Status: r8169 is active
>     Driver Activation Cmd: "modprobe r8169"
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
> ...
> $
>
> $ sudo hwinfo --network
> 25: None 00.0: 10701 Ethernet
>   [Created at net.126]
>   Unique ID: VV91.ndpeucax6V1
>   Parent ID: qru8.BzdVZ3YOQjC
>   SysFS ID: /class/net/wlp2s0
>   SysFS Device Link: /devices/pci0000:00/0000:00:1d.1/0000:02:00.0
>   Hardware Class: network interface
>   Model: "Ethernet network interface"
>   Driver: "ath10k_pci"
>   Driver Modules: "ath10k_pci"
>   Device File: wlp2s0
>   HW Address: 5c:3a:45:0a:fb:c1
>   Permanent HW Address: 5c:3a:45:0a:fb:c1
>   Link detected: yes
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
>   Attached to: #4 (Ethernet controller)
>
> 26: None 00.0: 10700 Loopback
>   [Created at net.126]
>   Unique ID: ZsBS.GQNx7L4uPNA
>   SysFS ID: /class/net/lo
>   Hardware Class: network interface
>   Model: "Loopback network interface"
>   Device File: lo
>   Link detected: yes
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
>
> 27: None 00.0: 10701 Ethernet
>   [Created at net.126]
>   Unique ID: QObM.ndpeucax6V1
>   Parent ID: lkKU.j9EpqGNzpV9
>   SysFS ID: /class/net/enp1s0
>   SysFS Device Link: /devices/pci0000:00/0000:00:1d.0/0000:01:00.0
>   Hardware Class: network interface
>   Model: "Ethernet network interface"
>   Driver: "r8169"
>   Driver Modules: "r8169"
>   Device File: enp1s0
>   HW Address: c0:3e:ba:26:aa:93
>   Permanent HW Address: c0:3e:ba:26:aa:93
>   Link detected: no
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
>   Attached to: #8 (Ethernet controller)
> $
>
>  After using Bookworm drivers I am still getting:
>
> [ 9514.141680] pcieport 0000:00:1d.0: AER: Multiple Corrected error
> received: 0000:01:00.0
> [ 9514.141723] r8169 0000:01:00.0: PCIe Bus Error: severity=Corrected,
> type=Physical Layer, (Receiver ID)
> [ 9514.141728] r8169 0000:01:00.0:   device [10ec:8136] error
> status/mask=00000001/00006000
> [ 9514.141734] r8169 0000:01:00.0:    [ 0] RxErr                  (First)
>
> Why would such errors start happening with I tried to use the NVRAM
> card? Why would that happen? How do you troubleshoot such errors in a
> more in depth way?

Before going down the rabbit hole, I would:

  1. update firmware for the computer and card
  2. use a new [known good] ethernet cable
  3. change ports at the switch

It is possible the messages are somewhat expected since they appear to
be part of PCI AER (Advanced Error Reporting). It is possible another
host is putting bad bits on the wire, and your machine is correcting
them. If another machine on your network is responsible, then you
might see different results if you plug your computer directly into
your router rather than a switch on your internal network.

There is another discussion of PCI AER at
<https://forums.developer.nvidia.com/t/pcie-bus-error-severity-corrected-type-physical-layer-id-0010-receiver-id/251840/19>.
You might find something of interest in it.

Jeff


Reply to: