HY(4) BSD Programmer's Manual (VAX Architecture) HY(4)
h
\bhy
\by - Network Systems Hyperchannel interface
S
\bSY
\bYN
\bNO
\bOP
\bPS
\bSI
\bIS
\bS
d
\bde
\bev
\bvi
\bic
\bce
\be h
\bhy
\by0
\b0 a
\bat
\bt u
\bub
\bba
\ba0
\b0 c
\bcs
\bsr
\br 0
\b01
\b17
\b72
\b24
\b41
\b10
\b0 v
\bve
\bec
\bct
\bto
\bor
\br h
\bhy
\byi
\bin
\bnt
\bt
D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
The h
\bhy
\by interface provides access to a Network Systems Corporation Hyper-
The network to which the interface is attached is specified at boot time
with an SIOCSIFADDR ioctl(2). The host's address is discovered by read-
ing the adapter status register. The interface will not transmit or re-
ceive packets until the network number is known.
D
\bDI
\bIA
\bAG
\bGN
\bNO
\bOS
\bST
\bTI
\bIC
\bCS
\bS
h
\bhy
\by%
\b%d
\bd:
\b: u
\bun
\bni
\bit
\bt n
\bnu
\bum
\bmb
\bbe
\ber
\br 0
\b0x
\bx%
\b%x
\bx p
\bpo
\bor
\brt
\bt %
\b%d
\bd t
\bty
\byp
\bpe
\be %
\b%x
\bx m
\bmi
\bic
\bcr
\bro
\boc
\bco
\bod
\bde
\be l
\ble
\bev
\bve
\bel
\bl 0
\b0x
\bx%
\b%x
\bx.
\b. Identifies
the device during autoconfiguration.
h
\bhy
\by%
\b%d
\bd:
\b: c
\bca
\ban
\bn'
\b't
\bt h
\bha
\ban
\bnd
\bdl
\ble
\be a
\baf
\bf%
\b%d
\bd.
\b. The interface was handed a message with ad-
dresses formatted in an unsuitable address family; the packet was
h
\bhy
\by%
\b%d
\bd:
\b: c
\bca
\ban
\bn'
\b't
\bt i
\bin
\bni
\bit
\bti
\bia
\bal
\bli
\biz
\bze
\be.
\b. The interface was unable to allocate UNIBUS re-
sources. This is usually due to having too many network devices on an
11/750 where there are only 3 buffered data paths.
h
\bhy
\by%
\b%d
\bd:
\b: N
\bNE
\bEX
\bX -
\b- N
\bNo
\bon
\bn E
\bEx
\bxi
\bis
\bst
\bte
\ben
\bnt
\bt M
\bMe
\bem
\bmo
\bor
\bry
\by.
\b. Non existent memory error returned from
h
\bhy
\by%
\b%d
\bd:
\b: B
\bBA
\bAR
\bR o
\bov
\bve
\ber
\brf
\bfl
\blo
\bow
\bw.
\b. Bus address register overflow error returned from
h
\bhy
\by%
\b%d
\bd:
\b: P
\bPo
\bow
\bwe
\ber
\br O
\bOf
\bff
\bf b
\bbi
\bit
\bt s
\bse
\bet
\bt,
\b, t
\btr
\bry
\byi
\bin
\bng
\bg t
\bto
\bo r
\bre
\bes
\bse
\bet
\bt.
\b. Adapter has lost power, driver
will reset the bit and see if power is still out in the adapter.
h
\bhy
\by%
\b%d
\bd:
\b: P
\bPo
\bow
\bwe
\ber
\br O
\bOf
\bff
\bf E
\bEr
\brr
\bro
\bor
\br,
\b, n
\bne
\bet
\btw
\bwo
\bor
\brk
\bk s
\bsh
\bhu
\but
\btd
\bdo
\bow
\bwn
\bn.
\b. 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.
h
\bhy
\by%
\b%d
\bd:
\b: R
\bRE
\bEC
\bCV
\bVD
\bD M
\bMP
\bP >
\b> M
\bMP
\bPS
\bSI
\bIZ
\bZE
\bE (
\b(%
\b%d
\bd)
\b).
\b. A message proper was received that is too
big. Probable a driver bug. Shouldn't happen.
h
\bhy
\by%
\b%d
\bd:
\b: x
\bxm
\bmi
\bit
\bt e
\ber
\brr
\bro
\bor
\br -
\b- l
\ble
\ben
\bn >
\b> h
\bhy
\by_
\b_o
\bol
\ble
\ben
\bn [
\b[%
\b%d
\bd >
\b> %
\b%d
\bd]
\b].
\b. Probable driver error.
h
\bhy
\by%
\b%d
\bd:
\b: D
\bDR
\bRI
\bIV
\bVE
\bER
\bR B
\bBU
\bUG
\bG -
\b- I
\bIN
\bNV
\bVA
\bAL
\bLI
\bID
\bD S
\bST
\bTA
\bAT
\bTE
\bE %
\b%d
\bd.
\b. The driver state machine reached a
non-existent state. Definite driver bug.
h
\bhy
\by%
\b%d
\bd:
\b: w
\bwa
\bat
\btc
\bch
\bhd
\bdo
\bog
\bg t
\bti
\bim
\bme
\ber
\br e
\bex
\bxp
\bpi
\bir
\bre
\bed
\bd.
\b. A command in the adapter has taken too
long to complete. Driver will abort and retry the command.
h
\bhy
\by%
\b%d
\bd:
\b: a
\bad
\bda
\bap
\bpt
\bte
\ber
\br p
\bpo
\bow
\bwe
\ber
\br r
\bre
\bes
\bst
\bto
\bor
\bre
\bed
\bd.
\b. Software was able to reset the power off
bit, indicating that the power has been restored.
S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
H
\bHI
\bIS
\bST
\bTO
\bOR
\bRY
\bY
The h
\bhy
\by interface appeared in 4.2BSD.
If the adapter does not respond to the status command issued during auto-
configure, the adapter is assumed down. A reboot is required to recog-
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.
4.2 Berkeley Distribution June 5, 1993 2
projects / unix-history / blob