System hanging after upgrade...NIC driver?

Same problem here with 2 r8169 nics - after upgrading from proxmox 7.4 to proxmox 8 it happens very often that the nics are more or less "offline" even if they sometimes indicate that they have a link.

see also:

- https://bugzilla.kernel.org/show_bug.cgi?id=107421
- https://forum.proxmox.com/threads/networking-issues-pve8.129742/
- https://bugzilla.proxmox.com/show_bug.cgi?id=4807


echo "performance" > /sys/module/pcie_aspm/parameters/policy seem to help "a little bit" but also increase the power consumption a bit.
I'm currently building the pve kernel myself and want to try out a mainline kernel afterwards to see if it changes something.
Has anyone already bisected from which changes the regression comes from? (as it seems to work fine in 5.15er pve kernel).
 
Last edited:
mzac23 said:
Also having a similar issue. Running proxmox on an old Thinkpad laptop with a Realtek 8168 NIC and just upgraded to v8. The system keeps locking up and have to power off and power back on. Real bummer to have this happen every few hours. I can't find anything in any of the system logs and nothing shows up on the console which is also locked up. :(

Edit 1: started getting errors on the console relating to the nic...

View attachment 52113

Edit 2: found a post with a similar issue suggesting to install r8168-dkms but seems this package is not available on pve 8

https://askubuntu.com/questions/140...340-15irh-gaming-wired-networking-not-working

Edit 3: Was able to install r8168-dkms after adding the non-free and non-free-firmware to my apt sources.list. I now see this kernel module. Will update if my system crashes again.

Code: 
root@pve3:~# cat /etc/apt/sources.list
deb http://ftp.ca.debian.org/debian bookworm main contrib non-free non-free-firmware

deb http://ftp.ca.debian.org/debian bookworm-updates main contrib non-free non-free-firmware

# security updates
deb http://security.debian.org bookworm-security main contrib non-free non-free-firmware

deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

Code: 
root@pve3:~# apt install r8168-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  build-essential cpp cpp-12 dkms dpkg-dev fakeroot g++ g++-12 gcc gcc-12 libabsl20220623 libalgorithm-diff-perl libalgorithm-diff-xs-perl
  libalgorithm-merge-perl libaom3 libasan8 libatomic1 libavif15 libc-dev-bin libc-devtools libc6-dev libcc1-0 libcrypt-dev libdav1d6 libde265-0 libdpkg-perl
  libfakeroot libfile-fcntllock-perl libgav1-1 libgcc-12-dev libgd3 libgomp1 libheif1 libisl23 libitm1 liblsan0 libmpc3 libmpfr6 libnsl-dev libquadmath0
  librav1e0 libstdc++-12-dev libsvtav1enc1 libtirpc-dev libtsan2 libubsan1 libx265-199 libxpm4 libyuv0 linux-libc-dev make manpages-dev pve-headers-6.2
  pve-headers-6.2.16-3-pve rpcsvc-proto sudo
Suggested packages:
  cpp-doc gcc-12-locales cpp-12-doc menu debian-keyring g++-multilib g++-12-multilib gcc-12-doc gcc-multilib autoconf automake libtool flex bison gdb gcc-doc
  gcc-12-multilib glibc-doc bzr libgd-tools libstdc++-12-doc make-doc
The following NEW packages will be installed:
  build-essential cpp cpp-12 dkms dpkg-dev fakeroot g++ g++-12 gcc gcc-12 libabsl20220623 libalgorithm-diff-perl libalgorithm-diff-xs-perl
  libalgorithm-merge-perl libaom3 libasan8 libatomic1 libavif15 libc-dev-bin libc-devtools libc6-dev libcc1-0 libcrypt-dev libdav1d6 libde265-0 libdpkg-perl
  libfakeroot libfile-fcntllock-perl libgav1-1 libgcc-12-dev libgd3 libgomp1 libheif1 libisl23 libitm1 liblsan0 libmpc3 libmpfr6 libnsl-dev libquadmath0
  librav1e0 libstdc++-12-dev libsvtav1enc1 libtirpc-dev libtsan2 libubsan1 libx265-199 libxpm4 libyuv0 linux-libc-dev make manpages-dev pve-headers-6.2
  pve-headers-6.2.16-3-pve r8168-dkms rpcsvc-proto sudo
