IE(4S) — DEVICES AND NETWORK INTERFACES
NAME
ie − Intel 10 Mb/s Ethernet interface
CONFIG — SUN-4 SYSTEM
device ie0 at obio ? csr 0x6000000 priority 3
device ie1 at vme24d16 ? csr 0xe88000 priority 3 vector ieintr 0x75
CONFIG — SUN-3x SYSTEM
device ie0 at obio ? csr 0x65000000 priority 3
device ie1 at vme24d16 ? csr 0xe88000 priority 3 vector ieintr 0x75
CONFIG — SUN-3 SYSTEM
device ie0 at obio ? csr 0xc0000 priority 3
device ie1 at vme24d16 ? csr 0xe88000 priority 3 vector ieintr 0x75
device ie0 at vme24d16 ? csr 0x31ff02 priority 3 vector ieintr 0x74
CONFIG — SUN-2 SYSTEM
device ie0 at obio 2 csr 0x7f0800 priority 3
device ie1 at vme24 ? csr 0xe88000 priority 3 vector ieintr 0x75
device ie0 at mbmem ? csr 0x88000 priority 3
device ie1 at mbmem ? csr 0x8c000 flags 2 priority 3
CONFIG — SUN386i SYSTEM
device ie0 at obmem ? csr 0xD0000000 irq 21 priority 3
DESCRIPTION
The ie interface provides access to a 10 Mb/s Ethernet network through the Intel 82586 controller chip. For a general description of network interfaces see if(4N).
The first Sun-4 and Sun-3x lines above specify CPU-board-resident Intel Ethernet interfaces; the second Sun-4 and Sun-3x lines specify Multibus Intel Ethernet interfaces for use with VME adapters.
In the Sun-3 lines above, the first line specifies the CPU-board-resident Intel Ethernet interface. The second line specifies a Multibus Intel Ethernet interface for use with a VME adapter. The third line specifies the Intel Ethernet interface present on a Sun-3 Eurocard board.
In the Sun-2 lines above, the first line specifies the CPU-board-resident Intel Ethernet interface on a Sun-2/50 or Sun-2/160 system. The second line specifies a Multibus Intel Ethernet controller for use with a VME adapter on these systems. The third line specifies the first Multibus Intel Ethernet controller for a Sun-2/120 or Sun-2/170 system. The fourth line specifies the second such controller for these systems.
The Sun386i line above specifies the CPU-board-resident Intel Ethernet interface.
SEE ALSO
DIAGNOSTICS
There are too many driver messages to list them all individually here. Some of the more common messages and their meanings follow.
ie%d: Ethernet jammed
Network activity has become so intense that sixteen successive transmission attempts failed, and the 82586 gave up on the current packet. Another possible cause of this message is a noise source somewhere in the network, such as a loose transceiver connection.
ie%d: no carrier
The 82586 has lost input to its carrier detect pin while trying to transmit a packet, causing the packet to be dropped. Possible causes include an open circuit somewhere in the network and noise on the carrier detect line from the transceiver.
ie%d: lost interrupt: resetting
The driver and 82586 chip have lost synchronization with each other. The driver recovers by resetting itself and the chip.
ie%d: iebark reset
The 82586 failed to complete a watchdog timeout command in the allotted time. The driver recovers by resetting itself and the chip.
ie%d: WARNING: requeueing
The driver has run out of resources while getting a packet ready to transmit. The packet is put back on the output queue for retransmission after more resources become available.
ie%d: panic: scb overwritten
The driver has discovered that memory that should remain unchanged after initialization has become corrupted. This error usually is a symptom of a bad 82586 chip.
ie%d: giant packet
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 this message is that some other station on the net is transmitting packets whose lengths exceed the maximum permitted for Ethernet.
Sun Release 4.0 — Last change: 25 March 1989