1.\" Copyright (c) 1983, 1991 The Regents of the University of California. 2.\" All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)hy.4 6.4 (Berkeley) 03/27/91 7.\" 8.Dd 9.Dt HY 4 vax 10.Os BSD 4.2 11.Sh NAME 12.Nm hy 13.Nd Network Systems Hyperchannel interface 14.Sh SYNOPSIS 15.Cd "device hy0 at uba0 csr 0172410 vector hyint" 16.Sh DESCRIPTION 17The 18.Nm hy 19interface provides access to a Network 20Systems Corporation Hyperchannel Adapter. 21.Pp 22The network to which the interface is attached 23is specified at boot time with an 24.Dv SIOCSIFADDR 25.Xr ioctl 2 . 26The host's address is discovered by reading the adapter status 27register. The interface will not transmit or receive 28packets until the network number is known. 29.Sh DIAGNOSTICS 30.Bl -diag 31.It "hy%d: unit number 0x%x port %d type %x microcode level 0x%x." 32Identifies the device during autoconfiguration. 33.Pp 34.It hy%d: can't handle af%d. 35The interface was handed 36a message with addresses formatted in an unsuitable address 37family; the packet was dropped. 38.Pp 39.It hy%d: can't initialize. 40The interface was unable to allocate 41.Tn UNIBUS 42resources. This 43is usually due to having too many network devices on an 11/750 44where there are only 3 buffered data paths. 45.Pp 46.It hy%d: NEX - Non Existent Memory. 47Non existent memory error returned from hardware. 48.Pp 49.It hy%d: BAR overflow. 50Bus address register 51overflow error returned from hardware. 52.Pp 53.It hy%d: Power Off bit set, trying to reset. 54Adapter has lost power, driver will reset the bit 55and see if power is still out in the adapter. 56.Pp 57.It hy%d: Power Off Error, network shutdown. 58Power was really off in the adapter, network 59connections are dropped. 60Software does not shut down the network unless 61power has been off for a while. 62.Pp 63.It hy%d: RECVD MP > MPSIZE (%d). 64A message proper was received that is too big. 65Probable a driver bug. 66Shouldn't happen. 67.Pp 68.It "hy%d: xmit error \- len > hy_olen [%d > %d]." 69Probable driver error. 70Shouldn't happen. 71.Pp 72.It hy%d: DRIVER BUG \- INVALID STATE %d. 73The driver state machine reached a non-existent state. 74Definite driver bug. 75.Pp 76.It hy%d: watchdog timer expired. 77A command in the adapter has taken too long to complete. 78Driver will abort and retry the command. 79.Pp 80.It hy%d: adapter power restored. 81Software was able to reset the power off bit, 82indicating that the power has been restored. 83.El 84.Sh SEE ALSO 85.Xr netintro 4 , 86.Xr inet 4 87.Sh HISTORY 88The 89.Nm 90interface appeared in 91.Bx 4.2 . 92.Sh BUGS 93If the adapter does not respond to the status command 94issued during autoconfigure, the adapter is assumed down. 95A reboot is required to recognize it. 96.Pp 97The adapter power fail interrupt seems to occur 98sporadically when power has, in fact, not failed. 99The driver will believe that power has failed 100only if it can not reset the power fail latch after 101a 102.Dq reasonable 103time interval. 104These seem to appear about 2-4 times a day on some machines. 105There seems to be no correlation with adapter 106rev level, number of ports used etc. and whether a 107machine will get these 108.Dq bogus powerfails . 109They don't seem to cause any real problems so they have 110been ignored. 111