0 upgraded, 57 newly installed, 0 to remove and 0 not upgraded.
Need to get 84.6 MB of archives.
After this operation, 372 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Code: 
root@pve3:~# lsmod | grep 816
r8168                 655360  0
Click to expand...
I tried this. It didn't work. When I run update-initrammfs -k 6.2.16-6-pve -c, The r8168 module does not get built. It adds the r8169.ko. It does however add /etc/modprobe.d/r8168-dkms.conf.

Thanks, Andy

Any ideas?
 
zeha said:
Chiming in here because I have the same problem on 6.2.16-3-pve:

Linux las-vh01 6.2.16-3-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) x86_64 GNU/Linux

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)

Edit: worked just fine on 5.15.104-1-pve.


Code: 
kernel: [36008.072686] ------------[ cut here ]------------
kernel: [36008.072695] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out
kernel: [36008.072712] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
kernel: [36008.072724] Modules linked in: tcp_diag inet_diag veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter scsi_transport_iscsi nf_tables softdog bonding tls sunrpc nfnetlink_log nfnetlink binfmt_misc intel_rapl_msr intel_rapl_common amdgpu edac_mce_amd snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp kvm_amd snd_sof_pci snd_sof_xtensa_dsp iommu_v2 drm_buddy snd_sof snd_hda_codec_realtek gpu_sched mt7921e drm_ttm_helper snd_sof_utils kvm snd_hda_codec_generic ttm mt7921_common snd_hda_codec_hdmi snd_soc_core mt76_connac_lib irqbypass crct10dif_pclmul drm_display_helper snd_compress polyval_clmulni snd_hda_intel polyval_generic ac97_bus mt76 btusb cec snd_pcm_dmaengine ghash_clmulni_intel snd_intel_dspcfg snd_intel_sdw_acpi sha512_ssse3 btrtl snd_hda_codec snd_pci_ps aesni_intel rc_core btbcm snd_rpl_pci_acp6x crypto_simd btintel snd_hda_core asus_nb_wmi eeepc_wmi snd_acp_pci btmtk cryptd mac80211 drm_kms_helper asus_wmi
kernel: [36008.072787]  snd_pci_acp6x snd_hwdep bluetooth snd_pcm ledtrig_audio i2c_algo_bit rapl sparse_keymap ecdh_generic cp210x syscopyarea cfg80211 platform_profile ecc snd_timer sysfillrect pcspkr snd_pci_acp5x wmi_bmof usbserial sysimgblt snd snd_rn_pci_acp3x k10temp snd_acp_config ucsi_acpi soundcore snd_soc_acpi libarc4 ccp snd_pci_acp3x typec_ucsi typec serial_multi_instantiate mac_hid vhost_net vhost vhost_iotlb tap drm efi_pstore dmi_sysfs ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor raid6_pq libcrc32c simplefb xhci_pci nvme xhci_pci_renesas crc32_pclmul ahci i2c_piix4 libahci nvme_core r8169 nvme_common xhci_hcd realtek video wmi
kernel: [36008.072869] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P           O       6.2.16-3-pve #1
kernel: [36008.072875] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN52/PN52, BIOS 11300 06/15/2022
kernel: [36008.072878] RIP: 0010:dev_watchdog+0x23a/0x250
kernel: [36008.072884] Code: 00 e9 2b ff ff ff 48 89 df c6 05 8a 6f 7d 01 01 e8 6b 08 f8 ff 44 89 f1 48 89 de 48 c7 c7 58 64 40 9d 48 89 c2 e8 06 ab 30 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
kernel: [36008.072890] RSP: 0018:ffff9a11c02cce38 EFLAGS: 00010246
kernel: [36008.072894] RAX: 0000000000000000 RBX: ffff8d45543bc000 RCX: 0000000000000000
kernel: [36008.072898] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
kernel: [36008.072901] RBP: ffff9a11c02cce68 R08: 0000000000000000 R09: 0000000000000000
kernel: [36008.072904] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8d45543bc4c8
kernel: [36008.072906] R13: ffff8d45543bc41c R14: 0000000000000000 R15: 0000000000000000
kernel: [36008.072909] FS:  0000000000000000(0000) GS:ffff8d540e700000(0000) knlGS:0000000000000000
kernel: [36008.072913] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: [36008.072916] CR2: 00007f01c75ba000 CR3: 0000000934810000 CR4: 0000000000750ee0
kernel: [36008.072920] PKRU: 55555554
kernel: [36008.072922] Call Trace:
kernel: [36008.072925]  <IRQ>
kernel: [36008.072929]  ? __pfx_dev_watchdog+0x10/0x10
kernel: [36008.072935]  call_timer_fn+0x2c/0x160
kernel: [36008.072940]  ? __pfx_dev_watchdog+0x10/0x10
kernel: [36008.072945]  __run_timers+0x259/0x310
kernel: [36008.072950]  run_timer_softirq+0x1d/0x40
kernel: [36008.072953]  __do_softirq+0xd9/0x346
kernel: [36008.072958]  ? hrtimer_interrupt+0x11f/0x250
kernel: [36008.072963]  __irq_exit_rcu+0xa2/0xd0
kernel: [36008.072968]  irq_exit_rcu+0xe/0x20
kernel: [36008.072972]  sysvec_apic_timer_interrupt+0x92/0xd0
kernel: [36008.072977]  </IRQ>
kernel: [36008.072978]  <TASK>
kernel: [36008.072980]  asm_sysvec_apic_timer_interrupt+0x1b/0x20
kernel: [36008.072984] RIP: 0010:cpuidle_enter_state+0xde/0x6f0
kernel: [36008.072990] Code: 2a 97 63 e8 54 7e 4a ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 82 86 49 ff 80 7d d0 00 0f 85 eb 00 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 12 02 00 00 4d 63 ee 49 83 fd 09 0f 87 c7 04 00 00
kernel: [36008.072995] RSP: 0018:ffff9a11c019fe38 EFLAGS: 00000246
kernel: [36008.072998] RAX: 0000000000000000 RBX: ffff8d45473d5c00 RCX: 0000000000000000
kernel: [36008.073001] RDX: 0000000000000004 RSI: 0000000000000000 RDI: 0000000000000000
kernel: [36008.073004] RBP: ffff9a11c019fe88 R08: 0000000000000000 R09: 0000000000000000
kernel: [36008.073007] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff9ded6600
kernel: [36008.073009] R13: 0000000000000003 R14: 0000000000000003 R15: 000020bfc8617ca1
kernel: [36008.073015]  ? cpuidle_enter_state+0xce/0x6f0
kernel: [36008.073018]  ? sched_clock_local+0x13/0x90
kernel: [36008.073023]  cpuidle_enter+0x2e/0x50
kernel: [36008.073027]  do_idle+0x216/0x2a0
kernel: [36008.073033]  cpu_startup_entry+0x1d/0x20
kernel: [36008.073036]  start_secondary+0x122/0x160
kernel: [36008.073042]  secondary_startup_64_no_verify+0xe5/0xeb
kernel: [36008.073052]  </TASK>
kernel: [36008.073054] ---[ end trace 0000000000000000 ]---
kernel: [36008.101687] r8169 0000:02:00.0 enp2s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
kernel: [36008.102878] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
kernel: [36008.103979] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
kernel: [36008.105116] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
kernel: [36008.106232] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
kernel: [36008.107331] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
kernel: [36008.108476] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
kernel: [36008.128718] r8169 0000:02:00.0 enp2s0: rtl_mac_ocp_e00e_cond == 1 (loop: 10, delay: 1000).
kernel: [36008.129391] r8169 0000:02:00.0 enp2s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
kernel: [36008.129995] r8169 0000:02:00.0 enp2s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
kernel: [36008.130585] r8169 0000:02:00.0 enp2s0: Link is Down
kernel: [36008.130827] vmbr0: port 1(enp2s0) entered disabled state
Click to expand...
Having same issue. How do you start Proxmox 8 with kernel 5.15.104-1?
 
