From: Jakub Kicinski <kuba@kernel.org>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
saeedm@nvidia.com
Subject: Re: [mlx5e] FYI dmesg is filled with mlx5e_page_release_fragmented.isra warnings in 6.6.12
Date: Thu, 18 Jan 2024 08:21:50 -0800 [thread overview]
Message-ID: <20240118082150.53a4d4b9@kernel.org> (raw)
In-Reply-To: <CAA85sZtZ9cL4g-SFSS-pTL11JocoOc4BAU7b4uj26MNckp41wQ@mail.gmail.com>
On Thu, 18 Jan 2024 16:27:13 +0100 Ian Kumlien wrote:
> > [ 1068.937977] WARNING: CPU: 0 PID: 0 at
> > include/net/page_pool/helpers.h:130
> > mlx5e_page_release_fragmented.isra.0+0x46/0x50 [mlx5_core]
Is this one time or repeating / reproducible?
What's the most recent kernel that did work?
next prev parent reply other threads:[~2024-01-18 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 15:08 [mlx5e] FYI dmesg is filled with mlx5e_page_release_fragmented.isra warnings in 6.6.12 Ian Kumlien
2024-01-18 15:27 ` Ian Kumlien
2024-01-18 16:21 ` Jakub Kicinski [this message]
2024-01-18 20:56 ` Ian Kumlien
2024-01-18 16:22 ` Dragos Tatulea
2024-01-18 20:54 ` Ian Kumlien
2024-01-22 10:11 ` Dragos Tatulea
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=20240118082150.53a4d4b9@kernel.org \
--to=kuba@kernel.org \
--cc=ian.kumlien@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).