2.11BSD#431 - /usr/man/cat4/hy.0

HY(4)		    UNIX Programmer's Manual		    HY(4)


NAME
     hy - Network Systems Hyperchannel interface

SYNOPSIS
     /sys/conf/SYSTEM:
	  NHY  hy_controllers # Hyperchannel

DESCRIPTION
     The hy interface provides access to a Network Systems Cor-
     poration Hyperchannel Adapter.

     The network to which the interface is attached is specified
     at boot time with an SIOCSIFADDR ioctl. The host's address
     is discovered by reading the adapter status register.  The
     interface will not transmit or receive packets until the
     network number is known.

DIAGNOSTICS
     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 dropped.

     hy%d: can't initialize.  The interface was unable to allo-
     cate 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 hardware.

     hy%d:  BAR overflow.  Bus address register overflow error
     returned from hardware.

     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.  Shouldn't happen.


Printed 11/26/99	 August 20, 1987			1


HY(4)		    UNIX Programmer's Manual		    HY(4)


     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 ALSO
     intro(4N), inet(4F)

BUGS
     If the adapter does not respond to the status command issued
     during autoconfigure, the adapter is assumed down.  A reboot
     is required to recognize it.

     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.


Printed 11/26/99	 August 20, 1987			2