Using 5.15.0-1064-bluefield, was able to get the expected outputs below
svc-soc-ver@bu-lab24v-oob:~$ cat /etc/mlnx-release
bf-bundle-3.0.0-95_25.04_ubuntu-22.04_dev
svc-soc-ver@bu-lab24v-oob:~$ uname -r
5.15.0-1064-bluefield
svc-soc-ver@bu-lab24v-oob:~$ sudo ethtool oob_net0
Settings for oob_net0:
Supported ports: [ TP MII ]
Supported link modes: 1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
master-slave cfg: preferred slave
master-slave status: slave
Port: Twisted Pair
PHYAD: 3
Transceiver: external
MDI-X: Unknown
Current message level: 0x000000e4 (228)
link ifup rx_err tx_err
Link detected: yes
svc-soc-ver@bu-lab24v-oob:~$ sudo ethtool -s oob_net0 msglvl 0x020
svc-soc-ver@bu-lab24v-oob:~$ sudo ethtool oob_net0 | grep 'Current message
level'
Current message level: 0x00000020 (32)
link
svc-soc-ver@bu-lab24v-oob:~$ sudo dmesg | grep mlxbf_gige
[ 10.775003] mlxbf_gige MLNXBF17:00 oob_net0: renamed from eth0
[ 28.973855] mlxbf_gige MLNXBF17:00: open: start state tx_ci=0x0 tx_pi=0x0
rx_ci=0x0 rx_pi=0x0 int_mask=0x1
[ 28.973872] mlxbf_gige MLNXBF17:00: din_drop=0x0 rx_dma=0x4000000
rx_fifo=0x0 rx_polarity=0
[ 28.975294] mlxbf_gige MLNXBF17:00: open: after phy_start tx_ci=0x0
tx_pi=0x0 rx_ci=0x0 rx_pi=0x0 int_mask=0x1
[ 28.975305] mlxbf_gige MLNXBF17:00: din_drop=0x0 rx_dma=0x4000000
rx_fifo=0x0 rx_polarity=0
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2101193
Title:
mlxbf_gige: msglvl infrastructure
Status in linux-bluefield package in Ubuntu:
Triaged
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
SRU Justification:
[Impact]
The mlxbf_gige driver does not utilize the msglvl infrastructure, so
there is no way to dynamically enable/disable certain debug log entries
from the driver.
[Fix]
The fix is to add logic for setting a default msglvl, providing support
for get/set of msglvl via ethtool, and updating certain driver paths
with netif_msg_XXX checks before logging of driver internals.
The driver currently supports the following msglvl settings:
link 0x004 (set by default)
ifup 0x020 (set by default)
rx_status 0x800
rx_err 0x040 (set by default)
tx_err 0x080 (set by default)
tx_done 0x400
tx_queued 0x100
[Test Case]
Boot BF2/BF3 with mlxbf_gige driver containing this patch
Verify "ethtool oob_net0" shows default msglvl in output
e.g. "Current message level: 0x000000e4 (228)
link ifup rx_err tx_err"
Verify that dmesg output shows log entries from driver, e.g.
mlxbf_gige MLNXBF17:00: open: start state tx_ci=0x0 tx_pi=0x0 rx_ci=0x0
rx_pi=0x0 int_mask=0x1
mlxbf_gige MLNXBF17:00: din_drop=0x0 rx_dma=0x4000000 rx_fifo=0x0
rx_polarity=0
Verify that setting new value via "ethtool -s oob_net0 msglvl <value>"
is reflected in output of "ethtool oob_net0"
Verify driver is fully functional after enabling various msglvl settings
[Regression Potential]
Since this is a debug feature that adds to kernel log, there is
potential for causing regression (e.g. spamming log) if the
msglvl is not set appropriately during certain test cases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2101193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
