Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve

ManuS · Tuesday at 14:55

Hi,
After upgrade on my test cluster using no-subscription repository, broadcom network card failed to load

Environment:

- Proxmox VE 9.2.21

- No-subscription repository

- Dell XC750-14 CORE

- Broadcom BCM57412 NetXtreme-E 10Gb

- Firmware 236.1.167.0

- Driver bnxt_en

Problem:

After upgrading to kernel 7.0.14-20-pve and rebooting, the management network becomes unavailable.

Observed errors:
bnxt_init_nic err: fffffff3
nic open fail (rc: fffffff3)
NETDEV WATCHDOG: transmit queue timed out

The server retains its network configuration, VLANs, bridges and routes are present, but cannot reach its default gateway.

Troubleshooting:
- Bond members detected
- Interfaces present
- IP configuration intact
- Gateway unreachable
- No configuration changes made

Workaround:
Booting back on kernel 7.0.14-19-pve immediately restores normal operation.

This issue appears to be related to the bnxt_en driver and/or BCM57412 firmware compatibility with kernel 7.0.14-20-pve.

Thank you for your help
Regards

Stoiko Ivanov · Tuesday at 16:02

could you share the journal from a boot where the issue happens, and one where the NICs work?

else - I did not find it right away - but there seems to be a newer firmware version available for the NIC - https://dl.dell.com/FOLDER14995749M/2/Release_user_NX1-20260921.txt
via https://www.dell.com/support/product-details/de-at/product/poweredge-r750xa/drivers
maybe the newer version contains the fix for the issue.

JensF · Tuesday at 16:08

Kernel 7.0.14-20 isn't in the no-sub-repo. You're using the test-repo. Right?

ManuS · Tuesday at 17:05

Thank you for your reply.

Yes, right, I'm using the test repo for this cluster.

I identified the affected and working kernels:

Working kernel:
7.0.14-19-pve (boot 0)

Failing kernel:
7.0.14-20-pve (boot -1)

The issue is fully reproducible:
- booting 7.0.14-20-pve results in network loss
- booting 7.0.14-19-pve immediately restores connectivity

I attached:
- kernel journal from the failing boot (7.0.14-20-pve)
- kernel journal from the working boot (7.0.14-19-pve)
- filtered bnxt_en related messages

Regarding the firmware, the issue was reproduced using firmware version 236.1.167.0. I have not yet updated the firmware, so both tests were performed with the same firmware and identical configuration.

Stoiko Ivanov · Tuesday at 18:08

Hm - the failing boot does not only fail with the NIC - I also see disk-errors in the journal:

Sep 29 13:33:51 proxmox10 kernel: I/O error, dev dm-7, sector 2214873984 op 0x1WRITE) flags 0x8800 phys_seg 1 prio class 2
Sep 29 13:33:51 proxmox10 kernel: I/O error, dev dm-7, sector 2254438784 op 0x0READ) flags 0x0 phys_seg 16 prio class 2
Sep 29 13:33:51 proxmox10 kernel: I/O error, dev dm-7, sector 2238660344 op 0x0READ) flags 0x0 phys_seg 4 prio class 2
Sep 29 13:33:51 proxmox10 kernel: I/O error, dev dm-7, sector 2215200952 op 0x1WRITE) flags 0x8800 phys_seg 6 prio class 2
Sep 29 13:33:51 proxmox10 kernel: I/O error, dev dm-7, sector 2216218288 op 0x1WRITE) flags 0x8800 phys_seg 11 prio class 2
Sep 29 13:33:51 proxmox10 kernel: I/O error, dev dm-7, sector 2223398624 op 0x1WRITE) flags 0x8800 phys_seg 3 prio class 2

on a hunch - could you check the BIOS for SR-IOV global and I/OAT DMA - see:
https://pve.proxmox.com/wiki/Roadmap#9.1-known-issues
(the issue was reported with older Dell Servers, but we never could pin it to a certain modell-number or firmware/bios version)

comparing the logs between -20 and -19 shows the following lines which might point to an issue in that area (or iommu) as first substantial deviation:

DMAR: DRHD: handling fault status reg 2

apart from the boot issue with the new kernel - I'd check out if you might have some misconfiguration or a loop in your network:

proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)
proxmox10 kernel: vmbr1: received packet on bond0 with own address as source address (addr:84:16:0c:71:db:30, vlan:1)

