Problem with RTL8126 NIC / Driver; don't know how to get it working

TDW0kxvche9

Member
Sep 1, 2022
15
3
8
Hi there,
i've bought a PCIe-NIC with RTL8126 chip (1,2.5,5 Gbit) and having problems to set it up correctly.
The chip actual isn't supported by the actual proxmox kernel (6.8.x.x) and on the realtek driver site (https://www.realtek.com/Download/List?cate_id=584) is only one entry for this card: 5G Ethernet LINUX driver r8126 for kernel up to 6.4

I'm no linux pro, but what i did: Booted several PVE-Kernels (6.8, 6.5., 6.2) and installed the driver package (unpack the driver -> ./autorun.sh); last try with Kernel 6.2, which should be compatible with the above driver. I've created a new linux bridge vmbr1, give it a ip and set the interface to enp6s0. I bound vmbr1 to a Windows-VM to check, if i can reach the devices in my network - that's not the case.

pveversion
Code:
pve-manager/8.2.4/faa83925c9641325 (running kernel: 6.2.16-5-pve)

With 6.2 and lspci -v i get:
Code:
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        !!! Unknown header type 7f
        I/O ports at 3000 [size=256]
        Memory at 41410000 (64-bit, non-prefetchable) [size=64K]
        Memory at 41420000 (64-bit, non-prefetchable) [size=16K]
        Expansion ROM at 41400000 [disabled] [size=64K]
        Kernel driver in use: r8126
        Kernel modules: r8126
dmesg spams:
Code:
[  410.073142] enp6s0: pci link is down
               .
[  412.089213] enp6s0: cmd = 0xff, should be 0x07
               .
[  412.089232] enp6s0: pci link is down
               .
[  414.105022] enp6s0: cmd = 0xff, should be 0x07

The NIC-LEDs blink, so i think, it has a link; but the state is "down":
ip a show enp6s0
Code:
root@fb4-PVE-1:~# ip a show enp6s0
2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr1 state DOWN group default qlen 1000
    link/ether 88:c9:b3:b4:07:70 brd ff:ff:ff:ff:ff:ff

List of NICs:
Code:
root@fb4-PVE-1:~# lshw -class network -short
H/W path           Device          Class          Description
=============================================================
/0/100/1c.5/0      enp5s0          network        I210 Gigabit Network Connection
/0/100/1c.7/0      enp6s0          network        Realtek Semiconductor Co., Ltd.
/0/100/1f.6        eno1            network        Ethernet Connection (7) I219-LM

Modinfo:
Code:
root@fb4-PVE-1:~# modinfo r8126
filename:       /lib/modules/6.2.16-5-pve/kernel/drivers/net/ethernet/realtek/r8126.ko
version:        10.013.00-NAPI
license:        GPL
description:    Realtek r8126 Ethernet controller driver
author:         Realtek and the Linux r8126 crew <netdev@vger.kernel.org>
srcversion:     6A363CDCE8D31E10F09DF08
alias:          pci:v000010ECd00005000sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008126sv*sd*bc*sc*i*
depends:       
retpoline:      Y
name:           r8126
vermagic:       6.2.16-5-pve SMP preempt mod_unload modversions
parm:           speed_mode:force phy operation. Deprecated by ethtool (8). (uint)
parm:           duplex_mode:force phy operation. Deprecated by ethtool (8). (uint)
parm:           autoneg_mode:force phy operation. Deprecated by ethtool (8). (uint)
parm:           aspm:Enable ASPM. (int)
parm:           s5wol:Enable Shutdown Wake On Lan. (int)
parm:           s5_keep_curr_mac:Enable Shutdown Keep Current MAC Address. (int)
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
parm:           timer_count:Timer Interrupt Interval. (int)
parm:           eee_enable:Enable Energy Efficient Ethernet. (int)
parm:           hwoptimize:Enable HW optimization function. (ulong)
parm:           s0_magic_packet:Enable S0 Magic Packet. (int)
parm:           tx_no_close_enable:Enable TX No Close. (int)
parm:           enable_ptp_master_mode:Enable PTP Master Mode. (int)
parm:           disable_wol_support:Disable PM support. (int)
parm:           enable_double_vlan:Enable Double VLAN. (int)
parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)

