From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1019] Cannot Rx after DPDK 22.03 version with iavf
Date: Fri, 27 May 2022 09:24:41 +0000 [thread overview]
Message-ID: <bug-1019-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1019
Bug ID: 1019
Summary: Cannot Rx after DPDK 22.03 version with iavf
Product: DPDK
Version: 22.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: happygmkim@gmail.com
Target Milestone: ---
Hi,
Sometimes XL710 VF cannot Rx packets when startup with DPDK 22.03.
It have been worked well before DPDK 22.03.
1. Reproduction : Send arp flooding packets in same subnet during DPDK driver
initialization, it happens randomly.
#!/bin/bash
while [ true ]
do
sudo arping -i ethvf -w 0 -B -q
done
Rx stopped after "fault addr 0 [fault reason 05] PTE Write access is not set"
message found.
2. Test environment
1) OS : Ubuntu 18.04
2) NIC : Intel XL710 SRIOV-VF
3) Used Kernel driver and F/W version
Driver version: 2.1.14-k
firmware-version: 7.10 0x800075e6 19.5.12
-> It happened other several other different drivers and F/W versions
3. Syslog
May 23 03:55:32 xx[31168]: EAL: VFIO support initialized
May 23 03:55:32 xx[31168]: EAL: Using IOMMU type 1 (Type 1)
May 23 03:55:32 kernel: vfio-pci 0000:3b:02.3: enabling device (0000 -> 0002)
May 23 03:55:33 xx[31168]: EAL: Probe PCI driver: net_iavf (8086:154c) device:
0000:3b:02.3 (socket 0)
May 23 03:55:33 kernel: vfio-pci 0000:3b:02.4: enabling device (0000 -> 0002)
May 23 03:55:33 xx[31168]: EAL: Probe PCI driver: net_iavf (8086:154c) device:
0000:3b:02.4 (socket 0)
May 23 03:55:33 xx[31168]: TELEMETRY: No legacy callbacks, legacy socket not
created
May 23 03:55:33 xx[31168]: iavf_configure_queues(): RXDID[22] is not supported,
request default RXDID[1] in Queue[0]
May 23 03:55:34 kernel: i40e 0000:3b:00.0: Unprivileged VF 3 is attempting to
configure promiscuous mode
May 23 03:55:34 kernel: i40e 0000:3b:00.0: Unprivileged VF 3 is attempting to
configure promiscuous mode
May 23 03:55:34 xx[31168]: iavf_configure_queues(): RXDID[22] is not supported,
request default RXDID[1] in Queue[0]
May 23 03:55:34 kernel: DMAR: DRHD: handling fault status reg 302
May 23 03:55:34 kernel: DMAR: [DMA Write] Request device [3b:02.4] fault addr 0
[fault reason 05] PTE Write access is not set
May 23 03:55:34 kernel: i40e 0000:3b:00.0: Unprivileged VF 4 is attempting to
configure promiscuous mode
May 23 03:55:34 kernel: DMAR: [DMA Write] Request device [3b:02.4] fault addr 0
[fault reason 05] PTE Write access is not set
May 23 03:55:34 kernel: DMAR: DRHD: handling fault status reg 500
4
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-05-27 9:24 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-1019-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.