ManuS · Wednesday at 09:39

Hello Stoiko,

Thank you for your analysis.
I checked the Dell support site and upgraded the Broadcom BCM57412 firmware to the latest version available from Dell.
After the firmware update, I pinned the previously failing kernel (7.0.14-20-pve) and rebooted the host.

Current result:

- The server successfully boots with 7.0.14-20-pve.
- Network connectivity is fully functional.
- The Proxmox web interface is reachable.
- The bond, bridges and VLAN interfaces are operating normally.
- I no longer observe the loss of connectivity that originally occurred with 7.0.14-20-pve.

Based on this test, it appears that the issue may have been related to the BCM57412 firmware rather than the kernel alone.

I have not yet checked the BIOS settings for SR-IOV global and I/OAT DMA because the firmware update alone resolved the problem, but I can review those settings if you believe it would still be useful.

Regarding the messages about:
"received packet on bond0 with own address as source address"
this is a test cluster and I will investigate the network configuration further to rule out any loop or misconfiguration.

Thank you also for pointing out the DMAR and I/O error messages. Since the system is now operating correctly with kernel 7.0.14-20-pve after the NIC firmware update, I suspect they may have been secondary symptoms, but I will continue monitoring the host and report back if they reappear.

For reference:
- Previously failing kernel: 7.0.14-20-pve
- Working kernel before workaround: 7.0.14-19-pve
- Current status after BCM57412 firmware update: 7.0.14-20-pve working correctly

Thank you for your assistance.
Best regards,
Emmanuel

Stoiko Ivanov · Wednesday at 11:45

ManuS said:
Based on this test, it appears that the issue may have been related to the BCM57412 firmware rather than the kernel alone.

Thanks for confirming this! - gives us a pointer if someone else runs into issues with newer Dell Servers!

ManuS said:
I have not yet checked the BIOS settings for SR-IOV global and I/OAT DMA because the firmware update alone resolved the problem, but I can review those settings if you believe it would still be useful.

If your system runs fine as is - I'd leave it there - but in case a future kernel does not boot cleanly - I'd check those settings

ManuS · Wednesday at 18:04

Stoiko Ivanov said:
Thanks for confirming this! - gives us a pointer if someone else runs into issues with newer Dell Servers!

If your system runs fine as is - I'd leave it there - but in case a future kernel does not boot cleanly - I'd check those settings

Hi,
Sorry I answered too fast.
After upgrading Broadcom firmware, server boot with network up now but after a few minutes network goes down again.

I check in the BIOS for SR-IOV global and I/OAT DMA. Both are Enabled

I can't investigate anymore at this time buit I'll find some time to do it tomorrow.

Thank you again for your help
Regards

daveanderson · Thursday at 00:34

