qfle3 log messages contain unintended additional empty or blank lines.
/var/run/log/vmkernel.log
In(182) vmkernel: cpu40:2097517)qfle3: qfle3_queue_alloc_with_attr:654: [vmnic1] Feature LRO requested.In(182) vmkernel: In(182) vmkernel: cpu40:2097517)qfle3: qfle3_remove_queue_filter:2392: [vmnic1] Removing s/w-only filterIn(182) vmkernel: In(182) vmkernel: cpu65:2097517)qfle3: qfle3_queue_alloc_with_attr:654: [vmnic1] Feature LRO requested.In(182) vmkernel: In(182) vmkernel: cpu65:2097517)qfle3: qfle3_remove_queue_filter:2392: [vmnic1] Removing s/w-only filterIn(182) vmkernel: In(182) vmkernel: cpu40:2097517)qfle3: qfle3_queue_alloc_with_attr:654: [vmnic0] Feature LRO requested.In(182) vmkernel: In(182) vmkernel: cpu40:2097517)qfle3: qfle3_remove_queue_filter:2392: [vmnic0] Removing s/w-only filterIn(182) vmkernel:
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
qfle3 driver inserts an additional newline (\n) character into log messages, creating empty lines in the log output.
This behavior is cosmetic and does not impact the driver’s functionality or network operations.
This issue impacts qfle3 driver version 1.4.51.0 and earlier.
Broadcom and Marvell are aware of the problem, and Marvell—the development partner for the qfle3 driver—has scheduled a fix for version 1.4.60.0.