acc(4) [bsd man page]
ACC(4) Kernel Interfaces Manual ACC(4) NAME
acc - ACC LH/DH IMP interface SYNOPSIS
/sys/conf/SYSTEM: NACC 0 # ACC LH/DH ARPAnet IMP interface PLI YES # LH/DH is connected to a PLI DESCRIPTION
The acc device provides a Local Host/Distant Host interface to an IMP. It is normally used when participating in the DARPA Internet. The controller itself is not accessible to users, but instead provides the hardware support to the IMP interface described in imp(4). When configuring, the imp(NIMP) pseudo-device must also be included. DIAGNOSTICS
acc%d: not alive. The initialization routine was entered even though the device did not autoconfigure. This indicates a system problem. acc%d: can't initialize. Insufficient UNIBUS resources existed to initialize the device. This is likely to occur when the device is run on a buffered data path on an 11/750 and other network interfaces are also configured to use buffered data paths, or when it is configured to use buffered data paths on an 11/730 (which has none). acc%d: imp doesn't respond, icsr=%b. The driver attempted to initialize the device, but the IMP failed to respond after 500 tries. Check the cabling. acc%d: stray xmit interrupt, csr=%b. An interrupt occurred when no output had previously been started. acc%d: output error, ocsr=%b, icsr=%b. The device indicated a problem sending data on output. acc%d: input error, csr=%b. The device indicated a problem receiving data on input. acc%d: bad length=%d. An input operation resulted in a data transfer of less than 0 or more than 1008 bytes of data into memory (according to the word count register). This should never happen as the maximum size of a host-IMP message is 1008 bytes. 3rd Berkeley Distribution July 26, 1987 ACC(4)
Check Out this Related Man Page
IL(4) Kernel Interfaces Manual IL(4) NAME
il - Interlan NI1010 10 Mb/s Ethernet interface SYNOPSIS
/sys/conf/SYSTEM: NIL il_controllers # Interlan Ethernet DESCRIPTION
The il interface provides access to a 10 Mb/s Ethernet network through an Interlan 1010 or 1010A controller. Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The il interface employs the address resolution protocol described in arp(4P) to dynamically map between Internet and Ethernet addresses on the local network. The interface normally tries to use a ``trailer'' encapsulation to minimize copying data on input and output. The use of trailers is nego- tiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. DIAGNOSTICS
il%d: input error. The hardware indicated an error in reading a packet off the cable or an illegally sized packet. il%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. il%d: setaddr didn't work. The interface was unable to reprogram its physical ethernet address. This may happen with very early models of the interface. This facility is used only when the controller is not the first network interface configured for XNS. The oldest interface tested (2.7.1.0.1.45) has never failed in this way. The following messages indicate a probable hardware error performing the indicated operation during autoconfiguration or initialization. The status field in the control and status register (the low-order four bits) should indicate the nature of the failure. See the hardware manual for details. il%d: reset failed, csr=%b. il%d: status failed, csr=%b. il%d: hardware diag failed, csr=%b. il%d: verifying setaddr, csr=%b. il%d: stray xmit interrupt, csr=%b. il%d: can't initialize. SEE ALSO
intro(4N), inet(4F), arp(4P) 3rd Berkeley Distribution August 20, 1987 IL(4)