DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1444] DMAR error in kernel caused FlexRAN retarted
Date: Mon, 20 May 2024 03:09:17 +0000	[thread overview]
Message-ID: <bug-1444-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1444

            Bug ID: 1444
           Summary: DMAR error in kernel caused FlexRAN retarted
           Product: DPDK
           Version: 22.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: juoren_wang@pegatroncorp.com
  Target Milestone: ---

Hi sir,

Our gNB running FlexRAN on pod but sometimes will got DMAR error in kernel, it
will caused it stop and restartrd, we don't know what happened in DPDK? could
you please help/suggest the direction to check what is means for and probably
caused?

Test environment
1) OS : WRCP 22.12 patch4 (StarlingX Debian 5.10.177.1.stx.73)
2) DPDK : 22.11.6
2) NIC : Intel E823 (intel ice-d CPU built-in NIC)
3) NIC : Device id (pf/vf): 8086:188c / 8086:1889
4) Accelerator: Intel Acc100 
5) Used Kernel driver and F/W version
Driver version: 1.10.1.2 (ice)
firmware-version: 3.26

--Syslog-----------------------------------------------------------------------
2024-03-14T15:10:59.004 controller-0 kernel: err [283403.137190] DMAR: [DMA
Read] Request device [89:01.2] PASID ffffffff fault addr 280103000 [fault
reason 06] PTE Read access is not set
2024-03-14T15:10:59.004 controller-0 kernel: err [283403.137199] DMAR: DRHD:
handling fault status reg 2
2024-03-14T15:10:59.004 controller-0 kernel: err [283403.137201] DMAR: [DMA
Read] Request device [89:01.2] PASID ffffffff fault addr 28010a000 [fault
reason 06] PTE Read access is not set
2024-03-14T15:10:59.004 controller-0 kernel: err [283403.137206] DMAR: DRHD:
handling fault status reg 3
2024-03-14T15:10:59.004 controller-0 kernel: info [283403.137206] ice
0000:89:00.0: 1 Tx Malicious Driver Detection events detected on PF 0 VF 2 MAC
00:02:01:1a:73:d1.
2024-03-14T15:10:59.004 controller-0 kernel: err [283403.137208] DMAR: [DMA
Read] Request device [89:01.2] PASID ffffffff fault addr 28010b000 [fault
reason 06] PTE Read access is not set
2024-03-14T15:10:59.004 controller-0 kernel: err [283403.137217] DMAR: DRHD:
handling fault status reg 3
--------------------------------------------------------------------------- 

Thank you
Best Regards,
Juoren

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 4273 bytes --]

                 reply	other threads:[~2024-05-20  3:09 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-1444-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).