I got a panic from the Tulip driver on a freshly installed 1.4 system 
on an Intel box.  I haven't seen this mentioned before.  Did I miss 
something? 

Here is the long story.

I just installed 1.4 on a PC.  I hadn't had time to clean up the 
network config area yet.  I had a point-point link connected to another 
PC.  When I rebooted the other PC, the PC running NetBSD landed in 
the debugger with this message: 

  tulip_media_link_monitor: unknown: botch at line 537 

I've got two Tulips in that box.  The one to the other PC is de1.  
It hasn't been configured yet. 

de0 at pci0 dev 13 function 0
de0: interrupting at irq 11
de0: DEC DE500-AA 21140A [10-100Mb/s] pass 2.2
de0: address 00:00:f8:1a:4b:9f
de1 at pci0 dev 14 function 0
de1: interrupting at irq 11
de1: DEC DE500-BA 21143 [10-100Mb/s] pass 3.0
de1: address 00:00:f8:1f:99:2a

% netstat -I de1
Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs Colls
de1*  1500  <Link>        00:00:f8:1f:99:2a        0     0        0     0     0
% 


Here is that chunk of code:

    if (mi == NULL) { 
#if defined(DIAGNOSTIC) || defined(TULIP_DEBUG)
        panic("tulip_media_link_monitor: %s: botch at line %d\n",
              tulip_mediums[sc->tulip_media],__LINE__);
#endif
        return TULIP_LINK_UNKNOWN; 
    }


I typed "continue" to the debugger and it took a dump so I can get 
more info if that will help.