We have had issues with bnxt_en on and off on our hosts (see here: https://forum.proxmox.com/threads/broadcom-bcm57504-100g-bnxt_en-tx-timeout-and-nic-reset-on-proxmox-8-1-5-—-while-bcm57414-25g-works-fine-on-same-host.179837/#post-860714)

For completeness in this thread, our impacted machines are BCM57508 based.

My other test cluster that is intel nic based (x520, x540, x710) is working just fine.

7.0.14-20 is an abject failure on our BCM based hosts that have had issues with some 7.x pve kernels before. Everything devolves into a madness of kernel prints and utter failure to network within 5m max of boot.

Pinned everything on our BCM based hosts back to 7.0.14-19 for now.

-Dave

ManuS · Thursday at 09:21

Thank you Dave, I'll not search anymore, pin kernel 7.0.14-19, and I'll wait for futur kernel release.
Regards

x2on · Thursday at 09:49

Same problem with 2.5GBE PCI-E RTL8125 Chipset.
Pinned to 7.0.14-19 which works fine.

CRCinAU · Thursday at 09:55

ManuS said:
After upgrading Broadcom firmware, server boot with network up now but after a few minutes network goes down again.

For the record, did you install firmware 38.11.70.00 from:
https://www.dell.com/support/produc.../drivers?driverid=F2K1J&driveros=naa&ld=F2K1J

Your logs mention Firmware 236.1.167.0 pre-update.

Annoyingly, from the dell web site - I can't seem to find a link between the two types of version numbers.

Andre_B · Thursday at 13:29

Can confirm the same issue here, adding another data point since we're on a different BCM model (BCM57416, not 57412/57508/57504 like others in this thread).

Environment:

Kernel 7.0.14-20-pve → issue; pinned back to 7.0.14-19-pve → stable
Affected NIC: Broadcom BCM57416 NetXtreme-E Dual-Media 10G RDMA [14e4:16d8], bonded (2x, PCI 01:00.0 / 01:00.1)

Like @daveanderson and others here, the problem was isolated to the Broadcom NICs. Our server also has Mellanox ConnectX-3 Pro and 4x Intel X540-AT2, all of which stayed completely stable on 7.0.14-20-pve — only the bnxt_en bond was affected.

dmesg showed repeated watchdog timeouts on both bond members:

Code:

[Thu Oct  1 11:32:04 2026] bnxt_en 0000:01:00.0 nic1: NETDEV WATCHDOG: CPU: 25: transmit queue 3 timed out 5649 ms
[Thu Oct  1 11:48:57 2026] bnxt_en 0000:01:00.0 nic1: NETDEV WATCHDOG: CPU: 28: transmit queue 0 timed out 5250 ms
[Thu Oct  1 11:55:47 2026] bnxt_en 0000:01:00.0 nic1: NETDEV WATCHDOG: CPU: 0: transmit queue 3 timed out 5709 ms
[Thu Oct  1 11:57:51 2026] bnxt_en 0000:01:00.1 nic2: NETDEV WATCHDOG: CPU: 29: transmit queue 0 timed out 5792 ms

Full NIC list for reference:

Code:

01:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller [14e4:16d8] (rev 01)
01:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller [14e4:16d8] (rev 01)
21:00.0 Ethernet controller [0200]: Mellanox Technologies MT27520 Family [ConnectX-3 Pro] [15b3:1007]
41:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)
41:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)
a1:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)
a1:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)

Bond config attached as screenshot. Pinning to 7.0.14-19-pve resolved it for us, same as everyone else so far.

fabian · Thursday at 13:54

there's https://lore.kernel.org/all/20260819233213.3673149-1-joe@dama.to/ and a few followups that might be relevant - those landed in 7.2.x

ManuS · Thursday at 14:07

CRCinAU said:
For the record, did you install firmware 38.11.70.00 from:
https://www.dell.com/support/produc.../drivers?driverid=F2K1J&driveros=naa&ld=F2K1J

Your logs mention Firmware 236.1.167.0 pre-update.

Annoyingly, from the dell web site - I can't seem to find a link between the two types of version numbers.

Hi,
I didn't send new logs with new firmware, but yes, new firmware installed is 38.11.70.00 downloaded from Dell support web site.
If needed, I can restart my server with kernel 7.0.14-20-pve and send you logs.
Regards

Andre_B · Thursday at 14:15

Thanks for confirming! To clarify — when you say it landed in 7.2.x, do you mean upstream Linux 7.2, or is there already a timeline for when a Proxmox kernel build containing this fix (opt-in or otherwise) will be available? I couldn't find an official Proxmox announcement for a 7.2-based kernel yet, just community speculation referencing Ubuntu's 7.2 kernel release for 26.10.

Dark26 · Thursday at 14:27

Same problem here. Everything was working with 7.0.14-19, but not with 7.0.14-20.
Dell serveur with BCM57414 with Firmware 233.1.135.7

Stoiko Ivanov · Thursday at 14:33

Andre_B said:
dmesg showed repeated watchdog timeouts on both bond members:

Dark26 said:
Same problem here. Everything was working with 7.0.14-19, but not with 7.0.14-20.

could you (and others affected):
* share the journal from booting up the machine until the issue occurred
* try disabling some offloading functionality: `ethtool -K <nic> rx-gro-hw off lro off`

showiproute · Thursday at 14:40

Also having those trouble on a Supermicro H12SSL mainboard with a Broadcom BCM57416 NetXtreme NIC.
Booting with an older kernel works.

Dark26 · Thursday at 14:47

some logs

Code:

