From: Pushpadant <pushpakjm@gmail.com>
To: users@dpdk.org
Subject: ixgbe driver - Intel nic 15e4 (x553) reporting link "up" even though the link is down (No traffic going through the interface)
Date: Tue, 15 Feb 2022 07:42:50 +0530 [thread overview]
Message-ID: <CAKebXfcnzD97t5xsYLpPqYq5WjdOjZpTO2qeS9NcVe8ZFDQ4EA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
Hi Guys,
Using Dpdk verion : 18.11
Could you please help me figure out why get link status still reports
interface as UP even though the link is Down.
Intel card:
06:00.0 Ethernet controller: Intel Corporation Device 15e4 (rev 11) - X553
06:00.1 Ethernet controller: Intel Corporation Device 15e4 (rev 11) - X553
07:00.0 Ethernet controller: Intel Corporation Device 15e5 (rev 11) - X553
Problem: Even after bringing DOWN the port, get link status still reports
interface UP.
My investigation:
1. in ixgbe/base/ixgbe_type.h i see these being defined. Not sure why its
defined under this following comment /* Placeholder value, pending
official value. */
#define IXGBE_DEV_ID_X550EM_A_1G_T 0x15E4
#define IXGBE_DEV_ID_X550EM_A_1G_T_L 0x15E5
From this detail i can conclude we have support for above nics.
2.
https://doc.dpdk.org/guides-18.11/nics/ixgbe.html#supported-chipsets-and-nics
- This link has supported nics and these above nics are not listed under
this.
3. After putting some debug statement in ixgbe driver the problem seem to
be in base/ixgbe_common.c(ixgbe_check_mac_link_generic() function)
links_orig = IXGBE_READ_REG(hw, IXGBE_LINKS);
links_reg = IXGBE_READ_REG(hw, IXGBE_LINKS);
if (links_orig != links_reg) {
4. I suspect on the resister value used to identify the link status is
messing up.
Could you please provide your input.
Thank you so much for your time.
[-- Attachment #2: Type: text/html, Size: 1783 bytes --]
next reply other threads:[~2022-02-15 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 2:12 Pushpadant [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-14 4:47 Pushpadant
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=CAKebXfcnzD97t5xsYLpPqYq5WjdOjZpTO2qeS9NcVe8ZFDQ4EA@mail.gmail.com \
--to=pushpakjm@gmail.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).