From: "Robbert Kouprie" <robbert@radium.jvb.tudelft.nl>
To: "'Ion Badulescu'" <ion@cs.columbia.edu>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
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: Sat, 13 Oct 2001 20:16:33 +0200 [thread overview]
Message-ID: <002601c15413$305938f0$020da8c0@nitemare> (raw)
In-Reply-To: <Pine.LNX.4.33.0110120923010.7250-100000@guppy.limebrokerage.com>
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
next prev parent reply other threads:[~2001-10-13 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 8:41 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-12 13:40 ` Ion Badulescu
2001-10-13 18:16 ` Robbert Kouprie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-11 12:29 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
2001-10-11 20:16 ` Dan Hollis
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='002601c15413$305938f0$020da8c0@nitemare' \
--to=robbert@radium.jvb.tudelft.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ion@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.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