[eepro100] Lockup with Intel PRO/100+ Dual Port Server Adapter

[Donald Becker]

On Sat, 13 Jan 2001, Thomas Lorenzen wrote:

> >>> > machine. My test machine is an old 486. Do you have any idea
> >>> Oooohhh, a 486.  Probably a SP3G with the Neptune chip set.
> >>> The one with the PCI burst bug.
..
> >>> This set cache alignment to 8 longwords and the burst limit to 8
> >>> longwords.
> >>> 
> >>> You _might_ be able to see the same effect with the eepro100 driver
> >>> setting the module options
> >>>    txdmacount=8 rxdmacount=8

>    I addition to the dual port adapter the PIII machine is
> also equipped with a 3com adapter, which is eth0 below.
> Entries eth1 and eth2 below steems from the dual port
> adapter.

> eth1      Link encap:Ethernet  HWaddr 00:03:47:3B:27:EE  
>           inet addr:192.168.200.201  Bcast:192.168.200.255 Mask:255.255.255.0
...
> eth2      Link encap:Ethernet  HWaddr 00:03:47:3B:27:EF  
>           inet addr:192.168.200.202  Bcast:192.168.200.255 Mask:255.255.255.0

Note that the interfaces both have the same station address.
You must run trunking on the switch if they are both on the same network
segment.

>   9:      13270          XT-PIC  eth1
>  12:      55770          XT-PIC  eth0, eth2

This is harmless.  I don't know why the BIOS picked this assignment, but
it should work.

You might want to test that the BIOS did set up the mapping correctly:
the packet count should approximatly equal the interrupt count.  Wait
for an idle period (or unplug) on eth0 and put a bunch of traffic on
eth1 and eth2.  Verify that the interrupt counts are increasing for both.


Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993