Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hy(4) [bsd man page]

HY(4)							     Kernel Interfaces 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 Corporation 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 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 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.

       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.

3rd Berkeley Distribution					  August 20, 1987							     HY(4)

Check Out this Related Man Page

DE(4)							     Kernel Interfaces Manual							     DE(4)

NAME

       de - DEC DEUNA 10 Mb/s Ethernet interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NDE  de_controllers # DEUNA

DESCRIPTION

       The de interface provides access to a 10 Mb/s Ethernet network through a Digital Equipment UNIBUS Network Adapter (DEUNA).

       Each  of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl.  The de 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

       de%d: hardware address %s.  This is a normal autoconfiguration message noting the 6 byte physical ethernet address of the adapter.

       de%d: oerror, flags=%b tdrerr=%b (len=%d).  The hardware indicated an error in transmitting a packet to the cable.  The	status	and  error
       flags are reported.

       de%d: ierror, flags=%b lenerr=%b (len=%d).  The hardware indicated an error in reading a packet from the cable.	The status and error flags
       are reported.

       de%d: can't handle af%d.  The interface was handed a message with addresses formatted in an  unsuitable	address  family;  the  packet  was
       dropped.

       de%d: buffer unavailable.  The interface received more packets than it had buffers allocated to receive them.

       de%d:  address  change failed, csr0=%b csr1=%b.	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 following messages indicate a probable hardware error performing the indicated operation during  autoconfiguration  or  initialization.
       The two control and status registers should indicate the nature of the failure.	See the hardware manual for details.

       de%d: reset failed, csr0=%b csr1=%b.

       de%d: ppcb failed, csr0=%b csr1=%b.

       de%d: read addr failed, csr0=%b csr1=%b.

       de%d: wtring failed, csr0=%b csr1=%b.

       de%d: wtmode failed, csr0=%b csr1=%b.

SEE ALSO

       intro(4N), inet(4F), arp(4P)

3rd Berkeley Distribution					  August 20, 1987							     DE(4)
Man Page