From: John <me@privacy.net>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
hpa@zytor.com, saw@saw.sw.com.sg
Subject: Re: Intel 82559 NIC corrupted EEPROM
Date: Thu, 09 Nov 2006 13:17:06 +0100 [thread overview]
Message-ID: <45531C42.3070503@privacy.net> (raw)
In-Reply-To: <45520337.2070303@intel.com>
Auke Kok wrote:
> This is what I was afraid of: even though the code allows you to bypass
> the EEPROM checksum, the probe fails on a further check to see if the
> MAC address is valid.
>
> Since something with this NIC specifically made the EEPROM return all
> 0xff's, the MAC address is automatically invalid, and thus probe fails.
I don't understand why you think there is something wrong with a
specific NIC?
In 2.6.14.7, e100.ko fails to read the EEPROM on 0000:00:08.0 (eth0)
In 2.6.18.1, e100.ko fails to read the EEPROM on 0000:00:09.0 (eth1)
In both kernels, eepro100.ko successfully reads all the EEPROMs.
> It seems that the driver has more problems with this NIC than just the
> eeprom checksum being bad. Needless to say this might need fixing.
>
> Can you load the eepro driver and send me the full eeprom dump?
> Perhaps I can duplicate things over here.
00:08.0 EEPROM contents, size 64x16
3000 0464 e4e6 0e03 0000 0201 4701 0000
7213 8310 40a2 0001 8086 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0128 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 92f7
00:09.0 EEPROM contents, size 64x16
3000 0464 e5e6 0e03 0000 0201 4701 0000
7213 8310 40a2 0001 8086 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0128 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 91f7
00:0a.0 EEPROM contents, size 64x16
3000 0464 e6e6 0e03 0000 0201 4701 0000
7213 8310 40a2 0001 8086 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0128 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 90f7
next prev parent reply other threads:[~2006-11-09 12:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <454B7C3A.3000308@privacy.net>
[not found] ` <454BF0F1.5050700@zytor.com>
[not found] ` <45506C9A.5010009@privacy.net>
2006-11-08 10:55 ` Intel 82559 NIC corrupted EEPROM John
2006-11-08 16:17 ` Auke Kok
2006-11-09 12:17 ` John [this message]
2006-11-09 17:03 ` Auke Kok
2006-11-08 17:26 ` Jesse Brandeburg
2006-11-09 14:15 ` John
2006-11-10 0:19 ` Jesse Brandeburg
2006-11-10 12:03 ` John
2006-11-15 8:34 ` John
2006-11-27 14:17 ` John
2006-11-27 20:34 ` Jesse Brandeburg
2006-11-29 11:26 ` John
2006-11-29 18:55 ` Jesse Brandeburg
[not found] ` <45704001.9040108@privacy.net>
2006-12-04 23:26 ` Jesse Brandeburg
[not found] <fa.FcMVUlqOXU3cAnxsPEN6d8T0wxU@ifi.uio.no>
[not found] ` <fa.0FC8eT8GQaLxmNQTrsqyNFjRK4E@ifi.uio.no>
[not found] ` <fa.nds0CFkNbotWh4VNM05EixY68wE@ifi.uio.no>
[not found] ` <fa.K3Gpuu7oYQv+4q85Ziy3ljV6u+E@ifi.uio.no>
[not found] ` <fa./RNOPU0DwWMrnKJSqlMaY+Y16JM@ifi.uio.no>
[not found] ` <fa.yV32AYzot0OkvPVCY7VTCvd6rJw@ifi.uio.no>
2007-02-07 11:06 ` John
2007-02-13 19:45 ` Brandeburg, Jesse
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=45531C42.3070503@privacy.net \
--to=me@privacy.net \
--cc=auke-jan.h.kok@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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).