Intermittent problems on PowerPC

[Matt Porter]

I'm using Andrey's latest eepro100.c on a PowerPC-based CompactPCI board.
The odd thing is that I've had the thing working and even had a
dual 82559 PMC module inserted and had all three interfaces working
after nfsrooting and configuring the other ones.  Basically, I'll
go through some boots where the thing just won't receive anything.
With kernel level autoconfiguration on as below, I can see it transmit
BOOTP request and my server responds, but apparent it never receives
the response because it doesn't continue.

Has anybody had success with the latest eepro100 on PowerPC?  I've
included a dump with debugging on below is anybody has any ideas.

Thanks,
Matt

-----

Found Intel i82557 PCI Speedo at I/O 0xf7fff000, IRQ 1.
  PCI latency timer (CFLT) is unreasonably low at 0.  Setting to 32 clocks.
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/dril
eepro100.c: $Revision: 1.20.2.5 $ 2000/03/28 Modified by Andrey V. Savochkin <ss
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly ffffff-255, Physical connectors present: RJ45 BNC AUI MII
  Primary interface chip unknown-15 PHY #31.
    Secondary interface chip i82555.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x8b51f404).
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drileepro100.c: $Revision: 1.20.2.5 $ 2000/03/28 Modified by Andrey V. Savochkin <ssSending BOOTP requests....<7>eth0: Media control tick, status 6050.
.<7>eth0: Media control tick, status 6050.
.<7>eth0: Media control tick, status 6050.
.<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.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device 02:00
Kernel panic: VFS: Unable to mount root fs on 02:00
Rebooting in 180 seconds.. 
-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-eepro100-request@beowulf.org