Errors after clean proxmox ve 8.4 install

D

Duke Agility

New Member
Jul 13, 2025
1
0
1
I have recently installed proxmox ve 8.4 on my server and in the install process, but also after, errors have been encountered(no network connection after install).
At shutdown/restart, it is locked for around 5 minutes in this state.
At boot, it is locked for 3 minutes in this state.
At the same time, there's this.
And when it has finally started and can login, after every startup, the networking service is stopped and has to be manually started.
And for who is looking at this and needs more, here is the full log of a restart.

I have apt update and apt upgrade, but to no avail. What should I do?
 
There are some issues with your network card
log excerpt 1
Code: 
Jul 13 19:19:48 pve kernel: CPU: 58 PID: 1109 Comm: (udev-worker) Tainted: P           O       6.8.12-9-pve #1
Jul 13 19:19:48 pve kernel: Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 02/21/2025
Jul 13 19:19:48 pve kernel: RIP: 0010:ib_free_cq+0x109/0x150 [ib_core]
Jul 13 19:19:48 pve kernel: Code: e8 8c 9c 02 00 65 ff 0d dd 57 f1 3e 0f 85 70 ff ff ff 0f 1f 44 00 00 e9 66 ff ff ff 48 8d 7f 50 e8 bc c2 5f cc e9 35 ff ff ff <0f> 0b 31 c0 31 f6 31 ff c3 cc cc cc cc 0f 0b eb 80 44 0f b6 25 a4
Jul 13 19:19:48 pve kernel: RSP: 0018:ffffb6914a4ff600 EFLAGS: 00010202
Jul 13 19:19:48 pve kernel: RAX: 0000000000000002 RBX: 0000000000000001 RCX: 0000000000000000
Jul 13 19:19:48 pve kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9dbd00853400
Jul 13 19:19:48 pve kernel: RBP: ffffb6914a4ff670 R08: 0000000000000000 R09: 0000000000000000
Jul 13 19:19:48 pve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9dcc21400000
Jul 13 19:19:48 pve kernel: R13: ffff9dbcc741ff00 R14: 00000000ffffff92 R15: ffff9dbd0084c000
Jul 13 19:19:48 pve kernel: FS:  0000737b1a5b28c0(0000) GS:ffff9dcbc0100000(0000) knlGS:0000000000000000
Jul 13 19:19:48 pve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 13 19:19:48 pve kernel: CR2: 00007ffe8d255f80 CR3: 000000105899a003 CR4: 00000000007706f0
Jul 13 19:19:48 pve kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 13 19:19:48 pve kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jul 13 19:19:48 pve kernel: PKRU: 55555554
Jul 13 19:19:48 pve kernel: Call Trace:
Jul 13 19:19:48 pve kernel:  <TASK>
Jul 13 19:19:48 pve kernel:  ? show_regs+0x6d/0x80
Jul 13 19:19:48 pve kernel:  ? __warn+0x89/0x160
Jul 13 19:19:48 pve kernel:  ? ib_free_cq+0x109/0x150 [ib_core]
Jul 13 19:19:48 pve kernel:  ? report_bug+0x17e/0x1b0
Jul 13 19:19:48 pve kernel:  ? handle_bug+0x6e/0xb0
Jul 13 19:19:48 pve kernel:  ? exc_invalid_op+0x18/0x80
Jul 13 19:19:48 pve kernel:  ? asm_exc_invalid_op+0x1b/0x20
Jul 13 19:19:48 pve kernel:  ? ib_free_cq+0x109/0x150 [ib_core]
Jul 13 19:19:48 pve kernel:  ? ib_mad_init_device+0x54c/0x8a0 [ib_core]
Jul 13 19:19:48 pve kernel:  add_client_context+0x127/0x1c0 [ib_core]
Jul 13 19:19:48 pve kernel:  enable_device_and_get+0xe6/0x1e0 [ib_core]
Jul 13 19:19:48 pve kernel:  ib_register_device+0x506/0x610 [ib_core]
Jul 13 19:19:48 pve kernel:  bnxt_re_probe+0xe95/0x11b0 [bnxt_re]
Jul 13 19:19:48 pve kernel:  ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re]
Jul 13 19:19:48 pve kernel:  auxiliary_bus_probe+0x3e/0xa0
Jul 13 19:19:48 pve kernel:  really_probe+0x1c9/0x430
Jul 13 19:19:48 pve kernel:  __driver_probe_device+0x8c/0x190
Jul 13 19:19:48 pve kernel:  driver_probe_device+0x24/0xd0
Jul 13 19:19:48 pve kernel:  __driver_attach+0x10b/0x210
Jul 13 19:19:48 pve kernel:  ? __pfx___driver_attach+0x10/0x10
Jul 13 19:19:48 pve kernel:  bus_for_each_dev+0x8a/0xf0
Jul 13 19:19:48 pve kernel:  driver_attach+0x1e/0x30
Jul 13 19:19:48 pve kernel:  bus_add_driver+0x14e/0x290
Jul 13 19:19:48 pve kernel:  driver_register+0x5e/0x130
Jul 13 19:19:48 pve kernel:  __auxiliary_driver_register+0x73/0xf0
Jul 13 19:19:48 pve kernel:  ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]
Jul 13 19:19:48 pve kernel:  bnxt_re_mod_init+0x3e/0xff0 [bnxt_re]
Jul 13 19:19:48 pve kernel:  ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]
Jul 13 19:19:48 pve kernel:  do_one_initcall+0x5b/0x340
Jul 13 19:19:48 pve kernel:  do_init_module+0x97/0x290
Jul 13 19:19:48 pve kernel:  load_module+0x213a/0x22a0
Jul 13 19:19:48 pve kernel:  init_module_from_file+0x96/0x100
Jul 13 19:19:48 pve kernel:  ? init_module_from_file+0x96/0x100
Jul 13 19:19:48 pve kernel:  idempotent_init_module+0x11c/0x310
Jul 13 19:19:48 pve kernel:  __x64_sys_finit_module+0x64/0xd0
Jul 13 19:19:48 pve kernel:  x64_sys_call+0x15ed/0x2480
Jul 13 19:19:48 pve kernel:  do_syscall_64+0x81/0x170
Jul 13 19:19:48 pve kernel:  ? do_syscall_64+0x8d/0x170
Jul 13 19:19:48 pve kernel:  ? syscall_exit_to_user_mode+0x86/0x260
Jul 13 19:19:48 pve kernel:  ? do_syscall_64+0x8d/0x170
Jul 13 19:19:48 pve kernel:  ? clear_bhb_loop+0x15/0x70
Jul 13 19:19:48 pve kernel:  ? clear_bhb_loop+0x15/0x70
Jul 13 19:19:48 pve kernel:  ? clear_bhb_loop+0x15/0x70
Jul 13 19:19:48 pve kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Jul 13 19:19:48 pve kernel: RIP: 0033:0x737b1a83d7d9
Jul 13 19:19:48 pve kernel: Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f7 05 0d 00 f7 d8 64 89 01 48
Jul 13 19:19:48 pve kernel: RSP: 002b:00007ffe8d259f28 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Jul 13 19:19:48 pve kernel: RAX: ffffffffffffffda RBX: 00005c5821f295e0 RCX: 0000737b1a83d7d9
Jul 13 19:19:48 pve kernel: RDX: 0000000000000000 RSI: 0000737b1a9d0efd RDI: 000000000000000f
Jul 13 19:19:48 pve kernel: RBP: 0000737b1a9d0efd R08: 0000000000000000 R09: 00005c5821ee4dc0
Jul 13 19:19:48 pve kernel: R10: 000000000000000f R11: 0000000000000246 R12: 0000000000020000
Jul 13 19:19:48 pve kernel: R13: 0000000000000000 R14: 00005c5821f25360 R15: 00007ffe8d25a160
Jul 13 19:19:48 pve kernel:  </TASK>
Jul 13 19:19:48 pve kernel: ---[ end trace 0000000000000000 ]---
Jul 13 19:19:48 pve kernel: bnxt_en 0000:5d:00.0 bnxt_re0: Free MW failed: 0xffffff92

