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

ne(4) Kernel Interfaces Manual ne(4)

Name
ne - Second Generation Ethernet Chip Interface

Syntax
device ne0 at ibus? vector neintr

Description
The interface provides access to a 10 Mb/s Ethernet network through the Digital's Second Generation Ethernet Chip (SGEC) based controller.

The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl. The interface employs the address resolution protocol
described in to map dynamically between Internet and Ethernet addresses on the local network.

The driver normally tries to use a trailer encapsulation to minimize copying data on input and output. This can be disabled for an inter-
face by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. Trailers are only used for packets destined for Internet hosts.

The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and the SIOCRPHYSADDR ioctl can be used to read its phys-
ical address.

The SIOCADDMULTI and SIOCDELMULTI ioctls can be used to add or delete multicast addresses. The recognizes a maximum of 16 multicast
addresses.

The SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear the Ethernet driver counters. The argument to these two ioctls
is a pointer to a counter structure, found in

The SIOCENABLBACK and SIOCDISABLBACK ioctls can be used to enable and disable the interface loopback mode respectively.

Diagnostics
The diagnostic error messages contain relevant information provided by the driver. For example,

ne%d: self test failed <reason lists>
Adapter did not pass the power-up self-test during autoconfiguration time.

ne%d: write CSR0 failed
The driver was unable to set the initial value for the adapter.

ne%d: couldn't allocate ......
The driver was unable to allocate memory for the internal data structures. ne%d: can't handle af%d
The interface was handed a message with addresses formated in an unsuitable address family, and the packet was dropped.

ne%d: memory error (MERR)
A host memory problem or a memory parity error has occurred.

ne%d: SIOCADDMULTI fail, multicast list full
Too many multicast requests have been made.

Linux and UNIX Man Pages

hy(4) [bsd man page]

Check Out this Related Man Page