The behaviour of all tested pve-kernels is the same; so i'm not sure, what i can do to get this card working. Has anyone a idea, what i could do next?
 
With 6.2 and lspci -v i get:
Would you be ok to run lspci with -vv instead and paste the entire output (for the realtek nic) here?

Some of the additional fields in there (link status especially) could be relevant. :)

That aside, it seems a lot like the driver source code you have isn't communicating properly with the device. I'm not personally sure what you can do apart from contacting the Realtek people to ask for assistance. They might be helpful (no idea personally).
 
Last edited:
Would you be ok to run lspci with -vv instead and paste the entire output (for the realtek nic) here?

Some of the additional fields in there (link status especially) could be relevant. :)

That aside, it seems a lot like the driver source code you have isn't communicating properly with the device. I'm not personally sure what you can do apart from contacting the Realtek people to ask for assistance. They might be helpful (no idea personally).
Hi,
that's the output of lspci -vv:

Code:
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        !!! Unknown header type 7f
        Interrupt: pin ? routed to IRQ 19
        IOMMU group: 18
        Region 0: I/O ports at 3000 [size=256]
        Region 2: Memory at 41410000 (64-bit, non-prefetchable) [size=64K]
        Region 4: Memory at 41420000 (64-bit, non-prefetchable) [size=16K]
        Expansion ROM at 41400000 [disabled] [size=64K]
        Kernel driver in use: r8126
        Kernel modules: r8126

I've installed the latest 6.2-Kernel, rebootet with it, and installed the driver. I ran lspci -vv, the output was 2-3 times longer. After i reboot again, i got this short output and the "Unknown header type 7f".


@justinclift
Code:
root@fb4-PVE-1:~# ethtool enp6s0
Settings for enp6s0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
                                5000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
                                5000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 5000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: no


I've searched the web for help and also found 2-3 posts, that users got it working without trouble on e.g. raspbian and opensuse. Also with the Realtek-Driver and also on newer Kernels.

:-/
 
  • Like
Reactions: justinclift
Cool. That's still missing a few fields I was looking for. I must have been misremembering the number of -v options needed (sorry).

Please try the lspci thing again, but this time with 3 v's. So, lspci -vvv. And yep, that's for real, I'm not being funny. :)
 
The ethtool output for that looks fine btw. Nothing weird there, with only the Link detected: no bit showing any kind of problem.
 
The ethtool output for that looks fine btw. Nothing weird there, with only the Link detected: no bit showing any kind of problem.
Hi,
the output doesn't change, also, if i use -vvv instead of -v.

I've bootet the actual 6.8.8.2-Kernel and got the same outputs.

In dmesg, i don't find any errors regarding the 8126:
Code:
root@fb4-PVE-1:~# dmesg | grep 8126
[    0.402059] pci 0000:06:00.0: [10ec:8126] type 00 class 0x020000 PCIe Endpoint
[    2.748586] r8126: loading out-of-tree module taints kernel.
[    2.748594] r8126: module verification failed: signature and/or required key missing - tainting kernel
[    2.749695] r8126 Ethernet controller driver 10.013.00-NAPI loaded
[    2.749733] r8126 0000:06:00.0: enabling device (0000 -> 0003)
[    2.771115] r8126: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
[    2.773362] r8126  Copyright (C) 2024 Realtek NIC software team <nicfae@realtek.com>
[    2.781693] r8126 0000:06:00.0 enp6s0: renamed from eth0
[    8.207214] r8126 0000:06:00.0 enp6s0: entered allmulticast mode
[    8.207281] r8126 0000:06:00.0 enp6s0: entered promiscuous mode

But still got this flapping events:
Code:
[  168.650319] enp6s0: pci link is down
               .
[  170.698286] enp6s0: cmd = 0xff, should be 0x07
               .
[  170.698314] enp6s0: pci link is down
               .
[  172.746301] enp6s0: cmd = 0xff, should be 0x07