dbenyakar said:
Having same issue. How do you start Proxmox 8 with kernel 5.15.104-1?
Click to expand...
You have to select it from GRUB. When the machine boots, you should see something like "Advanced options for Proxmox VE GNU/Linux". Select that and then the kernel you want.

To make that happen automatically, add a line to /etc/default/grub.d/proxmox-ve.cfg

GRUB_DEFAULT="1>2"

Then run update-grub

To figure out what to put for the GRUB_DEFAULT, grep menuentry /boot/grub.cfg

Code: 
grep menuentry /boot/grub/grub.cfg
if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
  menuentry_id_option=""
export menuentry_id_option
menuentry 'Proxmox VE GNU/Linux' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
submenu 'Advanced options for Proxmox VE GNU/Linux' $menuentry_id_option 'gnulinux-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
    menuentry 'Proxmox VE GNU/Linux, with Linux 6.2.16-6-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.16-6-pve-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
    menuentry 'Proxmox VE GNU/Linux, with Linux 6.2.16-6-pve (recovery mode)' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.16-6-pve-recovery-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
    menuentry 'Proxmox VE GNU/Linux, with Linux 5.15.108-1-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.15.108-1-pve-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {

Note that the "Advanced options" is a submenu. Menus start from 0, so the advanced menu is 1. Under that the 5.108 kernel is entry 2, so the GRUB_DEFAULT is 1>2.

