lkml.org 
[lkml]   [2001]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: eepro100.c bug on 10Mbit half duplex (kernels 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11)
Date
On Fri, 12 Oct 2001, Ion Badulescu wrote:

> > > Receiver lock-up bug exists -- enabling work-around.
> > > ^^^^^^^^^^^^^^^^^^^^
> >
> > My card DOES NOT have the receiver lock-up bug
>
> Your card's eeprom claims otherwise. The eeprom is most
> likely wrong, but
> again, the workaround for *this* bug is pretty harmless,
> whether the bug
> exists or not.
>
> Ion
>

Sorry, this was kind of a unlucky paste, because this line:

> > > Receiver lock-up bug exists -- enabling work-around.
> > > ^^^^^^^^^^^^^^^^^^^^

is from the previous sender's dmesg (Matthew S. Hallacy). *My card* does
not give this message, but it surely has a bug (which is not the
receiver lock-up bug).

Earlier, I was somewhat too quick with my conclusions. Since I upgraded
the link to 100 Mbit, also half duplex, the problem seemed gone. This
was NOT the case. The problem now only takes about 10 times as much
traffic to trigger.

* With vanilla kernel-2.4.13-pre2 the problem exists.
* With vanilla kernel-2.4.12-ac1 the problem exists.

So I added my device id to the 10 Mbit half-duplex workaround check, and
problem went away. For now. ;) I am gonna test this for some days and if
it stays put I will post the patch. Anyway, I should've stuck with 3com
:)

Regards,
- Robbert



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.037 / U:2.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site