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

Chapter 16 213
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
If you suspect a heavy load, you can try shutting some processes down,
then restart the driver. Otherwise use Control-B at the console to halt
the system, take a memory dump, and reboot. See Appendix A ,
“Submitting a CR.”
2240 CLAS0001 MESSAGE: Cannot reset a system timer.
CAUSE: The driver attempted to reset a system timer previously
obtained from I/O Services but encountered an error (“Cause” = 32-bit
status returned by the call to io_reset_timer). This is likely caused by
a bug in system software, or by corruption of the driver’s PDA context
memory.
ACTION: This is a fatal software error. The driver cannot operate without all
necessary timers. Afterreporting thiserror, the driverwill die, thenwill either
attempt an auto-reset or else require a manual shutdown and restart. If the
problem persists, use Control-B at the console to halt the system, take a
memory dump, and reboot. See Appendix A , “Submitting a CR.”
2270 CLAS0001 MESSAGE: Cannot free a system timer.
CAUSE: The driver attempted to release a system timer previously
obtained from I/O Services but encountered an error (“Cause” = 32-bit
status returned by the call to io_release_timer). This is likely caused
by a bug in system software, or by corruption of the driver’s PDA
context memory.
ACTION: This is a warning that some timer resources may have been lost.
The driver will attempt to continue. Unless this happens constantly, the
system should continuetorun. Possibly followed by another errorgivingmore
information about what kind of timer the driver was releasing; check log data
for that error and look it up also. If the problem happens every time, see
Appendix A , “Submitting a CR.”
2530 CLAS0001 MESSAGE: Pending message table full. Driver not finishing fast
enough.
CAUSE: While processing a new blocking request (requiring a driver exit
and later reply) and scanning a table in which to save the request, the
driver found an unused entry, but an entry counter indicated the table
was full (“Cause” is not used here).
ACTION: This fatal software error isonly caused by a bug, because the in use
flags and counters should match. After reporting thiserror, the driver will die,
then will eitherattempt an auto-reset or elserequire a manual shutdown and
restart. If the problem persists, use Control-B at the console to halt the
system, take a memory dump, and reboot. See Appendix A , “Submitting a
CR.”
2560 CLAS0001 MESSAGE: Pending message table full. Driver not finishing fast
enough.
CAUSE: While processing a new blocking request (requiring a driver exit
and later reply) and scanning a table in which to save the request, the