Carrier Loss PHY Resets
Increments every time the driver resets the PHY as a result of carrier sense
loss.
Checksum Good
Increments every time a packet that has a valid checksum is received.
Checksum Bad
Increments every time a packet that does not have a valid checksum is received.
Current IFS Value
Current Inter Frame Spacing (IFS) value. Higher value indicates
higher collisions and can lessen throughput.
Current Threshold
To lessen underruns, the software can change the wait time before
starting to transfer data onto the hardware buffers. The higher the number, the
more time the adapter waits before starting to transmit data onto the wire. Poor
bus performance, high traffic, or many devices on the same bus can cause this to
rise. If this number is always above 170, consider loading the driver with the
TXThreshold parameter set to something high, like 200.
Duplex
Holds the current duplex, as read directly from the PHY or general status
register of the 82559-based adapter. The duplex values are:
Flow Control RX Pause
Number of Flow Control frames received by the adapter. Includes both the
XOFF and XON frames received.
Flow Control TX Pause
Number of Flow Control frames transmitted by the adapter. Includes both the XOFF
and XON frames transmitted.
Flow Control Unsupported
Number of MAC Control frames received that are not Flow Control Pause frames.
These frames are valid MAC control frames that have the predefined MAC control
Type value and a valid address, but they contain an unsupported op-code.
Link Status
The link status, as read from the PHY or general status register of the
82559-based adapter. Updated once per second. If link detection is not supported,
the value is 2. A value of 0 is link up, 1 is link down.
REC
Keeps track of receive situations that are unexpected. Increments when the RU is in a state unrecognized by the software, or if the receive resource lists get out of sync. Used for software development use only. Normal to be non-zero.
RstartCnt
Also known as RSC, it stands for Re-Start Count. Keeps track of every time the Receive Path is reset. This includes any time the RU is restarted. Normal to be non-zero.
Rx Alignment Errors
Number of frames that are both misaligned and contain a CRC error.
Rx Collision Detect Errors
Number of frames that encountered collisions during frame reception.
Rx Crc Errors
Number of aligned frames discarded because of a CRC error. CRC Errors are
usually caused by late collisions in which another station has sent data in the
middle of a frame. This number should be very low.
Rx Dma Overrun Errors
Number of frames known to be lost because the device's internal receive FIFO
overflowed. This can occur if the device is unable to get the necessary
bandwidth on the system (PCI) bus. If the overflow condition persists for more
than one frame, the frames that follow the first could also be lost. Remedies: a
faster bus machine or fewer devices on the bus.
Rx Good Frames
Number of frames that were received properly from the link. Updated only after
the actual reception from the link is completed and all the data bytes are
stored in memory.
Rx No Resources Errors
Number of good frames discarded because there were no resources available.
Frames intended for a host whose Receive Unit is in the No Resources state fall
into this category. Can be reduced by increasing the number of receive buffers
or increasing the performance of the host machines processing power.
Rx Short Frame Errors
Number of received frames that are shorter than the minimum frame length.
Current Speed
Holds the current speed, as read directly from the PHY or general status
register of the 82559-based adapter. Value of 0 = Speed is not supported or not
available (usually due to unsupported chip type or absent link), 10 = 10 Mbps,
100 = 100 Mbps.
Stalled Ints SW Resets
Increments every time the driver issues a complete reset (to the driver and to
the adapter) as a result of a stalled interrupt situation. A stalled interrupt
situation is detected by the driver if there are no interrupts for a long time
and a SW interrupt issued by the driver fails to arrive.
Hardware Status
Holds the current internal status of the driver and chip as maintained by the
driver.
| Value | Short Name | Long Description |
| 1 | ISSUE CBA WAIT ERROR | A command was issued to the chip, and it was not accepted. |
| 2 | SELECT PHY ERROR | A PHY could not be selected or did not accept a command. |
| 3 | SETUP PHY ERROR | The PHY code encountered an error during setup. |
| 4 | PHY RESET ERROR | The PHY did not return after a reset command. |
| 5 | MDI WRITE ERROR | An MDI write command did not complete as expected. |
| 6 | MDI READ ERROR | An MDI read command did not complete as expected. |
| 7 | INIT ADAPTER ERROR | During INIT the chip was issued a command which was not accepted during the allotted time. |
TCO Rx Frames
Incremented any time the 82559-based adapter receives a TCO packet. Any
reception of TCO packets also affects the normal receive counters.
TCO Tx Frames
Incremented any time the 82559-based adapter transmits a packet initiated by the
TCO controller (or ICH). Any transmission of TCO packets also affects the normal
transmit counters.
Tx Frames Deferred
Number of frames that were deferred transmission due to activity on the link.
This is a normal condition in a busy network and can grow quite large.
Tx Dynamic Chaining Count
Performance evaluation counter. Currently not used.
Tx Good Frames
Number of frames that were transmitted properly on the link. Varies in
accordance with the amount of frames sent and can reach billions very quickly.
Tx Late Collisions
Number of frames that were not transmitted since they encountered a collision
outside the normal collision window. Very rare; indicates problem with cables,
distance, or duplex mismatch.
Tx Lost Carrier Sense
Number of frames that were encountered by the device despite the fact that it
detected loss of link during the transmission.
Tx Maximum Collisions
Number of frames that were not transmitted since they encountered the configured
maximum number of collisions (16). This value should only increase on saturated
network. Fix: segment network.
Tx OK with Multiple Collisions
Number of transmitted frames that encountered more than one collision. This only
gets incremented once, even though one frame made have had several collisions
before being successfully sent. Fix: segment network or increase IFS.
Tx OK with Single Collisions
Number of transmitted frames that encountered one, and only one, collision
before being successfully sent. Normal in busy networks.
Tx Total Collisions
Total number of collisions that were encountered while attempting to transmit.
Includes late collisions and max collisions (16).
Tx Timeouts
Debug timer. Currently not used.
Tx DMA Underrun Errors
Number of frames that were either not transmitted or retransmitted due to a Tx
DMA underrun. Occurs because a lack of PCI bandwidth resulting in the Tx FIFO
running dry during the transmission of a frame. Adaptive Tuning should keep this
number under control. To correct, load the driver with TxThreshold=200 on the
command line. See Current Threshold above.
Please read all restrictions and disclaimers.