From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1701] Mismatch in packet length causing ACC00 Firmware crash.
Date: Mon, 28 Apr 2025 06:02:03 +0000 [thread overview]
Message-ID: <bug-1701-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1701
Bug ID: 1701
Summary: Mismatch in packet length causing ACC00 Firmware
crash.
Product: DPDK
Version: 23.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: billjose.sibi@vvdntech.in
Target Milestone: ---
Apr 25 18:09:45 gnb0[132190]: HARQ input size is too small 0 < 256
Apr 25 18:09:45 gnb0[132190]: LDPC decoder validation rejected
Apr 25 18:09:45 gnb0[132190]: Enqueue Status: RTE_BBDEV_ENQ_STATUS_INVALID_OP
0x3
Apr 25 18:09:45 gnb0[132190]: HARQ input size is too small 0 < 256
Apr 25 18:09:45 gnb0[132190]: LDPC decoder validation rejected
Apr 25 18:09:45 gnb0[132190]: Enqueue Status: RTE_BBDEV_ENQ_STATUS_INVALID_OP
0x4
Apr 25 18:09:45 gnb0[132190]: HARQ input size is too small 0 < 256
Once we get this bufg, ACC100 firware gets crashed. How to avoid this from
happening.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3039 bytes --]
reply other threads:[~2025-04-28 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1701-3@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).