1*47674Scael.\" Copyright (c) 1983, 1991 The Regents of the University of California. 236756Sbostic.\" All rights reserved. 320718Smckusick.\" 443582Strent.\" %sccs.include.redist.man% 520718Smckusick.\" 6*47674Scael.\" @(#)hy.4 6.4 (Berkeley) 03/27/91 736756Sbostic.\" 8*47674Scael.Dd 9*47674Scael.Dt HY 4 vax 10*47674Scael.Os BSD 4.2 11*47674Scael.Sh NAME 12*47674Scael.Nm hy 13*47674Scael.Nd Network Systems Hyperchannel interface 14*47674Scael.Sh SYNOPSIS 15*47674Scael.Cd "device hy0 at uba0 csr 0172410 vector hyint" 16*47674Scael.Sh DESCRIPTION 1720718SmckusickThe 18*47674Scael.Nm hy 1920718Smckusickinterface provides access to a Network 2020718SmckusickSystems Corporation Hyperchannel Adapter. 21*47674Scael.Pp 2220718SmckusickThe network to which the interface is attached 23*47674Scaelis specified at boot time with an 24*47674Scael.Dv SIOCSIFADDR 25*47674Scael.Xr ioctl 2 . 2620718SmckusickThe host's address is discovered by reading the adapter status 2720718Smckusickregister. The interface will not transmit or receive 2820718Smckusickpackets until the network number is known. 29*47674Scael.Sh DIAGNOSTICS 30*47674Scael.Bl -diag 31*47674Scael.It "hy%d: unit number 0x%x port %d type %x microcode level 0x%x." 3220718SmckusickIdentifies the device during autoconfiguration. 33*47674Scael.Pp 34*47674Scael.It hy%d: can't handle af%d. 35*47674ScaelThe interface was handed 3620718Smckusicka message with addresses formatted in an unsuitable address 3720718Smckusickfamily; the packet was dropped. 38*47674Scael.Pp 39*47674Scael.It hy%d: can't initialize. 40*47674ScaelThe interface was unable to allocate 41*47674Scael.Tn UNIBUS 42*47674Scaelresources. This 4320718Smckusickis usually due to having too many network devices on an 11/750 4420718Smckusickwhere there are only 3 buffered data paths. 45*47674Scael.Pp 46*47674Scael.It hy%d: NEX - Non Existent Memory. 4720718SmckusickNon existent memory error returned from hardware. 48*47674Scael.Pp 49*47674Scael.It hy%d: BAR overflow. 50*47674ScaelBus address register 5120718Smckusickoverflow error returned from hardware. 52*47674Scael.Pp 53*47674Scael.It hy%d: Power Off bit set, trying to reset. 5420718SmckusickAdapter has lost power, driver will reset the bit 5520718Smckusickand see if power is still out in the adapter. 56*47674Scael.Pp 57*47674Scael.It hy%d: Power Off Error, network shutdown. 5820718SmckusickPower was really off in the adapter, network 5920718Smckusickconnections are dropped. 6020718SmckusickSoftware does not shut down the network unless 6120718Smckusickpower has been off for a while. 62*47674Scael.Pp 63*47674Scael.It hy%d: RECVD MP > MPSIZE (%d). 6420718SmckusickA message proper was received that is too big. 6520718SmckusickProbable a driver bug. 6620718SmckusickShouldn't happen. 67*47674Scael.Pp 68*47674Scael.It "hy%d: xmit error \- len > hy_olen [%d > %d]." 6920718SmckusickProbable driver error. 7020718SmckusickShouldn't happen. 71*47674Scael.Pp 72*47674Scael.It hy%d: DRIVER BUG \- INVALID STATE %d. 7320718SmckusickThe driver state machine reached a non-existent state. 7420718SmckusickDefinite driver bug. 75*47674Scael.Pp 76*47674Scael.It hy%d: watchdog timer expired. 7720718SmckusickA command in the adapter has taken too long to complete. 7820718SmckusickDriver will abort and retry the command. 79*47674Scael.Pp 80*47674Scael.It hy%d: adapter power restored. 8120718SmckusickSoftware was able to reset the power off bit, 8220718Smckusickindicating that the power has been restored. 83*47674Scael.El 84*47674Scael.Sh SEE ALSO 85*47674Scael.Xr netintro 4 , 86*47674Scael.Xr inet 4 87*47674Scael.Sh HISTORY 88*47674ScaelThe 89*47674Scael.Nm 90*47674Scaelinterface appeared in 91*47674Scael.Bx 4.2 . 92*47674Scael.Sh BUGS 9320718SmckusickIf the adapter does not respond to the status command 9420718Smckusickissued during autoconfigure, the adapter is assumed down. 9520718SmckusickA reboot is required to recognize it. 96*47674Scael.Pp 9720718SmckusickThe adapter power fail interrupt seems to occur 9820718Smckusicksporadically when power has, in fact, not failed. 9920718SmckusickThe driver will believe that power has failed 10020718Smckusickonly if it can not reset the power fail latch after 101*47674Scaela 102*47674Scael.Dq reasonable 103*47674Scaeltime interval. 10420718SmckusickThese seem to appear about 2-4 times a day on some machines. 10520718SmckusickThere seems to be no correlation with adapter 10620718Smckusickrev level, number of ports used etc. and whether a 107*47674Scaelmachine will get these 108*47674Scael.Dq bogus powerfails . 10920718SmckusickThey don't seem to cause any real problems so they have 11020718Smckusickbeen ignored. 111