From: "Krzysztof Olędzki" <ole@ans.pl>
To: Rick Jones <rick.jones2@hp.com>
Cc: eilong@broadcom.com, Michael Chan <mchan@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2x + SFP+ DA/2.6.33.3: Got bad status 0x0 when reading from SFP+ EEPROM -> SFP+ module is not initialized
Date: Thu, 20 May 2010 22:54:54 +0200 [thread overview]
Message-ID: <4BF5A19E.5010003@ans.pl> (raw)
In-Reply-To: <4BF59ABB.9070600@hp.com>
On 2010-05-20 22:25, Rick Jones wrote:
> Some simple/simplistic thoughts/questions...
>
> Has the DAC been used successfully prior to this?
Yes. It was successfully used to connect two HP switches, before I
received SFP+ SR modules, that allowed me to put the switches into
distanced rooms.
> Do you have another HP ProCurve 10-GbE SFP+ 7m Direct Attach Cable (J9285B) to try?
Yes. The same situation.
> There's a transceiver and presumably an EEPROM at both ends of a DAC right?
Yes, I think there should be one. ;)
> If
> the EEPROM at one end were "bad" might the 57711 be happier with the other end
> of the DAC?
Tested both ends. The same situation. :|
> Getting some sort of error message at the switch side, which may
> (or may not) have more detailed diagnostics might help.
There is no error message at the switch side. The switch shows that
everything is correct.
Best regards,
Krzysztof Olędzki
next prev parent reply other threads:[~2010-05-20 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 17:08 bnx2x + SFP+ DA/2.6.33.3: Got bad status 0x0 when reading from SFP+ EEPROM -> SFP+ module is not initialized Krzysztof Olędzki
2010-05-20 17:49 ` Eilon Greenstein
[not found] ` <4BF57ADF.1060203@ans.pl>
2010-05-20 18:45 ` Eilon Greenstein
2010-05-20 19:41 ` Krzysztof Olędzki
2010-05-20 20:25 ` Rick Jones
2010-05-20 20:54 ` Krzysztof Olędzki [this message]
2010-05-21 12:58 ` Eilon Greenstein
2010-05-21 13:19 ` Krzysztof Olędzki
2010-05-21 16:43 ` Krzysztof Olędzki
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=4BF5A19E.5010003@ans.pl \
--to=ole@ans.pl \
--cc=eilong@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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).