HY(4) BSD/vax Kernel Interfaces Manual HY(4)NAMEhy — Network Systems Hyperchannel interface
device hy0 at uba0 csr 0172410 vector hyint
The hy interface provides access to a Network Systems Corporation Hyper‐
The network to which the interface is attached is specified at boot time
with an SIOCSIFADDR ioctl(2). The host's address is discovered by read‐
ing the adapter status register. The interface will not transmit or
receive packets until the network number is known.
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies
the device during autoconfiguration.
hy%d: can't handle af%d. The interface was handed a message with
addresses formatted in an unsuitable address family; the packet was
hy%d: can't initialize. The interface was unable to allocate UNIBUS
resources. This is usually due to having too many network devices on an
11/750 where there are only 3 buffered data paths.
hy%d: NEX - Non Existent Memory. Non existent memory error returned from
hy%d: BAR overflow. Bus address register overflow error returned from
hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver
will reset the bit and see if power is still out in the adapter.
hy%d: Power Off Error, network shutdown. Power was really off in the
adapter, network connections are dropped. Software does not shut down
the network unless power has been off for a while.
hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too
big. Probable a driver bug. Shouldn't happen.
hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error.
hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a
non-existent state. Definite driver bug.
hy%d: watchdog timer expired. A command in the adapter has taken too
long to complete. Driver will abort and retry the command.
hy%d: adapter power restored. Software was able to reset the power off
bit, indicating that the power has been restored.
SEE ALSOnetintro(4), inet(4)HISTORY
The hy interface appeared in 4.2BSD.
If the adapter does not respond to the status command issued during auto‐
configure, the adapter is assumed down. A reboot is required to recog‐
The adapter power fail interrupt seems to occur sporadically when power
has, in fact, not failed. The driver will believe that power has failed
only if it can not reset the power fail latch after a “reasonable” time
interval. These seem to appear about 2-4 times a day on some machines.
There seems to be no correlation with adapter rev level, number of ports
used etc. and whether a machine will get these “bogus powerfails”. They
don't seem to cause any real problems so they have been ignored.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution