1SRI(4)                     Kernel Interfaces Manual                     SRI(4)
2
3
4

NAME

6       sri - DR11-C IMP interface
7

SYNOPSIS

9       /sys/conf/SYSTEM:
10            NSRI sri_controllers     # SRI DR11c ARPAnet IMP
11

DESCRIPTION

DIAGNOSTICS
14       sri%d:  not  alive.  The initialization routine was entered even though
15       the device did not autoconfigure.  This indicates a system problem.
16
17       sri%d: can't initialize.  Insufficient UNIBUS resources existed to ini‐
18       tialize  the device.  This is likely to occur when the device is run on
19       a buffered data path on an 11/750 and other network interfaces are also
20       configured  to use buffered data paths, or when it is configured to use
21       buffered data paths on an 11/730 (which has none).
22
23       sri%d: imp doesn't respond, ibf=%b.  The driver attempted to initialize
24       the  device,  but  the  IMP failed to respond after 5 tries.  Check the
25       cabling.
26
27       sri%d: stray xmit interrupt, csr=%b.  An  interrupt  occurred  when  no
28       output had previously been started.
29
30       sri%d:  output  error,  csr=%b.  The device indicated a problem sending
31       data on output.
32
33       sri%d: input error, ibf=%b.  The device indicated a  problem  receiving
34       data on input.
35
36       sri%d:  bad  length=%d.  An input operation resulted in a data transfer
37       of less than 10 or more than 1008 bytes of data into memory  (according
38       to  the  word count register).  This should never happen as the maximum
39       size of a host-IMP message is 1018 bytes.
40
41
42
433rd Berkeley Distribution       August 20, 1987                         SRI(4)



        

    


            
        

        

            Impressum