From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1170] Link status is not correclty updated for E810 NIC (ice driver) on Windows
Date: Tue, 28 Feb 2023 16:52:18 +0000 [thread overview]
Message-ID: <bug-1170-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1170
Bug ID: 1170
Summary: Link status is not correclty updated for E810 NIC (ice
driver) on Windows
Product: DPDK
Version: 22.11
Hardware: All
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: e.houet@deltacast.tv
Target Milestone: ---
Hello,
I have an issue regarding the link status when using a Intel E810 NIC with
DPDK.
I have a simple sample which simply loops, call `rte_eth_link_get` and prints
the result.
When using a E810 NIC, I have the following behaviour :
- At the start of the test, the cable is plugged in;
- I launch the sample, the link is reported as up (as expected)
- I unplug the cable
- The link is still reported as up in the sample (not expected).
- I stop the sample and relaunch it
- The link is reported as down by the sample (as expected)
- I replug the cable
- The link is still reported as down by the sample (not expected).
I looks like, once DPDK is started, the link status of the device is not
correctly updated.
When trying this with an XXV710 (i40e driver), i have no issue.
According to the Overview of Networking Drivers(
https://doc.dpdk.org/guides-21.02/nics/overview.html ), the ice driver is
compatible with "Link Status" and "Link Status Event" functionalities.
-------------------------------------------------------------
Setup:
- DPDK v22.11.1
- DDP : ice-1.3.30.0.pkg.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3681 bytes --]
reply other threads:[~2023-02-28 16:52 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-1170-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).