NAME

le − Sun-3/50 10 Mb/s Ethernet interface

SYNOPSIS

device le0 at obio ? csr

DESCRIPTION

The le interface provides access to a 10 Mb/s Ethernet network through a Sun-3 controller using the AMD LANCE (Local Area Network Controller for Ethernet) Am7990 chip.  For a general description of network interfaces see if(4N).

The synopsis line above specifies the first and only Ethernet controller on a Sun-3/50. 

DIAGNOSTICS

le%d: transmitter frozen -- resetting  A bug in the LANCE chip has caused the chip’s transmitter section to stop.  The driver has detected this condition and reinitialized the chip. 

le%d: out of mbufs: output packet dropped  The driver has run out of memory to use to buffer packets on output.  The packet being transmitted at the time of occurrence is lost.  This error is usually symptomatic of trouble elsewhere in the kernel. 

le%d: stray transmitter interrupt  The LANCE chip has signalled that it completed transmitting a packet but the driver has sent no such packet. 

le%d: LANCE Rev C/D Extra Byte(s) bug; Packet dropped  The LANCE chip’s internal silo pointers have become misaligned.  This error arises from a chip bug. 

le%d: trailer error  An incoming packet claimed to have a trailing header but did not. 

le%d: runt packet  An incoming packet’s size was below the Ethernet minimum transmission size. 

le%d: Receive buffer error - BUFF bit set in rmd  This error “should never happen,” as it occurs only in conjunction with a LANCE feature that the driver does not use. 

le%d: Received packet with STP bit in rmd cleared  This error “should never happen,” as it occurs only in conjunction with a LANCE feature that the driver does not use. 

le%d: Received packet with ENP bit in rmd cleared  This error “should never happen,” as it occurs only in conjunction with a LANCE feature that the driver does not use. 

le%d: Transmit buffer error - BUFF bit set in tmd  Excessive bus contention has prevented the LANCE chip from gathering packet contents quickly enough to sustain the packet’s transmission over the Ethernet.  The affected packet is lost. 

le%d: Transmit late collision -  Net problem?  A packet collision has occurred after the channel’s slot time has elapsed.  This error usually indicates faulty hardware elsewhere on the net. 

le%d: No carrier - transceiver cable problem?  The LANCE chip has lost input to its carrier detect pin while trying to transmit a packet. 

le%d: Transmit retried more than 16 times - net jammed  Network activity has become so intense that sixteen successive transmission attempts failed, causing the LANCE chip to give up on the current packet. 

le%d: missed packet  The driver has dropped an incoming packet because it had no buffer space for it. 

le%d: Babble error - sent a packet longer than the maximum length  While transmitting a packet, the LANCE chip has noticed that the packet’s length exceeds the maximum allowed for Ethernet.  This error indicates a kernel bug. 

le%d: Memory Error!  Ethernet chip memory access timed out  The LANCE chip timed out while trying to acquire the bus for a DVMA transfer. 

le%d: Reception stopped  Because of some other error, the receive section of the LANCE chip shut down and had to be restarted. 

le%d: Transmission stopped  Because of some other error, the transmit section of the LANCE chip shut down and had to be restarted. 

Sun Release 3.5  —  Last change: 18 September 1985