2026-10-01T14:03:37.449165+02:00 prabackservername01 kernel: bnxt_en 0000:14:00.0 nic0: NIC Link is servername, 25000 Mbps (NRZ) full dservernamelex, Flow control: none
2026-10-01T14:03:37.449179+02:00 prabackservername01 kernel: bnxt_en 0000:14:00.0 nic0: FEC autoneg off encoding: Clause 74 BaseR
2026-10-01T14:03:37.459140+02:00 prabackservername01 kernel: bond1: (slave nic0): Enslaving as a backservername interface with an servername link
2026-10-01T14:03:37.531170+02:00 prabackservername01 kernel: bnxt_en 0000:14:00.1 nic1: NIC Link is servername, 25000 Mbps (NRZ) full dservernamelex, Flow control: none
2026-10-01T14:03:37.531184+02:00 prabackservername01 kernel: bnxt_en 0000:14:00.1 nic1: FEC autoneg off encoding: Clause 74 BaseR
2026-10-01T14:03:37.538141+02:00 prabackservername01 kernel: bond1: (slave nic1): Enslaving as a backservername interface with an servername link
2026-10-01T14:03:37.540068+02:00 prabackservername01 kernel: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
2026-10-01T14:03:37.564135+02:00 prabackservername01 kernel: 8021q: 802.1Q VLAN Sservernameport v1.8
2026-10-01T14:03:37.564149+02:00 prabackservername01 kernel: 8021q: adding VLAN 0 to HW filter on device bond1
2026-10-01T14:03:37.641181+02:00 prabackservername01 kernel: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
2026-10-01T14:03:37.641193+02:00 prabackservername01 kernel: bond1: (slave nic0): link status definitely servername, 25000 Mbps full dservernamelex
2026-10-01T14:03:37.641194+02:00 prabackservername01 kernel: bond1: active interface servername!
2026-10-01T14:03:38.369193+02:00 prabackservername01 kernel: bond1: (slave nic1): link status definitely servername, 25000 Mbps full dservernamelex
2026-10-01T14:03:39.608711+02:00 prabackservername01 kernel: DMAR: DRHD: handling fault status reg 2

2026-10-01T14:03:39.608726+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Fatal firmware reset event, data1: 0x201, data2: 0xda27, min wait 1300 ms, max wait 4200 ms
2026-10-01T14:03:39.608728+02:00 servername kernel: DMAR: [DMA Read NO_PASID] Request device [14:00.0] fault addr 0xf70dc000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear
2026-10-01T14:03:39.617129+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms

2026-10-01T14:03:41.097148+02:00 servername kernel: bond1: (slave nic1): link status definitely up, 25000 Mbps full duplex
2026-10-01T14:03:41.529154+02:00 servername kernel: bnxt_en 0000:14:00.0 nic0: Abandoning msg {0x23 0xe8} len: 0 due to firmware status: 0x2000001
2026-10-01T14:03:42.553136+02:00 servername kernel: bnxt_en 0000:14:00.0 nic0: Abandoning msg {0x23 0xeb} len: 0 due to firmware status: 0x2000001
2026-10-01T14:03:43.577150+02:00 servername kernel: bnxt_en 0000:14:00.0 nic0: Abandoning msg {0x23 0xee} len: 0 due to firmware status: 0x2000001

2026-10-01T14:04:43.545183+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x23 0x272} len: 0 due to firmware status: 0x2000001
2026-10-01T14:04:44.569196+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x23 0x275} len: 0 due to firmware status: 0x2000001
2026-10-01T14:04:45.593187+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x23 0x278} len: 0 due to firmware status: 0x2000001
2026-10-01T14:04:46.617192+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x23 0x27b} len: 0 due to firmware status: 0x2000001
2026-10-01T14:04:47.641142+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x23 0x27e} len: 0 due to firmware status: 0x2000001
2026-10-01T14:04:48.665184+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x23 0x281} len: 0 due to firmware status: 0x2000001

