Firmware Dump or bnxnet3 dump Indication in VMware Logs

Products

• VMware vSphere ESXi 8.0

Issue/Introduction

Firmware dump messages may be found in VMware kernel logs of the ESXI.

Sample snippets:

2025-07-29T07:14:07.471Z In(182) vmkernel: cpu124:4716322)bnxtnet: dev_print_fw_data:123: [vmnic2 : 0x4527b0392000] == START OF TRACE ==
2025-07-29T07:14:07Z In(182) vmkernel:
2025-07-29T07:14:07Z In(182) vmkernel: ommon_util: Port 0 link down
2025-07-29T07:14:07Z In(182) vmkernel: 75252.051:D:common_util: Port 2 link down
2025-07-29T07:14:07Z In(182) vmkernel: 75252.051:D:common_util: Port 3 link down

or

2019-04-18T15:17:41.445Z cpu14:3171839)WARNING: bnxtnet: dev_dump_fw_trace:123: [vmnic3 : 0x4501d2b08000] Dumping FW Trace:
2019-04-18T15:17:41.445Z cpu14:3171839)WARNING: bnxtnet: dev_print_fw_data:94: [vmnic3 : 0x4501d2b08000] == START OF TRACE ==
cfg, pf 0
4939.6:invalid vf res strat, pf 0
4939.6:invalid dyn min cfg, pf 1
4939.6:invalid dyn max cfg, pf 1
4939.6:invalid msix max cfg, pf 1

less vmkernel.all | grep "== START OF TRACE =="

2025-07-29T07:14:00.930Z In(182) vmkernel: cpu123:4716322)bnxtnet: dev_print_fw_data:123: [vmnic9 : 0x452790bc6000] == START OF TRACE ==
2025-07-29T07:14:01.893Z In(182) vmkernel: cpu125:4716322)bnxtnet: dev_print_fw_data:123: [vmnic8 : 0x452785dda000] == START OF TRACE ==
2025-07-29T07:14:02.795Z In(182) vmkernel: cpu114:4716322)bnxtnet: dev_print_fw_data:123: [vmnic7 : 0x45269afee000] == START OF TRACE ==
2025-07-29T07:14:03.764Z In(182) vmkernel: cpu113:4716322)bnxtnet: dev_print_fw_data:123: [vmnic6 : 0x452690202000] == START OF TRACE ==
2025-07-29T07:14:04.710Z In(182) vmkernel: cpu125:4716322)bnxtnet: dev_print_fw_data:123: [vmnic5 : 0x4526d5416000] == START OF TRACE ==

Environment

vSphere ESXi 7.X

vSphere ESXi 8.X

 

Cause

The "Dumping Firmware Trace" message is a new feature introduced in the Broadcom firmware version 212.0 and later, along with the updated bnxtnet driver.

 

Resolution

These messages do not indicate any failure or issue with the associated Broadcom adapters. They are part of the expected behavior and are intentionally generated to collect firmware information whenever a vm-support bundle is captured.