Edit:
I re-ran the autorun.sh with the following output - seems OK to me:
Code:
root@fb4-PVE-1:~/r8126-10.013.00# ./autorun.sh

Check old driver and unload it.
rmmod r8126
Build the module and install
/root/r8126-10.013.00/src/r8126_n.c:13358:1: warning: no previous prototype for ‘rtl8126_enable_msix’ [-Wmissing-prototypes]
13358 | rtl8126_enable_msix(struct rtl8126_private *tp)
      | ^~~~~~~~~~~~~~~~~~~
/root/r8126-10.013.00/src/rtl_eeprom.c:96:5: warning: no previous prototype for ‘rtl8126_eeprom_cmd_done’ [-Wmissing-prototypes]
   96 | int rtl8126_eeprom_cmd_done(struct rtl8126_private *tp)
      |     ^~~~~~~~~~~~~~~~~~~~~~~
Skipping BTF generation for /root/r8126-10.013.00/src/r8126.ko due to unavailability of vmlinux
Warning: modules_install: missing 'System.map' file. Skipping depmod.
DEPMOD 6.8.8-2-pve
load module r8126
Updating initramfs. Please wait.
update-initramfs: Generating /boot/initrd.img-6.8.8-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Completed.

The autorun.sh created a logfile; seems also OK to me:
Code:
-------------------------------
Sat Jun 29 11:03:03 AM CEST 2024
make -C src/ clean
make[1]: Entering directory '/root/r8126-10.013.00/src'
make -C /lib/modules/6.8.8-2-pve/build M=/root/r8126-10.013.00/src clean
make[2]: Entering directory '/usr/src/linux-headers-6.8.8-2-pve'
  CLEAN   /root/r8126-10.013.00/src/Module.symvers
make[2]: Leaving directory '/usr/src/linux-headers-6.8.8-2-pve'
make[1]: Leaving directory '/root/r8126-10.013.00/src'
make -C src/ modules
make[1]: Entering directory '/root/r8126-10.013.00/src'
make -C /lib/modules/6.8.8-2-pve/build M=/root/r8126-10.013.00/src modules
make[2]: Entering directory '/usr/src/linux-headers-6.8.8-2-pve'
  CC [M]  /root/r8126-10.013.00/src/r8126_n.o
  CC [M]  /root/r8126-10.013.00/src/rtl_eeprom.o
  CC [M]  /root/r8126-10.013.00/src/rtltool.o
  LD [M]  /root/r8126-10.013.00/src/r8126.o
  MODPOST /root/r8126-10.013.00/src/Module.symvers
  CC [M]  /root/r8126-10.013.00/src/r8126.mod.o
  LD [M]  /root/r8126-10.013.00/src/r8126.ko
  BTF [M] /root/r8126-10.013.00/src/r8126.ko
make[2]: Leaving directory '/usr/src/linux-headers-6.8.8-2-pve'
make[1]: Leaving directory '/root/r8126-10.013.00/src'
make -C src/ install
make[1]: Entering directory '/root/r8126-10.013.00/src'
make -C /lib/modules/6.8.8-2-pve/build M=/root/r8126-10.013.00/src INSTALL_MOD_DIR=kernel/drivers/net/ethernet/realtek modules_install
make[2]: Entering directory '/usr/src/linux-headers-6.8.8-2-pve'
  INSTALL /lib/modules/6.8.8-2-pve/kernel/drivers/net/ethernet/realtek/r8126.ko
  SIGN    /lib/modules/6.8.8-2-pve/kernel/drivers/net/ethernet/realtek/r8126.ko
  DEPMOD  /lib/modules/6.8.8-2-pve
make[2]: Leaving directory '/usr/src/linux-headers-6.8.8-2-pve'
make[1]: Leaving directory '/root/r8126-10.013.00/src'

But still no change with lspci -vvv:
Code:
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        !!! Unknown header type 7f
        Interrupt: pin ? routed to IRQ 19
        IOMMU group: 18
        Region 0: I/O ports at 3000 [size=256]
        Region 2: Memory at 41410000 (64-bit, non-prefetchable) [size=64K]
        Region 4: Memory at 41420000 (64-bit, non-prefetchable) [size=16K]
        Expansion ROM at 41400000 [disabled] [size=64K]
        Kernel modules: r8126
 
