NAME

be − 100Mb/s and 10Mb/s Ethernet interface

CONFIG — Desktop SPARCsystems, SPARCsystem 600MP SERIES

device-driver bqe

DESCRIPTION

The be interface provides access to a 100 Mb/s and 10 Mb/s Ethernet network. The device will automatically set the Ethernet speed of the interface based on the speed of the network that it is connected to.  For a general description of network interfaces see if(4N). 

DIAGNOSTICS

be%d: Cannot find 100Mbit tcvr, using 10Mbit 
The device cannot find a 100 Mbps transceiver and is switching to 10 Mbps mode.

be%d: Cannot free unit -- still running 
An attempt was made to unload the driver when the interface was still up. Use ifconfig be<num> down to bring the interface down before unloading the driver. 

be%d: Cannot reset 
Cannot reset the device. This is most likely due to a bad BE device.  be%d: No carrier − cable problem or hub link test disabled?  The device has lost the carrier detect signal.  The driver has a test feature that verifies the Ethernet cable connection between the device and the Ethernet hub. In order for this feature to function correctly, the Ethernet hub must support the link test feature and it must be turned on in the hub.  If the hub doesn’t support the link test or if the link test is disabled in the hub, you will see this error message during the system boot. 

If you receive this message indicating cable problems, first check the cable. If no cable problem can be found then check for a link integrity mismatch. If there is a link integrity mismatch, you may enable the link test feature in your Ethernet hub (usually by turning a switch on), or you may disable the link test in your SPARCsystem. 

If the link test is enabled in the hub while the link integrity test is disabled in the SPARCsystem, the SPARCsystem will not be able to communicate with other systems properly.  You may disable the link test feature in your Ethernet hub (usually by turning a switch off), or you may enable the link test in your SPARCsystem. 

To enable/disable the link test in the SPARCsystem, see eeprom(8S).  To enable/disable the link test in the SPARCsystem at the OBP’s ok prompt, enter the OBP command help ethernet and press RETURN to receive more information. 

be%d: No transceiver found! 
The device did not find a transceiver. Check cabling and the transceiver.

be%d: SBus rx error ack 

be%d: SBus tx error ack 
The DMA engine encounted an error which indicates a potential hardware or driver problem.

be%d: SBus rx late error 

be%d: SBus tx late error 

be%d: SBus rx parity error 

be%d: SBus tx parity error 
The DMA engine encounted an error which typically indicates a hardware problem.

be%d: bechanstop: global reset failed 

be%d: bechanstop: qec init failed 

be%d: bechanstop: TDMD did not clear 
These errors indicate a hardware failure. The BE device is most likely bad. 

be%d: bqeallocthings: Not enough system memory 

be%d: bqeattach: Not enough system memory 
The driver cannot allocate sufficient memory for resources. These messages occur when attempting to load the driver. You will be unable to load the driver until sufficient memory becomes free. Terminating unnecessary processes or unloading unused drivers are ways to free memory.

be%d: bqeallocthings: berpending and qerpending are too large 
The values for the berpending and qerpending combined are too large. This should not happen unless you try to adjust these values. Reduce the values until the driver will load.

be%d: bqeread: mbuf alloc failed 
There is a resource shortage in the operating system most likely due to the system being too busy. As a result, a received packet has been dropped. This condition should be transitory.

be%d: beinit failed:  out of buffers 
The driver could not allocate enough receive buffers for the interface. The interface will not be usable.

be%d: beinit: unit not on the list 

be%d: bestart: unit not on the list 
An invalid device unit number was passed into the specified routine. This error is usually symptomatic of trouble elsewhere in the operating system.

be%d: map_regs for qec per-channel reg failed 

be%d: map_regs for bmac reg failed 

be%d: map_regs for bmac transceiver reg failed 

be%d: mb_nmapalloc for QMD and buffers failed 
The driver cannot allocate sufficient address space for resources. These messages occur when attempting to load the driver. You will be unable to load the driver until sufficient address space becomes free. Unloading unused drivers is one way to free up address space.

be%d: out of tmds - packet dropped 
The driver has run out of transmit message descriptors needed to queue a packet to the device and discarded the packet. This error usually indicates that the upper protocol layers are generating packets faster than the driver can transmit them on the Ethernet and is usually self-correcting.

be%d: pkt missed/drop error 
The device has dropped an incoming packet because it had no buffer space for it. This is most likely due to the driver being under a heavy networking load.

be%d: rx crc error 
The driver has received a packet with an incorrect checksum field.

be%d: rx fifo overflow 
Indicates that the device receive FIFO has overflowed. This is most likely due to the system being under a heavy load.

be%d: rx framing/alignment error 
The driver has received a packet containing a noninteger multiple of eight bits and there was a CRC error.

be%d: rx late collision error  
A packet collision has occurred after the channel’s slot time has elapsed. This error usually indicates faulty hardware elsewhere on the net.

be%d: rx pkt buff error 
Indicates that the buffer posted to the device was smaller than the actual packet received. This error is usually symptomatic of trouble in the operating system or driver.

be%d: rxmac did not reset 
Cannot reset the receiver state machine. This is most likely due to a bad BE device. 

be%d: tx chained packet descriptor error 
The DMA engine encounted a packet that it did not own during the transmission of a chained packet. This indicates a problem in the driver. The device will reset itself and continue normal operation.

be%d: tx babble 
A packet larger than 1518 bytes was passed to the device. This indicates an error in the driver.

be%d: tx fifo underflow 
Indicates that the device transmit FIFO has underflowed. This is most likely due to the system being under a heavy load.

be%d: tx jabber 
Indicates that the device attempted to transmit for an excessive time period. This is most likely due to a bad BE device or transceiver. 

be%d: tx late collision error  
A packet collision has occurred after the channel’s slot time has elapsed. This error usually indicates faulty hardware elsewhere on the net.

be%d: tx retry error 
The driver tried to retransmit the packet 16 times without any success. The packet is dropped. This could be caused by a bad cable, bad transceiver, or a very busy network.

be%d: txmac did not reset 
Cannot reset the transmitter state machine. This is most likely due to a bad BE device. 

bqeattach: bad number of regs %d 
The SBus card has reported an invalid number of device registers. The BE device may be bad, or there may be a problem in the operating system or driver. 

bqeattach: driver has no parent 
The driver doesn’t have a parent driver. This error is usually symptomatic of trouble elsewhere in the operating system.

Sun Release 4.1  —  Last change: 31 July 1994