NAME

eg − Solbourne VMEbus 10MB Ethernet interface

CONFIG

device eg0 at vme16d16 ? csr 0x9000
dma vme24d32_blk priority 3 vector egintr 0xe0
device eg1 at vme16d16 ? csr 0x9800
dma vme24d32_blk priority 3 vector egintr 0xe2

The synopsis lines above specify the Ethernet controller(s) on the VMEbus. 

DESCRIPTION

The eg interface provides access to a 10 Mb/s Ethernet network through the VMEbus.  For a general description of network interfaces see if(4N). 

SEE ALSO

if(4N), kb(4S), tty_compact(4)

DIAGNOSTICS

Common conditions which cause this message are listed below, if other messages occur they should be reported to Solbourne technical support:

eg%d is reserved for remote debugging 
The interface is present but being used exclusively for debugging.

eg%d: enet-address: rev-info
The enet-address is the hardware ethernet address for the controller board and rev-info contains information about the firmware revision, driver revision, and options. 

eg%d: Failed CNA status
This error indicates that the Controller is Not Available because of the specified status. 

eg%d: unable to configure: cause
This error indicates that the controller could not be configured for the specified cause. 

eg%d: CRB not done
After an interrupt the Command Response Block was not valid.

eg%d: big packet (%d)
Provided that all stations on the Ethernet are operating according to the Ethernet specification, this error “should never happen,” since the controller allocates its receive buffers to be large enough to hold packets of the largest permitted size. Most likely, some other station on the net is transmitting packets whose lengths exceed the maximum permitted for Ethernet.

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

eg%d: out of mbufs: output packet dropped 
The controller 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.

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

eg%d: transmit error tx-stat1 tx-stat3
An error occurred while trying to transmit a packet.

The tx-stat1 bit-field may have one or more of the following bit set:

MULTIPLE-RETRY
One or more retries was needed to transmit the packet.

RETRY
One retry was needed to transmit the packet.

DEFERED
The controller had to defer transmission of the packet until the net was idle.

The tx-stat3 bit-field has the following bits:

BUFFER_ERROR
This error “should never happen”.

UNDERFLOW
Excessive bus contention  has  prevented  the controller  from  gathering  packet contents quickly  enough  to  sustain   the   packet’s transmission over the Ethernet.  The affected packet is lost.

LATE_COLLISION
A packet collision  has  occurred  after  the channel’s  slot time has elapsed.  This error usually indicates faulty  hardware  elsewhere on the net.

LOSS_OF_CARRIER
The controller has lost input to its  carrier detect pin while trying to transmit a packet.

RETRY_FAILED
Network activity has become so  intense  that sixteen   successive   transmission  attempts failed, the controller gave up on the current packet.

eg%d: receive error %b
An error occurred while trying to receive a packet. The FRAMMING_ERROR and CRC_ERROR messages usually indicate a transition failure at another node, or some other physical net problem. The rx-stat1 bit-field has the following bits:

FRAMMING_ERROR
An incoming packet had a non-multiple of 8-bits.

OVERFLOW
The controller has  dropped  an  incoming  packet because it had no buffer space for it.

CRC_ERROR
A CRC error was detected in the incoming packet.

BUFFER_ERROR
This error “should never happen”.

Solbourne Computer, Inc.  —  11 Jan 1994