Last edited:
  • Like
Reactions: justinclift
Damn. Yeah I guess the missing info (PCIe link capabilities, and negotiated link info) must be related to the unknown header thing and the related unhappiness.

Sorry dude, I'm not real sure what to do next. Definitely try contacting Realtek support though, just in case they have ideas. :)
 
Hey,
thanks you!
i've replaced the NIC with the second one i ordered (got 2 - PC<->Server) and used a different PCIe-Port; still the same problem :-/
 
  • Like
Reactions: justinclift
Don't know if it helps to debug the error; i got some errors in dmesg after a reboot:

Code:
[   21.709871] EXT4-fs (dm-6): mounted filesystem 27682894-8de6-470e-abf6-d472db3a4154 r/w with ordered data mode. Quota mode: none.
[   22.022907] kauditd_printk_skb: 16 callbacks suppressed
[   22.022910] audit: type=1400 audit(1719897351.133:28): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-100_</var/lib/lxc>" pid=1293 comm="apparmor_parser"
[   42.698391] watchdog: BUG: soft lockup - CPU#1 stuck for 25s! [kworker/1:2:643]
[   42.698397] Modules linked in: veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter scsi_transport_iscsi nf_tables bonding tls bluetooth ecdh_generic ecc softdog msr sunrpc nfnetlink_log binfmt_misc nfnetlink intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 jc42 mei_hdcp mei_pxp kvm snd_hda_intel snd_intel_dspcfg crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 snd_intel_sdw_acpi sha1_ssse3 aesni_intel crypto_simd cryptd drm_buddy snd_hda_codec rapl snd_hda_core cmdlinepart intel_wmi_thunderbolt spi_nor wmi_bmof mtd ee1004 snd_hwdep pcspkr intel_cstate gigabyte_wmi mei_me ttm snd_pcm mei drm_display_helper intel_pmc_core snd_timer intel_vsec joydev snd cec vgastate pmt_telemetry input_leds soundcore fb_ddc rc_core intel_pch_thermal ie31200_edac pmt_class acpi_pad mac_hid zfs(PO) spl(O) vhost_net vhost vhost_iotlb tap
[   42.698443]  vfio_pci vfio_pci_core irqbypass vfio_iommu_type1 vfio iommufd efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq hid_generic usbkbd usbmouse usbhid hid dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c nvme xhci_pci spi_intel_pci xhci_pci_renesas igb crc32_pclmul ahci i2c_i801 e1000e spi_intel i2c_algo_bit i2c_smbus libahci nvme_core r8126(OE) xhci_hcd nvme_auth dca video wmi pinctrl_cannonlake
[   42.698467] CPU: 1 PID: 643 Comm: kworker/1:2 Tainted: P           OE      6.8.8-2-pve #1
[   42.698469] Hardware name: Gigabyte Technology Co., Ltd. C246M-WU4/C246M-WU4-CF, BIOS F6 01/18/2022
[   42.698471] Workqueue: events rtl8126_esd_task [r8126]
[   42.698481] RIP: 0010:mdio_real_direct_write_phy_ocp+0x52/0x70 [r8126]
[   42.698487] Code: 00 80 89 b0 b8 00 00 00 bb 20 4e 00 00 eb 05 83 eb 01 74 1a bf c7 10 00 00 e8 1a 8c 71 e6 49 8b 04 24 48 05 b8 00 00 00 8b 00 <85> c0 78 e1 5b 41 5c 5d 31 c0 31 d2 31 f6 31 ff c3 cc cc cc cc 0f
[   42.698489] RSP: 0018:ffffb89d0042bd68 EFLAGS: 00000286
[   42.698490] RAX: 00000000ffffffff RBX: 0000000000001b20 RCX: 0000000000000000
[   42.698492] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[   42.698492] RBP: ffffb89d0042bd78 R08: 0000000000000000 R09: 0000000000000000
[   42.698493] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9a75148409e0
[   42.698494] R13: ffff9a7514840000 R14: ffffffffc05c3d58 R15: 0000000000000004
[   42.698496] FS:  0000000000000000(0000) GS:ffff9a847e480000(0000) knlGS:0000000000000000
[   42.698497] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   42.698498] CR2: 0000000000000000 CR3: 000000045c236002 CR4: 00000000003726f0
[   42.698499] Call Trace:
[   42.698500]  <IRQ>
[   42.698502]  ? show_regs+0x6d/0x80
[   42.698506]  ? watchdog_timer_fn+0x206/0x290
[   42.698509]  ? __pfx_watchdog_timer_fn+0x10/0x10
[   42.698511]  ? __hrtimer_run_queues+0x105/0x280
[   42.698514]  ? clockevents_program_event+0xb3/0x140
[   42.698517]  ? hrtimer_interrupt+0xf6/0x250
[   42.698519]  ? __sysvec_apic_timer_interrupt+0x4e/0x150
[   42.698521]  ? sysvec_apic_timer_interrupt+0x8d/0xd0
[   42.698524]  </IRQ>
[   42.698525]  <TASK>
[   42.698525]  ? asm_sysvec_apic_timer_interrupt+0x1b/0x20
[   42.698529]  ? mdio_real_direct_write_phy_ocp+0x52/0x70 [r8126]
[   42.698535]  ? mdio_real_direct_write_phy_ocp+0x46/0x70 [r8126]
[   42.698541]  rtl8126_set_phy_mcu_ram_code+0x3f/0x70 [r8126]
[   42.698547]  rtl8126_up+0x25af/0x2600 [r8126]
[   42.698554]  rtl8126_esd_task+0x723/0x7d0 [r8126]
[   42.698561]  process_one_work+0x16a/0x350
[   42.698564]  worker_thread+0x306/0x440
[   42.698566]  ? __pfx_worker_thread+0x10/0x10
[   42.698568]  kthread+0xef/0x120
[   42.698570]  ? __pfx_kthread+0x10/0x10
[   42.698572]  ret_from_fork+0x44/0x70
[   42.698574]  ? __pfx_kthread+0x10/0x10
[   42.698575]  ret_from_fork_asm+0x1b/0x30
[   42.698578]  </TASK>
[   70.698274] watchdog: BUG: soft lockup - CPU#1 stuck for 51s! [kworker/1:2:643]
[   70.698279] Modules linked in: veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter scsi_transport_iscsi nf_tables bonding tls bluetooth ecdh_generic ecc softdog msr sunrpc nfnetlink_log binfmt_misc nfnetlink intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 jc42 mei_hdcp mei_pxp kvm snd_hda_intel snd_intel_dspcfg crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 snd_intel_sdw_acpi sha1_ssse3 aesni_intel crypto_simd cryptd drm_buddy snd_hda_codec rapl snd_hda_core cmdlinepart intel_wmi_thunderbolt spi_nor wmi_bmof mtd ee1004 snd_hwdep pcspkr intel_cstate gigabyte_wmi mei_me ttm snd_pcm mei drm_display_helper intel_pmc_core snd_timer intel_vsec joydev snd cec vgastate pmt_telemetry input_leds soundcore fb_ddc rc_core intel_pch_thermal ie31200_edac pmt_class acpi_pad mac_hid zfs(PO) spl(O) vhost_net vhost vhost_iotlb tap
[   70.698321]  vfio_pci vfio_pci_core irqbypass vfio_iommu_type1 vfio iommufd efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq hid_generic usbkbd usbmouse usbhid hid dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c nvme xhci_pci spi_intel_pci xhci_pci_renesas igb crc32_pclmul ahci i2c_i801 e1000e spi_intel i2c_algo_bit i2c_smbus libahci nvme_core r8126(OE) xhci_hcd nvme_auth dca video wmi pinctrl_cannonlake
[   70.698348] CPU: 1 PID: 643 Comm: kworker/1:2 Tainted: P           OEL     6.8.8-2-pve #1
[   70.698349] Hardware name: Gigabyte Technology Co., Ltd. C246M-WU4/C246M-WU4-CF, BIOS F6 01/18/2022
[   70.698351] Workqueue: events rtl8126_esd_task [r8126]
[   70.698359] RIP: 0010:mdio_real_direct_write_phy_ocp+0x52/0x70 [r8126]
[   70.698366] Code: 00 80 89 b0 b8 00 00 00 bb 20 4e 00 00 eb 05 83 eb 01 74 1a bf c7 10 00 00 e8 1a 8c 71 e6 49 8b 04 24 48 05 b8 00 00 00 8b 00 <85> c0 78 e1 5b 41 5c 5d 31 c0 31 d2 31 f6 31 ff c3 cc cc cc cc 0f
[   70.698367] RSP: 0018:ffffb89d0042bd68 EFLAGS: 00000286
[   70.698369] RAX: 00000000ffffffff RBX: 000000000000446e RCX: 0000000000000000
[   70.698370] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[   70.698370] RBP: ffffb89d0042bd78 R08: 0000000000000000 R09: 0000000000000000
[   70.698371] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9a75148409e0
[   70.698372] R13: ffff9a7514840000 R14: ffffffffc05c3d58 R15: 0000000000000004
[   70.698373] FS:  0000000000000000(0000) GS:ffff9a847e480000(0000) knlGS:0000000000000000
[   70.698374] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   70.698375] CR2: 0000000000000000 CR3: 000000045c236002 CR4: 00000000003726f0
[   70.698377] Call Trace:
[   70.698378]  <IRQ>
[   70.698379]  ? show_regs+0x6d/0x80
[   70.698383]  ? watchdog_timer_fn+0x206/0x290
[   70.698386]  ? __pfx_watchdog_timer_fn+0x10/0x10
[   70.698388]  ? __hrtimer_run_queues+0x105/0x280
[   70.698390]  ? clockevents_program_event+0xb3/0x140
[   70.698393]  ? hrtimer_interrupt+0xf6/0x250
[   70.698395]  ? __sysvec_apic_timer_interrupt+0x4e/0x150
[   70.698398]  ? sysvec_apic_timer_interrupt+0x8d/0xd0
[   70.698400]  </IRQ>
[   70.698401]  <TASK>
[   70.698402]  ? asm_sysvec_apic_timer_interrupt+0x1b/0x20
[   70.698406]  ? mdio_real_direct_write_phy_ocp+0x52/0x70 [r8126]
[   70.698412]  ? mdio_real_direct_write_phy_ocp+0x46/0x70 [r8126]
[   70.698418]  rtl8126_set_phy_mcu_ram_code+0x3f/0x70 [r8126]
[   70.698424]  rtl8126_up+0x25af/0x2600 [r8126]
[   70.698430]  rtl8126_esd_task+0x723/0x7d0 [r8126]
[   70.698437]  process_one_work+0x16a/0x350
[   70.698440]  worker_thread+0x306/0x440
[   70.698442]  ? __pfx_worker_thread+0x10/0x10
[   70.698444]  kthread+0xef/0x120
[   70.698447]  ? __pfx_kthread+0x10/0x10
[   70.698448]  ret_from_fork+0x44/0x70
[   70.698450]  ? __pfx_kthread+0x10/0x10
[   70.698452]  ret_from_fork_asm+0x1b/0x30
[   70.698455]  </TASK>
 
Ouch, that's not a good sign.

Have you contacted Realtek support about the driver problems (and this kernel error)?
 
Did you ever get this working ?

I have RTL8126, I got it working it on 6.5.13-6-pve .

Problem is that it negotiates 5Gbs, but only delivers 2
 
Let me give that a try

I was able to get a big speed increase by changing kernel versions on one side > 6.10, and getting rid of the downloaded driver

Presumably that's going to be a while off in proxmox, though
 
I installed the DKMS - Cheers for that

It's telling me proxmox had the same driver - So it is what it is - At least I wont have to remember

To be honest - I've had kernel issues anyway - So I probably wont change until 6.10

I'll probably be dead by the time that happens
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!