Driver Logging Levels

Alveo X3522 User Guide (UG1523)

Document ID
UG1523
Release Date
2023-08-25
Revision
1.4 English

For the X3522 net driver, two settings affect the verbosity of log messages appearing in dmesg output and /var/log/messages:

  • The kernel console log level
  • The netif message per network log level.

The kernel console log level controls the overall log message verbosity and can be set with the command dmesg -n or through the /proc/sys/kernel/printk file:

echo 6 > /proc/sys/kernel/printk

Refer to ‘man 2 syslog’ for log levels and Documentation/sysctl/kernel.txt for a description of the values in /proc/sys/kernel/printk.

The netif message level provides additional logging control for a specified interface. These message levels are documented in Documentation/networking/netif-msg.txt. A message will only appear on the terminal console if both the kernel console log level and netif message level requirements are met.

The current netif message level can be viewed using the following command:

ethtool <iface> | grep -A 1 'message level:'
        Current message level: 0x000020f7 (8439)
                               drv probe link ifdown ifup rx_err tx_err hw

Changes to the netif message level can be made with ethtool, either by name:

ethtool -s <iface> msglvl rx_status on

or by bit mask:

ethtool -s <iface> msglvl 0x7fff

The initial setting of the netif msg level for all interfaces is configured using the debug module parameter. For example:

modprobe xilinx_efct debug=0x7fff
ethtool <iface> | grep -A 1 'message level:'
        Current message level: 0x00007fff (32767)
                               drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol