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

256 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
Check the configuration of the hub or switch port to which the adapter
card is connected. Adjust that configuration and, if necessary, use
NMMGR to adjust the configuration of the link, so that something will
match. If necessary, specify a forced speed and duplex setting, and
disable autonegotiation, at both ends.
7850 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While attempting to logically disconnect the link, the driver
encountered a problem (“Cause” = 32-bit status from the call to
Vg_isr_call_phy_state_machine). Probably a power failure or
system timer problem has occurred.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. If a power failure has occurred,
this error may be ignored; the driver will soon attempt to recover.
Otherwise, most likely the previous error was fatal and the driver is
about to “die”, then will either attempt an auto-reset or else require a
manual shutdown and restart.
7880 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: After attempting to disconnect the link, the driver’s ISR module
determined the link did disconnect, then encountered an error trying to
notify the DVR module of the disconnect (“Cause” = 32-bit status from
the call to Vg_isr_copy_send_to_dvr). Probably no comm frame was
available.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. Most likely the previous error
was fatal and the driver is about to “die”, then will either attempt an
auto-reset or else require a manual shutdown and restart.
7910 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: After an attempt failed to connect the link, the driver’s ISR
module started to prepare for a later retry, then encountered an error
while trying to get or reset a timer (“Cause” = 32-bit status from the call
to vg_start_timer). This timer was to be used to awaken the driver so
it could retry the connect; the driver cannot connect the link if a PHY
timer cannot be started. If this error is reported, it is because the driver
has already encountered some other error.
ACTION: Typically preceded by another error message giving better
information about the original cause; check log data for that error and
look it up also. The driver did not dump, but will still attempt to
auto-reset itself, up to a total of 12 times or more. If the problem
persists, the system may be low on timers; try stopping some
applications before retrying again.