From: John <me@privacy.net>
To: linux-kernel@vger.kernel.org
Cc: linux.nics@intel.com
Subject: Intel 82559 NIC corrupted EEPROM
Date: Fri, 03 Nov 2006 18:28:26 +0100 [thread overview]
Message-ID: <454B7C3A.3000308@privacy.net> (raw)
Hello,
I have an EBC-2000T motherboard with 3 on-board Intel 82559 NICs.
http://www.intel.com/design/network/products/lan/controllers/82559.htm
http://www.adlinktech.com/PD/web/PD_detail.php?pid=213
http://www.intel.com/support/network/adapter/1000/linux/e100.htm
Running a 2.6.14 kernel, the e100 driver refuses to load because
it detects a corrupted EEPROM.
cf. e100_eeprom_load()
/* The checksum, stored in the last word, is calculated such that
* the sum of words should be 0xBABA */
checksum = le16_to_cpu(0xBABA - checksum);
if(checksum != nic->eeprom[nic->eeprom_wc - 1]) {
DPRINTK(PROBE, ERR, "EEPROM corrupted\n");
if (!eeprom_bad_csum_allow)
return -EAGAIN;
}
Several people have reported the same error. Intel's Auke Kok has
stated that ignoring the error is a BAD idea.
http://lkml.org/lkml/2006/7/10/215
What tool is used to reprogram the EEPROM? ethtool?
I suppose I'll have to ask the manufacturer for an updated EEPROM?
# ethtool -e eth0
Cannot get EEPROM data: Operation not supported
I'm not sure why I can't dump the contents of the EEPROM.
Does the driver need to be loaded?
On a totally unrelated note, does the 82559 support VLAN tagging?
(I believe the driver supports it.)
Thanks for reading this far.
Please note, email address is a bit-bucket.
I do monitor the mailing list.
Regards.
John
# lspci -vv
[...]
00:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e5402000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at d800 [size=64]
Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 20000000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 12
Region 0: Memory at e5401000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at dc00 [size=64]
Region 2: Memory at e5100000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 20100000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e5400000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e000 [size=64]
Region 2: Memory at e5200000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 20200000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
next reply other threads:[~2006-11-03 17:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 17:28 John [this message]
2006-11-04 1:46 ` Intel 82559 NIC corrupted EEPROM 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
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=454B7C3A.3000308@privacy.net \
--to=me@privacy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.