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

[Andrey Savochkin]

Hello,

On Mon, Jul 03, 2000 at 04:59:44PM +0200, David Müller wrote:
> After the upgrade to Linux 2.4.0-test2, the self test of the Intel 82559
> based NIC (on a StrongArm eval board) seems to work quite good, but now 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. Savochkin <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