public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: John <me@privacy.net>
Cc: linux-kernel@vger.kernel.org, linux.nics@intel.com
Subject: Re: Intel 82559 NIC corrupted EEPROM
Date: Fri, 03 Nov 2006 17:46:25 -0800	[thread overview]
Message-ID: <454BF0F1.5050700@zytor.com> (raw)
In-Reply-To: <454B7C3A.3000308@privacy.net>

John wrote:
> 
> 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?
> 

Yes, the driver needs to be loaded.

Basically, Auke wants you to throw away your NIC and/or motherboard. 
Since you're effectively dead, the only damage you can do by disabling 
the check has already been done.  This unfortunately seems to be fairly 
common with e100, especially for the on-motherboard version, and you 
basically have two options: either disable the check or write an offline 
tool to reprogram the EEPROM.

The latest netdev tree (if it's not in Linus' tree already, which it 
might be) does add back the option to ignore the check so you can update 
the EEPROM, which will automatically fix the checksum.

	-hpa

  reply	other threads:[~2006-11-04  1:48 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 [this message]
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=454BF0F1.5050700@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.nics@intel.com \
    --cc=me@privacy.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