From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1722] Kernel crash with WARNING: CPU: 17 PID: 4510 at lib/refcount.c:28 refcount_warn_saturate+0xd8/0xe0
Date: Wed, 11 Jun 2025 11:01:19 +0000 [thread overview]
Message-ID: <bug-1722-3-pxFTVtwSzU@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1722-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1722
Kevin Traynor (ktraynor@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Kevin Traynor (ktraynor@redhat.com) ---
Marking as wontfix as 20.11 is EoL and not clear if issue is kni or kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2719 bytes --]
prev parent reply other threads:[~2025-06-11 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 8:25 bugzilla
2025-06-11 11:01 ` bugzilla [this message]
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=bug-1722-3-pxFTVtwSzU@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).