1HY(4) Kernel Interfaces Manual HY(4)
2
6 hy - Network Systems Hyperchannel interface
7
9 /sys/conf/SYSTEM:
10 NHY hy_controllers # Hyperchannel
11
13 The hy interface provides access to a Network Systems Corporation
14 Hyperchannel Adapter.
15 The network to which the interface is attached is specified at boot
17 time with an SIOCSIFADDR ioctl. The host's address is discovered by
18 reading the adapter status register. The interface will not transmit
19 or receive packets until the network number is known.
20
22 hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identi‐
23 fies the device during autoconfiguration.
24 hy%d: can't handle af%d. The interface was handed a message with
26 addresses formatted in an unsuitable address family; the packet was
27 dropped.
28 hy%d: can't initialize. The interface was unable to allocate UNIBUS
30 resources. This is usually due to having too many network devices on an
31 11/750 where there are only 3 buffered data paths.
32 hy%d: NEX - Non Existent Memory. Non existent memory error returned
34 from hardware.
35 hy%d: BAR overflow. Bus address register overflow error returned from
37 hardware.
38 hy%d: Power Off bit set, trying to reset. Adapter has lost power,
40 driver will reset the bit and see if power is still out in the adapter.
41 hy%d: Power Off Error, network shutdown. Power was really off in the
43 adapter, network connections are dropped. Software does not shut down
44 the network unless power has been off for a while.
45 hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is
47 too big. Probable a driver bug. Shouldn't happen.
48 hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error.
50 Shouldn't happen.
51 hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached
53 a non-existent state. Definite driver bug.
54 hy%d: watchdog timer expired. A command in the adapter has taken too
56 long to complete. Driver will abort and retry the command.
57 hy%d: adapter power restored. Software was able to reset the power off
59 bit, indicating that the power has been restored.
60
62 intro(4N), inet(4F)
63
65 If the adapter does not respond to the status command issued during
66 autoconfigure, the adapter is assumed down. A reboot is required to
67 recognize it.
68 The adapter power fail interrupt seems to occur sporadically when power
70 has, in fact, not failed. The driver will believe that power has
71 failed only if it can not reset the power fail latch after a ``reason‐
72 able'' time interval. These seem to appear about 2-4 times a day on
73 some machines. There seems to be no correlation with adapter rev
74 level, number of ports used etc. and whether a machine will get these
75 ``bogus powerfails''. They don't seem to cause any real problems so
76 they have been ignored.
773rd Berkeley Distribution August 20, 1987 HY(4)