From: Jakub Kicinski <kuba@kernel.org>
To: Matthew W Carlis <mattc@purestorage.com>
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com,
mbloch@nvidia.com, ashishk@purestorage.com,
msaggi@purestorage.com, adailey@purestorage.com
Subject: Re: [PATCH 1/1] net/mlx5: query_mcia_reg fail logging at debug severity
Date: Tue, 28 Oct 2025 15:43:30 -0700 [thread overview]
Message-ID: <20251028154330.6705d2da@kernel.org> (raw)
In-Reply-To: <20251028194011.39877-2-mattc@purestorage.com>
On Tue, 28 Oct 2025 13:40:11 -0600 Matthew W Carlis wrote:
> Whenever a user or automation runs ethtool -m <eth> or an equivalent
> to mlx5 device & there is not any SFP module in that device the
> kernel log is spammed with ""query_mcia_reg failed: status:" which
> is really not that informative to the user who already knows that
> their command failed. Since the severity is logged at error severity
> the log message cannot be disabled via dyndbg etc...
+1 from me FWIW. I wonder if we're hitting this on the same class
of systems but recently this started hitting at Meta as well.
Millions of log entries a day because some ports don't have an SFP
plugged in :|
next prev parent reply other threads:[~2025-10-28 22:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 19:40 [PATCH 0/1] net/mlx5: query_mcia_reg fail logging at debug severity Matthew W Carlis
2025-10-28 19:40 ` [PATCH 1/1] " Matthew W Carlis
2025-10-28 20:28 ` Gal Pressman
2025-10-28 21:48 ` Matthew W Carlis
2025-10-29 7:22 ` Gal Pressman
2025-10-28 22:43 ` Jakub Kicinski [this message]
2025-10-29 7:33 ` Gal Pressman
2025-10-29 16:49 ` Matthew W Carlis
2025-10-29 23:33 ` Jakub Kicinski
2025-10-30 14:48 ` Gal Pressman
2025-10-30 20:09 ` Matthew W Carlis
2025-11-02 13:09 ` Gal Pressman
2025-10-28 20:27 ` [PATCH 0/1] " Gal Pressman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251028154330.6705d2da@kernel.org \
--to=kuba@kernel.org \
--cc=adailey@purestorage.com \
--cc=ashishk@purestorage.com \
--cc=mattc@purestorage.com \
--cc=mbloch@nvidia.com \
--cc=msaggi@purestorage.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).