public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux.nics@intel.com
Subject: Re: [bug] e100 bug: checksum mismatch on 82551ER rev10
Date: Mon, 10 Jul 2006 08:25:30 -0700	[thread overview]
Message-ID: <44B2716A.3030009@intel.com> (raw)
In-Reply-To: <62b0912f0607090434q735e36b7pd9ab35baf0914e7a@mail.gmail.com>

Molle Bestefich wrote:
> I'm trying to get Linux running on a Nokia IP130 box.
> 
> The 3x Intel i82551ER NICs doesn't work.
> 
> Apply this patch which just removes the error return path (and adds a
> little debug info):
> 
> ===============================================================
> --- drivers/net/e100.c.orig     2006-07-09 12:03:14.000000000 +0200
> +++ drivers/net/e100.c  2006-07-09 12:03:22.000000000 +0200
> @@ -756,8 +756,7 @@
>         * 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");
> -               return -EAGAIN;
> +               DPRINTK(PROBE, ERR, "EEPROM corrupted (stored: %4.4x, 
> calc'ed: %
> 4.4x)\n", nic->eeprom[nic->eeprom_wc - 1], checksum);
>        }
> 
>        return 0;
> ===============================================================
> 
> And everything works!
> 
> I think I've heard about this bug before, but I don't know why it occurs.
> So the best I can do is the above (ignore failed EEPROM checksum test).

[removed scott feldman since he's not maintained e100 for a long time now]

Hi,


If you have received a motherboard or card with a broken EEPROM then your card 
is in a limbo state - it might work but results are unreliable and may cause 
your entire system to break (and even data corruption).

You should contact the hardware vendor and have the board replaced or upgraded 
with a proper EEPROM. Continuing to work with the corrupted EEPROM image that 
you have now can seriously hurt you later on.

Cheers,

Auke

  reply	other threads:[~2006-07-10 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09 11:34 [bug] e100 bug: checksum mismatch on 82551ER rev10 Molle Bestefich
2006-07-10 15:25 ` Auke Kok [this message]
2006-07-10 16:45   ` Molle Bestefich
2006-07-10 17:20     ` Auke Kok
2006-07-10 17:41       ` Molle Bestefich
2006-07-10 17:58         ` Auke Kok
  -- strict thread matches above, loose matches on Subject: below --
2006-07-31 21:07 Charlie Brady

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=44B2716A.3030009@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.nics@intel.com \
    --cc=molle.bestefich@gmail.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