2026-10-01T14:05:02.684219+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [10]: rx{fw_ring: 252 prod: 20c} rx_agg{fw_ring: 268 agg_prod: 7fd sw_agg_prod: 7fd}
2026-10-01T14:05:02.684233+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [10]: cp{fw_ring: 319 raw_cons: 59}
2026-10-01T14:05:02.684233+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [11.0]: tx{fw_ring: 181 prod: 101 cons: f9}
2026-10-01T14:05:02.684235+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [11]: rx{fw_ring: 253 prod: 236} rx_agg{fw_ring: 269 agg_prod: 7ff sw_agg_prod: 7ff}
2026-10-01T14:05:02.684237+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [11]: cp{fw_ring: 320 raw_cons: c5}
2026-10-01T14:05:02.685290+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [12.0]: tx{fw_ring: 182 prod: 156 cons: 154}
2026-10-01T14:05:02.685306+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [12]: rx{fw_ring: 254 prod: 25a} rx_agg{fw_ring: 270 agg_prod: 7ff sw_agg_prod: 7ff}
2026-10-01T14:05:02.685308+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [12]: cp{fw_ring: 321 raw_cons: 125}
2026-10-01T14:05:02.685309+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [13.0]: tx{fw_ring: 183 prod: 322 cons: 322}
2026-10-01T14:05:02.685310+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: [13]: rx{fw_ring: 255 prod: 216} rx_agg{fw_ring: 271 agg_prod: 7fc sw_agg_prod: 7fc}

2026-10-01T14:05:02.691268+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x41 seq id 0x2b7 error 0x3
2026-10-01T14:05:02.691280+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x41 seq id 0x2b8 error 0x3
2026-10-01T14:05:02.691281+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x41 seq id 0x2b9 error 0x3

2026-10-01T14:05:02.710154+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Resp cmpl intr abandoning msg: 0x51 due to firmware status: 0x2000001
2026-10-01T14:05:02.711297+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 2 failed. rc:fffffff0 err:3
2026-10-01T14:05:02.711305+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Resp cmpl intr abandoning msg: 0x51 due to firmware status: 0x2000001
2026-10-01T14:05:02.711306+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 2 failed. rc:fffffff0 err:3
2026-10-01T14:05:02.711306+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Resp cmpl intr abandoning msg: 0x51 due to firmware status: 0x2000001

2026-10-01T14:05:02.717186+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 0 failed. rc:fffffff3 err:3
2026-10-01T14:05:02.718261+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x51 seq id 0x2fc error 0x3
2026-10-01T14:05:02.718269+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 0 failed. rc:fffffff3 err:3
2026-10-01T14:05:02.718270+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x51 seq id 0x2fd error 0x3
2026-10-01T14:05:02.718270+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 0 failed. rc:fffffff3 err:3
2026-10-01T14:05:02.718271+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x51 seq id 0x2fe error 0x3
2026-10-01T14:05:02.718271+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 0 failed. rc:fffffff3 err:3
2026-10-01T14:05:02.718272+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0x51 seq id 0x2ff error 0x3
2026-10-01T14:05:02.719121+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm_ring_free type 0 failed. rc:fffffff3 err:3

2026-10-01T14:05:02.723124+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0xb1 seq id 0x31c error 0x3
2026-10-01T14:05:02.723125+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0xb1 seq id 0x31d error 0x3
2026-10-01T14:05:02.723125+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0xb1 seq id 0x31e error 0x3
2026-10-01T14:05:02.723125+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0xb1 seq id 0x31f error 0x3
2026-10-01T14:05:02.746128+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.749126+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.751122+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.754122+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.757121+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.760121+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.762118+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.765129+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.768119+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.768128+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm req_type 0xb0 seq id 0x320 error 0x3
2026-10-01T14:05:02.768129+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: hwrm stat ctx alloc failure rc: fffffff3
2026-10-01T14:05:02.768132+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: bnxt_init_nic err: fffffff3
2026-10-01T14:05:02.771119+02:00 servername kernel: bond1: (slave nic1): link status down for interface, disabling it in 400 ms
2026-10-01T14:05:02.778113+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: nic open fail (rc: fffffff3)
2026-10-01T14:05:02.781124+02:00 servername kernel: bnxt_en 0000:14:00.1 nic1: Abandoning msg {0x20 0x321} len: 0 due to firmware status: 0x2000001
2026-10-01T14:05:03.201123+02:00 servername kernel: bond1: (slave nic1): link status definitely down, disabling slave
2026-10-01T14:05:03.201131+02:00 servername kernel: bond1: now running without any active interface!

Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve

New Member

Proxmox Staff Member

Renowned Member

New Member

Attachments

Proxmox Staff Member

New Member

Proxmox Staff Member

New Member

New Member

New Member

New Member

Renowned Member

New Member

Attachments

Proxmox Staff Member

New Member

New Member

Renowned Member

Proxmox Staff Member

Renowned Member

Renowned Member

We value your privacy