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>
Subject: [dpdk-dev] Link status issue with i40e firmware 7.0x
Date: Wed, 30 Oct 2019 15:20:36 +0100	[thread overview]
Message-ID: <CAJFAV8wkf_rYTAfA4RhEF7f4YAJ9QXXvChOg4O8aqPjOSYxvfg@mail.gmail.com> (raw)

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.

I tried with the 19.11-rc1 tag, same behavior.

To restore connectivity, the workaround is to unbind the device from
vfio-pci, bind it again to the i40e kernel driver, and bind it back to
vfio-pci.


We noticed a question on Intel forum:
https://forums.intel.com/s/question/0D50P00004OjvP2SAJ/xxv7102-how-to-rollbackdowngrade-firmware-to-version-601-from-version-700
But no public solution in this forum.


We are trying to downgrade the firmware to version 6.8x or 6.0x but so
far, we did not manage to do this downgrade.


Any help appreciated.

Thanks.

-- 
David Marchand

             reply	other threads:[~2019-10-30 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 14:20 David Marchand [this message]
2019-10-31 14:32 ` David Marchand
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=CAJFAV8wkf_rYTAfA4RhEF7f4YAJ9QXXvChOg4O8aqPjOSYxvfg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=cfontain@redhat.com \
    --cc=dev@dpdk.org \
    --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).