log excerpt 2
Code: 
Jul 13 19:20:12 pve systemd[1]: Startup finished in 4.119s (kernel) + 2min 7.069s (userspace) = 2min 11.189s.
Jul 13 19:20:48 pve pvestatd[1729]: status update time (30.429 seconds)
Jul 13 19:21:06 pve systemd-udevd[1092]: bnxt_en.rdma.0: Worker [1170] processing SEQNUM=6410 killed
Jul 13 19:21:06 pve systemd-udevd[1092]: bnxt_en.rdma.1: Worker [1109] processing SEQNUM=6413 killed
Jul 13 19:21:06 pve systemd-udevd[1092]: bnxt_en.rdma.0: Worker [1170] terminated by signal 9 (KILL).
Jul 13 19:21:31 pve kernel: bnxt_en 0000:5d:00.1: QPLIB: bnxt_re_is_fw_stalled: FW STALL Detected. cmdq[0xe]=0x3 waited (102348 > 100000) msec active 1
Jul 13 19:21:31 pve kernel: bnxt_en 0000:5d:00.1 bnxt_re1: Failed to modify HW QP
Jul 13 19:21:31 pve kernel: infiniband bnxt_re1: Couldn't change QP1 state to INIT: -110
Jul 13 19:21:31 pve kernel: infiniband bnxt_re1: Couldn't start port
Jul 13 19:21:31 pve kernel: bnxt_en 0000:5d:00.1 bnxt_re1: Failed to destroy HW QP
Jul 13 19:21:31 pve kernel: bnxt_en 0000:5d:00.1 bnxt_re1: Free MW failed: 0xffffff92
Jul 13 19:21:31 pve kernel: infiniband bnxt_re1: Couldn't open port 1
Jul 13 19:21:31 pve kernel: infiniband bnxt_re1: Device registered with IB successfully
Jul 13 19:21:31 pve systemd-udevd[1092]: bnxt_en.rdma.1: Worker [1109] terminated by signal 9 (KILL).

Maybe this thread contains some advice: https://forum.proxmox.com/threads/kernel-6-5-11-bug-with-nic-hp-631flr-sfp28.138720/
 
You must log in or register to reply here.
Top Bottom