From: "H. Peter Anvin" <hpa@zytor.com>
To: John <me@privacy.net>
Cc: linux-kernel@vger.kernel.org, linux.nics@intel.com,
saw@saw.sw.com.sg, thockin@hockin.org
Subject: Re: Intel 82559 NIC corrupted EEPROM
Date: Tue, 07 Nov 2006 09:17:05 -0800 [thread overview]
Message-ID: <4550BF91.2020403@zytor.com> (raw)
In-Reply-To: <45506C9A.5010009@privacy.net>
John wrote:
>
> I then used ethtool to dump the contents of the EEPROMs.
>
> # ethtool -e eth0
> Offset Values
> ------ ------
> 0x0000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>
> Either the EEPROM image on eth0 is corrupted, or ethtool is not
> able to read the contents of the EEPROM.
>
[...]
>
> I then used Donald Becker's program to dump the contents of all
> the EEPROMs. ( ftp://www.scyld.com/pub/diag/ )
>
> # eepro100-diag -ee
> eepro100-diag.c:v2.13 2/28/2005 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
>
> Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xd800.
> EEPROM contents, size 64x16:
> 00: 3000 0464 e4e6 0e03 0000 0201 4701 0000 _0d__________G__
> 0x08: 7213 8310 40a2 0001 8086 0000 0000 0000 _r___@__________
> ...
> 0x30: 0128 0000 0000 0000 0000 0000 0000 0000 (_______________
> 0x38: 0000 0000 0000 0000 0000 0000 0000 92f7 ________________
> The EEPROM checksum is correct.
> Intel EtherExpress Pro 10/100 EEPROM contents:
> Station address 00:30:64:04:E6:E4.
> Board assembly 721383-016, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> Sleep mode is enabled. This is not recommended.
> Under high load the card may not respond to
> PCI requests, and thus cause a master abort.
> To clear sleep mode use the '-G 0 -w -w -f' options.
>
> Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xdc00.
> EEPROM contents, size 64x16:
> 00: 3000 0464 e5e6 0e03 0000 0201 4701 0000 _0d__________G__
> 0x08: 7213 8310 40a2 0001 8086 0000 0000 0000 _r___@__________
> ...
> 0x30: 0128 0000 0000 0000 0000 0000 0000 0000 (_______________
> 0x38: 0000 0000 0000 0000 0000 0000 0000 91f7 ________________
> The EEPROM checksum is correct.
> Intel EtherExpress Pro 10/100 EEPROM contents:
> Station address 00:30:64:04:E6:E5.
> Board assembly 721383-016, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> Sleep mode is enabled. This is not recommended.
> Under high load the card may not respond to
> PCI requests, and thus cause a master abort.
> To clear sleep mode use the '-G 0 -w -w -f' options.
>
> Index #3: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xe000.
> EEPROM contents, size 64x16:
> 00: 3000 0464 e6e6 0e03 0000 0201 4701 0000 _0d__________G__
> 0x08: 7213 8310 40a2 0001 8086 0000 0000 0000 _r___@__________
> ...
> 0x30: 0128 0000 0000 0000 0000 0000 0000 0000 (_______________
> 0x38: 0000 0000 0000 0000 0000 0000 0000 90f7 ________________
> The EEPROM checksum is correct.
> Intel EtherExpress Pro 10/100 EEPROM contents:
> Station address 00:30:64:04:E6:E6.
> Board assembly 721383-016, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> Sleep mode is enabled. This is not recommended.
> Under high load the card may not respond to
> PCI requests, and thus cause a master abort.
> To clear sleep mode use the '-G 0 -w -w -f' options.
>
> Apparently, eepro100.ko is able to read the contents of the EEPROM on
> eth0 and it declares the checksum correct. Is it possible that there is
> a bug in e100.c that makes it fail to read the EEPROM on eth0?
>
Sure as heck sounds like it.
-hpa
next prev parent reply other threads:[~2006-11-07 17:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 17:28 Intel 82559 NIC corrupted EEPROM John
2006-11-04 1:46 ` H. Peter Anvin
2006-11-04 6:22 ` thockin
2006-11-04 6:28 ` thockin
2006-11-07 11:23 ` John
2006-11-07 17:17 ` H. Peter Anvin [this message]
2006-11-07 17:43 ` Auke Kok
2006-11-07 18:27 ` H. Peter Anvin
2006-11-07 18:34 ` Auke Kok
2006-11-07 18:38 ` H. Peter Anvin
2006-11-08 10:55 ` John
2006-11-08 16:17 ` Auke Kok
2006-11-09 12:17 ` John
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
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 16:35 Amin Azez
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=4550BF91.2020403@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=me@privacy.net \
--cc=saw@saw.sw.com.sg \
--cc=thockin@hockin.org \
/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