18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

le0: Memory error!<br />

Cause<br />

This message indicates that the network interface encountered an access time-out<br />

from the CPU’s main memory. There is probably nothing wrong except system<br />

overload.<br />

Action<br />

If the system is busy with other processes, this error can occur frequently. If possible,<br />

try to reduce the system load by quitting applications or killing some processes.<br />

Technical Notes<br />

The Lance Ethernet chip timed out while trying to acquire the bus for a DVMA<br />

transfer. Most network applications wait for a transfer to occur, so generally no data<br />

gets lost. However, data transfer might fail after too many time-outs.<br />

See Also<br />

For more information about the Lance Ethernet chip, see the le(7D) man page.<br />

le0: No carrier-- cable disconnected<br />

or hub link test disabled?<br />

Cause<br />

Standalone machines with no Ethernet port connection get this error when the system<br />

tries to access the network. If the Ethernet cable is disconnected, SPARC machines<br />

with the sun4m architecture usually display this message, whereas machines with<br />

the sun4c architecture usually display the "le0: No carrier– transceiver cable problem"<br />

message instead. If the Ethernet cable is connected, this message could result from a<br />

mismatch between the machine’s NVRAM settings and the Ethernet hub settings.<br />

Action<br />

If this message is continuous, try to save any work to local disk.<br />

Alphabetical Message Listing 99

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!