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

262 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: Driver encountered a software problem.
8120 CLAS0001 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.
MESSAGE: Driver encountered a software problem.
8150 CLAS0001 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.
MESSAGE: Bad message for current state.
8180 CLAS0001 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).
ACTION: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding. The bind failed. The driver logged the error, then
attempted to send an error reply message back to the protocol module
and continue.
Check the system console; if the driver is shutting down or doing a
dump, wait until that completes. In these cases, several protocols may
experience this same error. If the driver is not shutting down or dying,
the protocol may be sending binds to the driver at the wrong time. See
Appendix A, “Submitting an SR,” and file an SR against the network
subsystem being started.