From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: ICR0: malicious programming detected in dpdk application
Date: Fri, 21 Oct 2022 07:33:21 +0000 [thread overview]
Message-ID: <PSAPR04MB55167F29F6F7F3E881C82020D62D9@PSAPR04MB5516.apcprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Hi All,
While running our dpdk application we are facing below driver error.
It occurred in long run with high traffic.
i40e_dev_alarm_handler(): ICR0: malicious programming detected
i40e_handle_mdd_event(): Malicious Driver Detection event 0x02 on TX queue 8 PF number 0x03 VF number 0x00 device 0000:5e:00.3
i40e_handle_mdd_event(): TX driver issue detected on PF.
Recently we have added Packet reassembly feature in our application.
Can anyone help us why we are hitting this error.
Regards,
Bala
[-- Attachment #2: Type: text/html, Size: 5144 bytes --]
reply other threads:[~2022-10-21 7:33 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=PSAPR04MB55167F29F6F7F3E881C82020D62D9@PSAPR04MB5516.apcprd04.prod.outlook.com \
--to=balakrishnan.k1@tatacommunications.com \
--cc=users@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).