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

264 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
8510 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While beginning a driver start or restart operation, the driver
tried to set the heartbeat timer, but encountered an error
(“Cause” = 32-bit status from the call to vg_start_timer). This timer
was to be used to periodically awaken the driver so it could verify card
health; the driver cannot start 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.
8540 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: While beginning a driver start or restart operation, the driver
tried to initialize the adapter card registers, but lower level software
reported an error (“Cause” = 32-bit status from the call to
vg_isr_init_card_regs). 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. If necessary, replace the adapter card.
8570 CLAS0001 MESSAGE: One or more bad unbind parms passed by upper level
protocol.
CAUSE: The driver received an unbind (separate) from an upper layer
protocol module, but the specified rendezvous ID was out of range of
legal rendezvous ID values for this driver (“Cause” = 32-bit value giving
the bad ID which was specified). The protocol was supposed to pass a
rendezvous ID value previously returned to it by the driver, when that
protocol did a bind.
ACTION: This problem most likely occurred while stopping a running
network subsystem. Attempt to determine which subsystem was being
stopped when the error occurred and, if possible, which upper layer
protocol was unbinding.
The unbind failed. The driver logged the error, then attempted to send
an error reply message back to the protocol module and continue. The
driver still thinks the protocol is bound. Future attempts to start that
same protocol will probably fail until the entire network is stopped or
the system is rebooted.
Either there is a bug in the driver or upper layer protocol software,
memory data corruption has occurred, or there is a system software
mismatch. You may require additional software patches; contact your