[eepro100] Re: New problem with eepro100 and StrongArm board

[gerry.murphy@smartm.com]

--0__=cLjNsEm9PlLTCzdbRC03vAMEq4WsXuMbkm7akO7Tc0QIqGF3XVC1IWye
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline





Hi
     I have a problem similar to one  listed on the eepro100 mailing list in
July. My architecture is a StrongARM based ebsa285 running linux-2.4.0-test11,
although I have the same problem in test8-10. As in the problem description in
July the eepro100 passes the self test and tx a bootp request. It seems to
receive a valid response but does not  receive all the data, and doesnt see any
error asa result. The rx packet size usually is seen by the driver as 86bytes
but should be 380bytes, and most of the 86bytes received are correct, Just the
last 8bytes are junk.
Did anyone get to the bottom of this. I believed the cache coherence problems on
the StrongArm were solved by linux-2.4.
Thanks for you help
Gerry


Hello,

On Mon, Jul 03, 2000 at 04:59:44PM +0200, David M
--0__=cLjNsEm9PlLTCzdbRC03vAMEq4WsXuMbkm7akO7Tc0QIqGF3XVC1IWye
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-transfer-encoding: quoted-printable


=DDller wrote:
> After the upgrade to Linux 2.4.0-test2, the self test of the Intel 82=
559
> based NIC (on a StrongArm eval board) seems to work quite good, but n=
ow i
> have a new problem.
>
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.33 $ 2000/05/24 Modified by Andrey V. Savoch=
kin
<saw@saw.sw.com.sg> and others
> Found Intel i82557 PCI Speedo, MMIO at 0x4080000, IRQ 22.
> eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:D0:B7:4C:36:56, =
IRQ 22.
> Receiver lock-up bug exists -- enabling work-around.
> Board assembly 721383-008, 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 (0x04f4518b).
> Sending BOOTP requests....<7>eth0: Link status change.
> .<7>eth0: Media control tick, status e050.
> .<7>eth0: Media control tick, status e050.
> .<7>eth0: Media control tick, status e050.
> .<7>eth0: Media control tick, status e050.
> .<7>eth0: Media control tick, status e050.
> .<7>eth0: Media control tick, status f048.
> .<7>eth0: Media control tick, status f048.
> .<7>eth0: Media control tick, status f048.
> .<7>eth0: Media control tick, status f048.
> timed out!
> IP-Config: Auto-configuration of network failed.
>
> My BOOTP server gets the request and responses to it, but the
> reply seems to get lost.
> As the FR bit in the status register is set, i think that the
> reply packet was received, but not further processed.

Looks like it.
So, either the card didn't generate interrupt, or the driver didn't see=
 the
RX buffer status updated by the card directly in the memory.
Considering your architecture, I suspect the latter.

Best regards
                                        Andrey V.
                                        Savochkin
=

--0__=cLjNsEm9PlLTCzdbRC03vAMEq4WsXuMbkm7akO7Tc0QIqGF3XVC1IWye--