From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1337] [21.11.5] iavf driver stuck in rte_eal_alarm_cancel
Date: Wed, 20 Dec 2023 10:45:57 +0000 [thread overview]
Message-ID: <bug-1337-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1337
Bug ID: 1337
Summary: [21.11.5] iavf driver stuck in rte_eal_alarm_cancel
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: ktraynor@redhat.com
Target Milestone: ---
With iavf device in OVS and dpdk 21.11.5.
OVS main thread is calling rte_eth_dev_configure()...iavf_queues_req_reset()
and is getting stuck in rte_eal_alarm_cancel() waiting for alarms to be
cancelled.
eal-intr-thread is stuck in application callback as it is requesting
reconfiguration and waiting for current configure to be completed in the main
thread.
The issue was introduced with the patch below. There are some related patches
in this area that were not previously backported and newer ones to come.
commit b965aceffdb9dd8d2501314c174716617371d752
Author: Mingjin Ye <mingjinx.ye@intel.com>
Date: Wed Jun 14 09:53:03 2023 +0000
net/iavf: fix abnormal disable HW interrupt
[ upstream commit 675a104e2e940ec476e8b469725e8465d01c0098 ]
For command VIRTCHNL_OP_REQUEST_QUEUES, polling access to the admin
queue has the issue of access overruns after disabling interrupt. That
results in FW disabling HW interrupt for protection purposes.
The updates/changes in this patch:
1. Remove the polling admin queue processing and use the generic interrupt
processing instead.
2. Release redundant queue resource before stopping processing interrupt
events.
Fixes: 22b123a36d07 ("net/avf: initialize PMD")
Fixes: ef807926e148 ("net/iavf: support requesting additional queues from
PF")
Fixes: 84108425054a ("net/iavf: support asynchronous virtual channel
message")
Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4186 bytes --]
reply other threads:[~2023-12-20 10:45 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-1337-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).