LE(4S)

NAME
le - LANCE 10Mb/s Ethernet interface

CONFIG — SUN-4/3xx, SUN-4/xx SYSTEMS
device le0 at obio ? csr 0xf9000000 priority 3

CONFIG — Desktop SPARCsystems, SPARCsystem 600MP SERIES
device-driver le
device-driver lebuf
device-driver ledma

DESCRIPTION

The le interface provides access to a 10 Mb/s Ethernet network through a controller using the AMD LANCE (Local Area Network Controller for Ethernet) Am7990 chip. For a general description of network interfaces see if(4N). The lebuf and ledma device drivers, when present, support hardware-specific buffering and DMA for each le interface.

DIAGNOSTICS

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: out of tmds - packet dropped
    The driver has run out of transmit message descriptors needed to queue a packet to the LANCE 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.

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

le%d: RINT with buffer owned by chip
    The LANCE has generated a receive interrupt but the driver finds no packets have been received. This causes the driver to reinitialize the chip.

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

le%d: Receive: overflow error
    Indicates that the receiver has lost all or part of an incoming packet due to an inability to store the packet in a memory buffer before the LANCE internal silo overflowed.

le%d: Receive: BUFF 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: Receive: framming error
    The driver has received a packet containing a noninteger multiple of eight bits and there was a CRC error.

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

le%d: Receive: STP in rmd cleared
    The driver has received a packet that straddles multiple receive buffers and therefore consumes more than one of the LANCE chip's receive descriptors. Provided that all stations on the Ethernet are operating according to the Ethernet specification, this error “should never happen,” since the driver 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.

le%d: Receive: ENP in rmd cleared
    The driver has received a packet that straddles multiple receive buffers and therefore consumes more than one of the LANCE chip's receive descriptors. Provided that all stations on the Ethernet are operating according to the Ethernet specification, this error “should never happen,” since the driver allocates its receive buffers to be large enough to hold packets of the largest permitted size. The most likely cause of the message is that some other station on the net is transmitting packets whose lengths exceed the maximum permitted for Ethernet.

le%d: Transmit: BUFF 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 underflow
    The transmitter has truncated a packet due to data late from memory.

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: No carrier - twisted pair cable problem or hub link test disabled?
    SPARCstation 10 system only.

    The LANCE chip has lost input to its carrier detect pin while trying to transmit a packet.

    The TPE (Twisted-Pair Ethernet) in the SPARCstation 10 system has a test feature that verifies the Ethernet cable connection between the SPARCstation 10 system 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 SPARCstation 10 system.

    If the link test is enabled in the hub while the link integrity test is disabled in the SPARCstation 10 system, the SPARCstation 10 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 SPARCstation 10 system.

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

le%d: Transmit retried more than 16 times - net jammed
    Network activity has become so intense that sixteen successive transmission attempts failed, the LANCE chip gave 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 (1518 bytes). This error indicates a kernel bug.

le%d: Memory Error!
    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 reinitialized.

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