[SRU][J:linux-bluefield][PATCH v1 0/1] mlxbf_gige: dont log RX errors by default
David Thompson
davthompson at nvidia.com
Fri Jan 9 20:39:33 UTC 2026
BugLink: https://bugs.launchpad.net/bugs/2138128
SRU Justification:
[Impact]
During certain reset flows, the BF3 kernel log shows instances of this MAC receive error:
mlxbf_gige MLNXBF17:00: rx_mac_error tx_ci=0x0 tx_pi=0x0 rx_ci=0x1 rx_pi=0x80 int_mask=0x1
This log shows that a packet was received with a MAC error, and this packet was dropped.
While everything is handled OK, this event should not be placed into dmesg log by default.
[Fix]
The initial "enable" value of the mlxbf_gige msglvl infrastructure logic
includes the value for NETIF_MSG_RX_ERR. The fix is to change the initial
value, removing NETIF_MSG_RX_ERR, and preventing any logging based on this
type of RX error. Instead, the driver has a counter tracking this type of
RX error and its value can be displayed via "ethtool -S oob_net0"
[Test Case]
* Exercise reboot, power cycle, and FW reset flows of BF3
* Verify no instances of "rx_mac_error" log entries in the dmesg output
[Regression Potential]
None
David Thompson (1):
UBUNTU: SAUCE: mlxbf_gige: dont log RX errors by default
drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
2.43.0
More information about the kernel-team
mailing list