DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Beilei Xing <beilei.xing@intel.com>, Qi Zhang <qi.z.zhang@intel.com>
Cc: dev <dev@dpdk.org>, Jean Hsiao <jhsiao@redhat.com>,
	 Christophe Fontaine <cfontain@redhat.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] Link status issue with i40e firmware 7.0x
Date: Thu, 31 Oct 2019 15:32:12 +0100	[thread overview]
Message-ID: <CAJFAV8z7bQ7s+KkPnyn7VR2khFRdTWpxiexsunh-L=1+-b2U=g@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wkf_rYTAfA4RhEF7f4YAJ9QXXvChOg4O8aqPjOSYxvfg@mail.gmail.com>

On Wed, Oct 30, 2019 at 3:20 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Hello,
>
> We recently upgraded a XXV710 nic on a Dell R740 server (running RHEL
> 7.7) to firmware version 7.00.
>
> # ethtool -i enp59s0f0
> driver: i40e
> version: 2.8.10-k
> firmware-version: 7.00 0x80004cf8 1.2154.0
> expansion-rom-version:
> bus-info: 0000:3b:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>
>
> Following this upgrade, using the nic with dpdk only works once.
> Restarting testpmd (dpdk 18.11.2) ends up with all ports reporting
> that link is down, and indeed, the other side of the cable reports
> that there is no light.

More info on reproducing the issue.
From a testpmd with links up:

# all good
testpmd> show port summary all
Number of available ports: 2
Port MAC Address       Name         Driver         Status   Link
0    3C:FD:FE:AD:BF:C4 0000:3b:00.0 net_i40e       up       25000Mbps
1    3C:FD:FE:AD:BF:C5 0000:3b:00.1 net_i40e       up       25000Mbps


# setting one link down
testpmd> set link-down port 0
i40e_phy_conf_link():     Current: abilities 1c, link_speed 4c
i40e_phy_conf_link():     Config:  abilities 24, link_speed 4c
testpmd> i40e_dev_alarm_handler(): ICR0: adminq event

Port 0: link state change event
i40e_dev_alarm_handler(): ICR0: adminq event

testpmd> show port summary all
Number of available ports: 2
Port MAC Address       Name         Driver         Status   Link
0    3C:FD:FE:AD:BF:C4 0000:3b:00.0 net_i40e       down     0Mbps
1    3C:FD:FE:AD:BF:C5 0000:3b:00.1 net_i40e       up       25000Mbps


# trying to set back up
testpmd> set link-up port 0
i40e_phy_conf_link():     Current: abilities 4, link_speed 0
i40e_phy_conf_link():     Config:  abilities 3c, link_speed 7e
testpmd> i40e_dev_alarm_handler(): ICR0: adminq event

testpmd> show port summary all
Number of available ports: 2
Port MAC Address       Name         Driver         Status   Link
0    3C:FD:FE:AD:BF:C4 0000:3b:00.0 net_i40e       down     0Mbps
1    3C:FD:FE:AD:BF:C5 0000:3b:00.1 net_i40e       up       25000Mbps

End of the game.
Need to bind back to the i40e kernel module to restore connectivity.


Any idea?

-- 
David Marchand

  reply	other threads:[~2019-10-31 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 14:20 David Marchand
2019-10-31 14:32 ` David Marchand [this message]
2019-11-04  5:33 ` Xing, Beilei

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='CAJFAV8z7bQ7s+KkPnyn7VR2khFRdTWpxiexsunh-L=1+-b2U=g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=cfontain@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jhsiao@redhat.com \
    --cc=qi.z.zhang@intel.com \
    /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).