Hello!

> Diagnosing this problem really depends on the driver and hardware
> you're using, which isn't given in your message above.
> If you  specify

You are right, sorry!
 
> 	* The version of NetBSD you're using (and date, for -current)

NetBSD current 22.12.1996
 
> 	* exactly what network interface you're using
> 	  (name, model, bus, firmware/asic level, etc.),

PCMCIA 3COM Etherlink III 3C589C, ep0

> 	* the kind of machine you're using (e.g., laptop?)

Laptop Toshiba Tecra 500 CDT
 
> 	* ideally, the network-interface attach messages the
> 	  kernel gives at boot time, and any mesages for the
> 	  bus your network is attatched to;

pcicmaster0 at isa0 port 0x3e0-0x3e1
pcic0 at pcicmaster0: Intel 82365sl Rev. 1 slots 0-1 iomem d4000-d4fff irq 11
pcmcia0 at pcic0
pcmcia0: slot 0 contains <3Com Corporation, 3C589, TP/BNC LAN Card Ver.  2a, 000002>
ep0 at pcmcia0 port 0x300-0x30f irq 10: 3Com 3C589 Ethernet
ep0: 8KB byte-wide RAM, aui/bnc/utp, address 00:60:97:40:bc:a7

> If you have console access, does 
> 	 ifconfig <ifname> down; ifconfig <ifname> up
> help at all after an APM resume?

I tryed that without success.

Greets
-- 

   Name  : Thorsten Frueauf            Milano@irc cri@onaliM       //
   E-Mail: s_frueau@ira.uka.de oder ukfy@rz.uni-karlsruhe.de     \X/