From: "Matthew S. Hallacy" <poptix@techmonkeys.org>
To: 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 11:42:08 -0600 [thread overview]
Message-ID: <20011011114208.N11846@techmonkeys.org> (raw)
In-Reply-To: <002001c15250$6fad3c50$020da8c0@nitemare>
In-Reply-To: <002001c15250$6fad3c50$020da8c0@nitemare>; from robbert@radium.jvb.tudelft.nl on Thu, Oct 11, 2001 at 02:29:56PM +0200
On Thu, Oct 11, 2001 at 02:29:56PM +0200, 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.
[snip]
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).
^^^^
IRQ 10.
Master Capable. Latency=64. Min Gnt=8.Max Lat=56.
Prefetchable 32 bit memory at 0xcb7ff000 [0xcb7fffff].
I/O at 0x7c00 [0x7c1f].
Non-prefetchable 32 bit memory at 0xcfe00000 [0xcfefffff].
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.
^^^^^^^^^^^^^^^^^^^^
Board assembly 009542-001, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x24c9f043).
Receiver lock-up workaround activated.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
eth1: OEM i82557/i82558 10/100 Ethernet, DE:AD:BE:EF:CA:FE, IRQ 10.
Receiver lock-up bug exists -- enabling work-around.
^^^^^^^^^^^^^^^^^^^^
Board assembly 009542-001, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x24c9f043).
Receiver lock-up workaround activated.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
etc etc, for every interface.
I'm up to 2.4.10, it's worked fine on 2.4.2, 2.4.4, 2.4.5-8, and 2.4.10 so far.
(I didn't use the kernels not mentioned)
Good luck.
-poptix
next prev parent reply other threads:[~2001-10-11 17:46 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 [this message]
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=20011011114208.N11846@techmonkeys.org \
--to=poptix@techmonkeys.org \
--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