You may be able to use the value from the menuentry_id_option instead. Something like this:

GRUB_DEFAULT="gnulinux-5.15.108-1-pve-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f"

I'm not sure if that works. I vaguely remember it does.

Hope this helps.

Andy
 
AndyHowell said:
You have to select it from GRUB. When the machine boots, you should see something like "Advanced options for Proxmox VE GNU/Linux". Select that and then the kernel you want.

To make that happen automatically, add a line to /etc/default/grub.d/proxmox-ve.cfg

GRUB_DEFAULT="1>2"

Then run update-grub

To figure out what to put for the GRUB_DEFAULT, grep menuentry /boot/grub.cfg

Code: 
grep menuentry /boot/grub/grub.cfg
if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
  menuentry_id_option=""
export menuentry_id_option
menuentry 'Proxmox VE GNU/Linux' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
submenu 'Advanced options for Proxmox VE GNU/Linux' $menuentry_id_option 'gnulinux-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
    menuentry 'Proxmox VE GNU/Linux, with Linux 6.2.16-6-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.16-6-pve-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
    menuentry 'Proxmox VE GNU/Linux, with Linux 6.2.16-6-pve (recovery mode)' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.16-6-pve-recovery-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {
    menuentry 'Proxmox VE GNU/Linux, with Linux 5.15.108-1-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.15.108-1-pve-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f' {

Note that the "Advanced options" is a submenu. Menus start from 0, so the advanced menu is 1. Under that the 5.108 kernel is entry 2, so the GRUB_DEFAULT is 1>2.

You may be able to use the value from the menuentry_id_option instead. Something like this:

GRUB_DEFAULT="gnulinux-5.15.108-1-pve-advanced-7bdbf2de-5c2a-4b5d-9937-803b341d3c2f"

I'm not sure if that works. I vaguely remember it does.

Hope this helps.

Andy
Click to expand...
Thanks Andy. I eventually used 'proxmox-boot-tool kernel pin' to pin a kernel to be the default one at boot.
 
Patric Pesch said:
I had the problem that the r8168 was not used and after installing the drivers no connection was possible at all. The installation of the kernel headers helped:

Code: 
apt install pve-headers

But for this I had to disable the r8168 again, reboot, install the headers, enable drivers and reboot. Quite cumbersome.
I found this solution here: https://forum.proxmox.com/threads/networking-issues-pve8.129742/
Click to expand...
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
 
  • Like
Reactions: cyabai, Jay L, _gabriel and 6 others
dbenyakar said:
How do we know when Proxmox fixes this dug and how they are going to release this fix?
Click to expand...
I'm not sure. However, installing the pve-headers and r8168-dkms resolved the issue for me. See my previous message. r8168-dkms should have a dependency on pve-headers. They are needed to compile r8168-dkms.

Regards, Andy
 
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...
THanks for the advice. I have a fresh install of Promox 8 running a couple of vm's. Each night after several hours, the server and vm's are unreachable. The server appears to be running, but can't connect. A reboot allows me to reconnect. Using the r8169 drivers. Will give this a try.
 
shaywood said:
THanks for the advice. I have a fresh install of Promox 8 running a couple of vm's. Each night after several hours, the server and vm's are unreachable. The server appears to be running, but can't connect. A reboot allows me to reconnect. Using the r8169 drivers. Will give this a try.
Click to expand...
I have the same issue with the r8169 drivers today and reboot helped. I tried what AndyHowell suggested and I will see how it goes.
 
I have encountered the related problem when upgrading from 6 to 7.4.16 with kernel 5.15.116-1-pve.
I have 3 ethernet cards:
Code: 
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
I think the first one is working but not the 2 others, because they are linked to vm no more working.

I have installed pve-kernel-5.15.108-1-pve and boot on it but it doesn't work.
I have installed on the 5.15.116 kernel the pve-headers and r8168-dkms packages but it doesn't work.

Any idea ?
 
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...

I followed your small guide and ask myself if i should go back to original sources.list, afterwards?
 
MisterMue said:
I followed your small guide and ask myself if i should go back to original sources.list, afterwards?
Click to expand...
If you remove the repo component again, than you will not get updates for the dkms package if available. No harm in keeping it.
 
  • Like
Reactions: rRobbie
stefe said:
I have encountered the related problem when upgrading from 6 to 7.4.16 with kernel 5.15.116-1-pve.
I have 3 ethernet cards:
Code: 
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
I think the first one is working but not the 2 others, because they are linked to vm no more working.

I have installed pve-kernel-5.15.108-1-pve and boot on it but it doesn't work.
I have installed on the 5.15.116 kernel the pve-headers and r8168-dkms packages but it doesn't work.

Any idea ?
Click to expand...
My problem is resolved.
During the debian migration, my interfaces were renamed: eth1 => eth2 and eth2 => eth1.
 
  • Like
Reactions: rRobbie
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...
Thanks, hope that stabilizes my Proxmox-V8@DellWyse5070

It did. Runs stable now !!
 
Last edited:
AndyHowell said:
Patric,

Thanks, installing the headers worked. I backed out my changes to default to the 5 series kernel, installed the headers, and rebooted. I didn't have to disable anything. Installing the headers was the magic sauce I needed.

For anyone that finds this later, this is what I did, gleaned from previous messages:

Edit /etc/apt/sources.list
Code: 
deb http://ftp.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# Original
#deb http://ftp.debian.org/debian bookworm main contrib
#deb http://ftp.debian.org/debian bookworm-updates main contrib
#deb http://security.debian.org/debian-security bookworm-security main contrib

Update apt:
apt update

Install the headers:
apt install pve-headers

Install the r8168-dkms driver
apt install r8168-dkms

Reboot. Then check that 8168 driver is installed
Code: 
lsmod|grep 816
r8168                 655360  0
Andy
Click to expand...
I don't quiet understand why trying this a second time just recently seems to have worked. Never the less, thank you Andy! I'm going on 48 hrs of no reboots. Hoping it finally fixed.
 
I also have tried the solution as mentioned above by AndyHowell and it seems to work quite well!

The problem I have now is that the root disk is full because the log files have been spammed continuously. Since it's a small drive, it is causing issues if I do not truncate the syslog and the kernel.log files located in /var/log.

This is what gets logged about every second in the kernel.log (and syslog as well):
Code: 
2023-09-14T23:21:49.251124+02:00 moon kernel: [46793.486973] pcieport 0000:00:1c.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:1c.0
2023-09-14T23:21:49.251134+02:00 moon kernel: [46793.486999] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
2023-09-14T23:21:49.251135+02:00 moon kernel: [46793.487004] pcieport 0000:00:1c.0:   device [8086:a394] error status/mask=00100000/00010000
2023-09-14T23:21:49.251136+02:00 moon kernel: [46793.487007] pcieport 0000:00:1c.0:    [20] UnsupReq               (First)
2023-09-14T23:21:49.251136+02:00 moon kernel: [46793.487009] pcieport 0000:00:1c.0: AER:   TLP Header: 34000000 02000010 00000000 90039003
2023-09-14T23:21:49.251137+02:00 moon kernel: [46793.487016] r8168 0000:02:00.0: AER: can't recover (no error_detected callback)
2023-09-14T23:21:49.251137+02:00 moon kernel: [46793.487031] pcieport 0000:00:1c.0: AER: device recovery failed

I tried adding "pci=noaer" to the grub entry to prevent the spamming of the log files, but it did not have the results I hoped for...

Anyone else noticing this? Or maybe someone has a way to prevent the log spamming?
 
This is how I resolved the network driver issue after upgrading from Proxmox 7 to 8 on a Dell Optiplex 3090. Rolling back to r8168-dkms as others suggested didn't work for me.

Code: 
nano /etc/apt/sources.list

2. Add line
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

Code: 
apt update

apt install pve-kernel-5.15.108-1-pve

proxmox-boot-tool kernel pin 5.15.108-1-pve

reboot

Finally, remove line from step 2 as you don't need it for Proxmox 8.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back