From: "Molle Bestefich" <molle.bestefich@gmail.com>
To: "Auke Kok" <auke-jan.h.kok@intel.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 18:45:57 +0200 [thread overview]
Message-ID: <62b0912f0607100945o574dcce8w8f734e5828bdcaa8@mail.gmail.com> (raw)
In-Reply-To: <44B2716A.3030009@intel.com>
Auke Kok wrote:
> 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.
Every single IP130 I've had my hands on has had an EEPROM that the
Linux driver declared bad.
I'm afraid that it's not the board that's at fault, it's the driver.
The NICs are working perfectly.
(Also, it seems mighty odd to refuse to drive the hardware based on an
EEPROM checksum failure, when the e100 driver will happily load for a
device where for example IRQ routing is broken. Just another
indication that erroring out in this situation is overkill.)
next prev parent reply other threads:[~2006-07-10 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 11:34 Molle Bestefich
2006-07-10 15:25 ` Auke Kok
2006-07-10 16:45 ` Molle Bestefich [this message]
2006-07-10 17:20 ` Auke Kok
2006-07-10 17:41 ` Molle Bestefich
2006-07-10 17:58 ` Auke Kok
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=62b0912f0607100945o574dcce8w8f734e5828bdcaa8@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®