NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 16 259
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
8090 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While the link was connected and working, the driver received
an interrupt from the PHY chip on the adapter card and passed that to
a lower level, but the lower level returned an error (“Cause” = 32-bit
status from the call to vg_isr_call_phy_state_machine). Probably
the link has unexpectedly disconnected.
ACTION: This informational error is typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
8120 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: During a link connect attempt, an interval timer used to control
the PHY chip on the adapter card popped and the driver passed that to
a lower level, but the lower level returned an error (in older software,
“Cause” is not used here; otherwise “Cause” = 32-bit status from the call
to vg_isr_call_phy_state_machine).
ACTION: This informational error is typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
8150 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While the link was disconnected. the driver initiated a link
reconnect attempt, but received an error from lower level software used
to control the PHY chip on the adapter card (in older software, “Cause”
is not used here; otherwise “Cause” = 32-bit status from the call to
vg_isr_call_phy_state_machine).
ACTION: This informational error is typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
8180 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a new bind (rendezvous) from an upper
layer protocol, at a time when the driver was not able to process these
requests, such as before receiving its initial configuration data, during
shutdown, or after a fatal software error (“Cause” = 16-bit encoded
value, giving driver input event code and current state: HP use only).