string
string
string
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Technical Notes<br />
This error is returned to processes that resume execution after the removal of an<br />
identifier from the file system’s name space. See msgctl(2), semctl(2), and<br />
shmctl(2) for details.<br />
The symbolic name for this error is EIDRM, errno=36.<br />
ie0: Ethernet jammed<br />
Cause<br />
This message can appear on SPARCservers or x86 machines with an Intel 82586<br />
Ethernet chip. It indicates that 16 successive transmission attempts failed, causing the<br />
driver to give up on the current packet.<br />
Action<br />
If this error occurs sporadically or at busy times, it probably means that the network<br />
is saturated. Wait for network traffic to clear. If bottlenecks arise frequently, think<br />
about reconfiguring the network or adding subnets.<br />
Another possible cause of this message is a noise source somewhere in the network,<br />
such as a loose transceiver connection. Use snoop(1M) or a similar program to<br />
isolate the problem area, then check and tighten network connectors as necessary.<br />
ie0: no carrier<br />
Cause<br />
This message can appear on SPARCservers or x86 machines with an Intel 82586<br />
Ethernet chip. It indicates that the chip has lost input to its carrier detect pin while<br />
trying to transmit a packet, causing the packet to be dropped.<br />
Action<br />
Check that the Ethernet connector is not loose or disconnected. Other possible causes<br />
include an open circuit somewhere in the network and noise on the carrier detect<br />
line from the transceiver. Use snoop(1M) or a similar program to isolate the<br />
problem area, then check the network connectors and transceivers, as needed.<br />
Alphabetical Message Listing 81