The following messages originate from the QEC/MACE Ethernet device driver:
------------------------------------------
qe%d: Cannot free unit -- still running\ \ ------------------------------------------
An attempt was made to unload the driver when the interface was still up. Use ifconfig qe<num down to bring the interface down before unloading the driver.
---------------------------------------
qe%d: Cannot reset channel register\ \& ---------------------------------------
and
------------------------------------
qe%d: Cannot reset mace register\ \& ------------------------------------
Cannot reset the device. This is most likely due to a bad device.
-------------------------------------------------------------
qe%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 SPARC system.
If the link test is enabled in the hub while the link integrity test is disabled in the SPARC system, the SPARC system 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 SPARC system.
To enable/disable the link test in the SPARC system, see eeprom (8S). To enable/disable the link test in the SPARC system at the OBP' ok prompt, enter the OBP command help ethernet and press RETURN to receive more information.
---------------------------
qe%d: SBus rx error ack\ \& ---------------------------
and
---------------------------
qe%d: SBus tx error ack\ \& ---------------------------
The DMA engine encountered an error which indicates a potential hardware or driver problem.
---------------------------
qe%d: SBus rx late rror\ \& ---------------------------
----------------------------
qe%d: SBus tx late error\ \& ----------------------------
---------------------------
qe%d: SBus rx late rror\ \& ---------------------------
and
------------------------------
qe%d: SBus tx parity error\ \& ------------------------------
The DMA engine encounted an error which typically indicates a hardware problem.
--------------------------------------------------
qe%d: bqeallocthings: Not enough system memory\ \& --------------------------------------------------
and
---------------------------------------------
qe%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.
-----------------------------------------------------------------
qe%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.
------------------------------------
qe%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.
-------------------------------------------------
qe%d: map_regs for qec per-channel reg failed\ \& -------------------------------------------------
--------------------------------------
qe%d: map_regs for mace reg failed\ \& --------------------------------------
and
-------------------------------------------------
qe%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.
--------------------------------------
qe%d: out of tmds - packet dropped\ \& --------------------------------------
The driver has run out of transmit message descriptor 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.
-------------------------------
qe%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.
----------------------------------------
qe%d: qeinit failed: out of buffers\ \& ----------------------------------------
The driver could not allocate enough receive buffers for the interface. The interface will not be usable.
--------------------------------------
qe%d: qeinit: unit not on the list\ \& --------------------------------------
and
---------------------------------------
qe%d: qestart: 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.
----------------------
qe%d: rx crc error\ \& ----------------------
The driver has received a packet with an incorrect checksum field.
--------------------------
qe%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.
--------------------------
qe%d: rx framing error\ \& --------------------------
The driver has received a packet containing a noninteger multiple of eight bits and there was a CRC error.
---------------------------------
qe%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.
---------------------------
qe%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.
------------------------------------------
%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.
-------------------
qe%d: tx babble\ \& -------------------
A packet larger than 1518 bytes was passed to the device. This indicates an error in the driver.
----------------------------------
qe%d: tx excessive defer error\ \& ----------------------------------
Indicates that the MACE had to wait a long time for the network before being able to transmit the packet. This usually indicates a very busy network.
---------------------------
qe%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.
-------------------
qe%d: tx jabber\ \& -------------------
Indicates that the device attempted to transmit for an excessive time period. This is most likely due to a bad device or transceiver.
---------------------------------
qe%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.
------------------------
qe%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.
------------------------------------------
qe%d: bqeattach: bad number of regs %d\ \& ------------------------------------------
The SBus card has reported an invalid number of device registers. The QE device may be bad, or there may be a problem in the operating system or driver.
-----------------------------------------
qe%d: 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.
The following messages originate from the QEC Bus Nexus device driver:
--------------------------------
qec%d: Bad number of regs %d\ \& --------------------------------
The SBus card has reported an invalid number of device registers. The QEC device is most likely bad.
-------------------------------
qec%d: Driver has no parent\ \& -------------------------------
The driver doesn't have a parent driver. This error is usually symptomatic of trouble elsewhere in the operating system.
--------------------------------------------
qec%d: Failed to get driver private data\ \& --------------------------------------------
The QEC initialization function could not recover its private data. This error is usually symptomatic of trouble in the operating system or driver. QEC device is most likely bad.
------------------------------
qec%d: Global reset failed\ \& ------------------------------
Could not reset the QEC device. The QEC device is most likely bad.
--------------------------------
qec%d: Missing reg property!\ \& --------------------------------
The devices register property is missing. The device is most likely bad.
----------------------------------------
qec%d: Not all children are detached\ \& ----------------------------------------
An attempt was made to unload the driver before unloading the children's drivers. First unload the BE and the QE device drivers before trying to unload the QEC device driver.
------------------------------------------------
qec%d: Not used - SBus slot %d is slave-only\ \& ------------------------------------------------
The SBus card has been installed into a slot that cannot be used by a DMA master. Move the SBus card to another slot.
--------------------------------------
qec%d: Unknown chip identification\ \& --------------------------------------
Driver does not know what type of MACE chip is being used. Upgrading the driver may eliminate this error.
--------------------------
qec%d: map_regs failed\ \& --------------------------
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.
