diff options
| author |   Aya Levin <ayal@nvidia.com> | 2021-10-11 17:19:23 +0300 |
|---|---|---|
| committer |   Saeed Mahameed <saeedm@nvidia.com> | 2021-10-25 13:51:19 -0700 |
| commit | b87ef75cb5c98a16a7b8e01765277890a6a175cd (patch) | |
| tree | 49ea81ae8e33930f8b83a108e6a71c7bece04654 /Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst | |
| parent | net/mlx5: Extend health buffer dump (diff) | |
| download | linux-dev-b87ef75cb5c98a16a7b8e01765277890a6a175cd.tar.xz linux-dev-b87ef75cb5c98a16a7b8e01765277890a6a175cd.zip | |
net/mlx5: Print health buffer by log level
Add log macro which gets log level as a parameter. Use the severity
read from the health buffer and the new log macro to log the health buffer
with severity as log level. Prior to this patch, health buffer was
printed in error log level regardless of its severity. Now the user may
filter dmesg (--level) or change kernel log level to focus on different
severity levels of firmware errors.
Signed-off-by: Aya Levin <ayal@nvidia.com>
Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to '')
| -rw-r--r-- | Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst b/Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst index 4b59cf2c599f..2ee74a49be9d 100644 --- a/Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst +++ b/Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst @@ -543,6 +543,8 @@ The CR-space dump uses vsc interface which is valid even if the FW command interface is not functional, which is the case in most FW fatal errors. The recover function runs recover flow which reloads the driver and triggers fw reset if needed. +On firmware error, the health buffer is dumped into the dmesg. The log +level is derived from the error's severity (given in health buffer). User commands examples: |