Return to hy.4 CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / man / man4 / man4.vax

Annotation of 43BSDReno/share/man/man4/man4.vax/hy.4, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1983 The Regents of the University of California.
                      2: .\" All rights reserved.
                      3: .\"
                      4: .\" Redistribution and use in source and binary forms are permitted provided
                      5: .\" that: (1) source distributions retain this entire copyright notice and
                      6: .\" comment, and (2) distributions including binaries display the following
                      7: .\" acknowledgement:  ``This product includes software developed by the
                      8: .\" University of California, Berkeley and its contributors'' in the
                      9: .\" documentation or other materials provided with the distribution and in
                     10: .\" all advertising materials mentioning features or use of this software.
                     11: .\" Neither the name of the University nor the names of its contributors may
                     12: .\" be used to endorse or promote products derived from this software without
                     13: .\" specific prior written permission.
                     14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
                     15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
                     16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
                     17: .\"
                     18: .\"    @(#)hy.4        6.3 (Berkeley) 6/23/90
                     19: .\"
                     20: .TH HY 4 "June 23, 1990"
                     21: .UC 5
                     22: .SH NAME
                     23: hy \- Network Systems Hyperchannel interface
                     24: .SH SYNOPSIS
                     25: .B "device hy0 at uba0 csr 0172410 vector hyint"
                     26: .SH DESCRIPTION
                     27: The
                     28: .I hy
                     29: interface provides access to a Network
                     30: Systems Corporation Hyperchannel Adapter.
                     31: .PP
                     32: The network to which the interface is attached
                     33: is specified at boot time with an SIOCSIFADDR ioctl.  
                     34: The host's address is discovered by reading the adapter status
                     35: register.  The interface will not transmit or receive
                     36: packets until the network number is known.
                     37: .SH DIAGNOSTICS
                     38: \fBhy%d: unit number 0x%x port %d type %x microcode level 0x%x\fP.
                     39: Identifies the device during autoconfiguration.
                     40: .PP
                     41: \fBhy%d: can't handle af%d\fP.  The interface was handed
                     42: a message with addresses formatted in an unsuitable address
                     43: family; the packet was dropped.
                     44: .PP
                     45: \fBhy%d: can't initialize\fP.
                     46: The interface was unable to allocate UNIBUS resources. This
                     47: is usually due to having too many network devices on an 11/750
                     48: where there are only 3 buffered data paths.
                     49: .PP
                     50: \fBhy%d: NEX - Non Existent Memory\fP.
                     51: Non existent memory error returned from hardware.
                     52: .PP
                     53: \fBhy%d:  BAR overflow\fP.  Bus address register
                     54: overflow error returned from hardware.
                     55: .PP
                     56: \fBhy%d: Power Off bit set, trying to reset\fP.
                     57: Adapter has lost power, driver will reset the bit
                     58: and see if power is still out in the adapter.
                     59: .PP
                     60: \fBhy%d: Power Off Error, network shutdown\fP.
                     61: Power was really off in the adapter, network
                     62: connections are dropped.
                     63: Software does not shut down the network unless
                     64: power has been off for a while.
                     65: .PP
                     66: \fBhy%d: RECVD MP > MPSIZE (%d)\fP.
                     67: A message proper was received that is too big.
                     68: Probable a driver bug.
                     69: Shouldn't happen.
                     70: .PP
                     71: \fBhy%d: xmit error \- len > hy_olen [%d > %d]\fP.
                     72: Probable driver error.
                     73: Shouldn't happen.
                     74: .PP
                     75: \fBhy%d: DRIVER BUG \- INVALID STATE %d\fP.
                     76: The driver state machine reached a non-existent state.
                     77: Definite driver bug.
                     78: .PP
                     79: \fBhy%d: watchdog timer expired\fP.
                     80: A command in the adapter has taken too long to complete.
                     81: Driver will abort and retry the command.
                     82: .PP
                     83: \fBhy%d: adapter power restored\fP.
                     84: Software was able to reset the power off bit,
                     85: indicating that the power has been restored.
                     86: .SH SEE ALSO
                     87: netintro(4), inet(4)
                     88: .SH BUGS
                     89: If the adapter does not respond to the status command
                     90: issued during autoconfigure, the adapter is assumed down.
                     91: A reboot is required to recognize it.
                     92: .PP
                     93: The adapter power fail interrupt seems to occur
                     94: sporadically when power has, in fact, not failed.
                     95: The driver will believe that power has failed
                     96: only if it can not reset the power fail latch after
                     97: a ``reasonable'' time interval.
                     98: These seem to appear about 2-4 times a day on some machines.
                     99: There seems to be no correlation with adapter
                    100: rev level, number of ports used etc. and whether a
                    101: machine will get these ``bogus powerfails''.
                    102: They don't seem to cause any real problems so they have
                    103: been ignored.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.