public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@cs.columbia.edu>
To: "Matthew S. Hallacy" <poptix@techmonkeys.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100.c bug on 10Mbit half duplex (kernels 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11)
Date: Thu, 11 Oct 2001 16:08:39 -0400	[thread overview]
Message-ID: <200110112008.f9BK8dP20700@buggy.badula.org> (raw)
In-Reply-To: <20011011114208.N11846@techmonkeys.org>

On Thu, 11 Oct 2001 11:42:08 -0600, Matthew S. Hallacy <poptix@techmonkeys.org> wrote:

> I currently have the equivalent of 8 of these in my system (Compaq NC3131,
> quad ethernet..)
> 
>  Bus  2, device   4, function  0:
>    Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 5).
>                                           ^^^^

Umm, no, that's actually an 82558 rev B. pci.ids should be updated to 
have "Intel Corporation 8255[7-9]" for this id, because Intel can't make 
up their minds to change the PCI id when they release a new product.

rev 1-3 are 82557, rev 4-5 are 82558, rev 6-8 are 82559.

> it is the same chip, this particular interface is 10mbit/half duplex, and
> all the interfaces transfer 1G+/day (some small files, some larger than 500 megs)
> with no problems, I should note this:
> 
> eth0: OEM i82557/i82558 10/100 Ethernet, DE:AD:BA:BE:CA:FE, IRQ 10.
>  Receiver lock-up bug exists -- enabling work-around.
>  ^^^^^^^^^^^^^^^^^^^^

The OEM probably forgot to initialized the eeprom correctly, because 
82558 rev B and higher don't have this bug. Anyway, the workaround is 
pretty harmless.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

  reply	other threads:[~2001-10-11 20:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 12:29 eepro100.c bug on 10Mbit half duplex (kernels 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11) Robbert Kouprie
2001-10-11 16:27 ` John Gluck
2001-10-11 16:52   ` Robbert Kouprie
2001-10-11 17:15     ` Alan Cox
2001-10-11 17:29       ` Robbert Kouprie
2001-10-11 19:19       ` Robbert Kouprie
2001-10-11 19:34         ` Alan Cox
2001-10-11 21:02           ` Robbert Kouprie
2001-10-11 17:42 ` Matthew S. Hallacy
2001-10-11 20:08   ` Ion Badulescu [this message]
2001-10-11 20:16     ` Dan Hollis
  -- strict thread matches above, loose matches on Subject: below --
2001-10-12  8:41 Robbert Kouprie
2001-10-12 13:40 ` Ion Badulescu
2001-10-13 18:16   ` Robbert Kouprie

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=200110112008.f9BK8dP20700@buggy.badula.org \
    --to=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=poptix@techmonkeys.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