From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Alex Forster <alex@alexforster.com>, e1000-devel@lists.sourceforge.net
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Unsupported SFP+ Module - Hardware Initialization Failure -19
Date: Tue, 30 Aug 2016 21:21:49 -0500 [thread overview]
Message-ID: <CACZ4nhsJK3Ap2_PVfy2=soZnXqVgX_qgSr+qeiOj_zUJs0vk+Q@mail.gmail.com> (raw)
In-Reply-To: <513E1D25-0380-4D94-B254-3C129FD46A68@alexforster.com>
On Tue, Aug 30, 2016 at 11:02 AM, Alex Forster <alex@alexforster.com> wrote:
> Hi guys,
>
> I have a problem again that I had about a year ago[1]. My Finisar
> FTL410QE2C (multimode QSFP) transceivers aren’t working with my Intel
> X520-QDA1’s. I have 7 servers, each with two X520’s and two QSFP
> transceivers in them, totaling 14 NICs and transceivers, and all of them
> fail with the same error: Unsupported SFP+ Module / Hardware Initialization
> Failure: -19.
>
> This doesn’t appear to be specifically a DPDK issue, but rather an IXGBE
> issue, since (a) the stock Debian 8 IXGBE, (b) the latest out of tree
> IXGBE, and (c) DPDK’s copy of IXGBE all fail in this same way. I’m happy to
> take this to an IXGBE mailing list if somebody can point me to one, but
> just in case anyone here can help, here’s the info I’ve gathered–
>
> * The exact function where IXGBE bails is here, annotated with the values
> read from the transceiver’s EEPROMs: https://www.googledrive.com/
> host/0B_-81lR_g8lyNDJ6QkkxS28yQzQ
> * I’ve modified DPDK’s copy of IXGBE to dump the whole EEPROM of these
> transceivers, which are here: https://gist.github.com/alexforster/
> 5da30cd89d49877d5d6908e9628baee8
>
> Here’s (I think) an important part: Last time I had this problem, I only
> had one server, and one of the two transceivers worked. I fixed the other
> transceiver in that server by replacing it with an identical model. Now,
> suddenly, neither of those transceivers (which have worked for ~11 months)
> are recognized. I don’t know how I could have done something that would
> have affected the EEPROM output, but I suspect I may have.
>
> Anybody able to offer any advice?
>
> Alex Forster
>
> [1] http://dpdk.org/ml/archives/dev/2015-October/024973.html
Adding e1000-devel@lists.sourceforge.net
next prev parent reply other threads:[~2016-08-31 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 16:02 Alex Forster
2016-08-31 2:21 ` Ajit Khaparde [this message]
2016-08-31 16:28 ` [dpdk-dev] [E1000-devel] " Skidmore, Donald C
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='CACZ4nhsJK3Ap2_PVfy2=soZnXqVgX_qgSr+qeiOj_zUJs0vk+Q@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=alex@alexforster.com \
--cc=dev@dpdk.org \
--cc=e1000-devel@lists.sourceforge.net \
/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).