From: "Robbert Kouprie" <robbert@radium.jvb.tudelft.nl>
To: "'John Gluck'" <jgluckca@home.com>
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 18:52:49 +0200 [thread overview]
Message-ID: <002601c15275$2945b510$020da8c0@nitemare> (raw)
In-Reply-To: <3BC5C866.1337F5DF@home.com>
Hi,
My testcase was indeed one large file. I did not test lots of small
files. It would always lockup after said amount of traffic, but only in
10 Mbit half duplex mode. Also, I have the 82557, not the 82558 chip.
The problem looks a lot like what should be fixed in this changelog line
from 2.4.9-ac13:
- Work around eepro100 bug with some chip (Arjan van de
Ven)
versions on 10Mbit half duplex
Only 2.4.10ac11 still had the problem...
- Robbert
> -----Original Message-----
> From: john@femail22.sdc1.sfba.home.com
> [mailto:john@femail22.sdc1.sfba.home.com] On Behalf Of John Gluck
> Sent: donderdag 11 oktober 2001 18:27
> To: Robbert Kouprie
> 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)
>
>
> Hi
>
> I haven't noticed this problem on my system...
>
> I have an 82558 that uses this driver on a Tyan S1836DLUAN
> motherboard.
> I have Dual PIIIs and the system is multi homed. I have a 2nd
> interface that
> uses the NE2000 PCI driver.
>
> The system is my workstation but also acts as an internet
> gateway (via cable
> modem) and firewall for 2 other computers. My workstation is
> on 24/7 and has
> never hungup.
>
> I am currently using 2.4.10 for the kernel but I've used most
> kenels since
> the 2.4.0testX days.
>
> In your tests, is the 80 - 130 megs a single file or is it an
> aggregate. In
> my use I far exceed the amount of data but it's web surfing
> so the files are
> much smaller the what you mention.
>
> John
>
> Robbert Kouprie wrote:
>
> > Hi all,
> >
> > I can confirm that the known bug in the Intel EtherExpress Pro/100
> > adapter is still not worked around in recent kernels. The bug only
> > manifests itself when the card is operating on 10 Mbit half
> duplex. On
> > 100 Mbit there are no problems. The problem is that after the device
> > received certain amount of traffic (between 80 and 130 Mb
> in my tests)
> > the device will lockup on new connections. Processes start
> to hang after
> > this and logging in is impossible. The only solution is to reset the
> > interface (using a previously logged in root session) and reboot the
> > system.
> >
>
>
next prev parent reply other threads:[~2001-10-11 16:52 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 [this message]
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
-- 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='002601c15275$2945b510$020da8c0@nitemare' \
--to=robbert@radium.jvb.tudelft.nl \
--cc=jgluckca@home.com \
--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