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

Chapter 16 215
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
another error giving more 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 an SR.
MESSAGE: Pending message table full. Driver not finishing fast
enough.
2530 CLAS0001 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 is only caused by a bug, because the
in use flags and counters should match. After reporting this error, the
driver will die, then will 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 an SR.
MESSAGE: Pending message table full. Driver not finishing fast
enough.
2560 CLAS0001 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 was unable to find an unused entry (“Cause” is not used
here).
ACTION: This fatal software error is only caused by a bug, since
message port subqueue controls should have prevented the table from
filling. After reporting this error, the driver will die, then will either
attempt an auto-reset or else require a manual shutdown and restart.
Most likely some subsystem has sent a message to an incorrect
subqueue. If the problem persists, try to determine which program,
networking subsystem, or operator command causes it; then activate
link tracing, reproduce the problem, and save the resulting trace file
(NMTC####.PUB.SYS) for analysis by Hewlett-Packard. See Appendix
A, “Submitting an SR.
MESSAGE: Illegal access to saved port message area.
2590 CLAS0001 CAUSE: While completing an old blocking request (requiring a driver
exit and later reply), the driver found that the entry in the pending
message save area, where the request was supposedly saved, was no
longer in use (“Cause”= table entry number where the request was
supposed to be).
ACTION: This fatal software error is only caused by a bug, because the
driver should never be trying to complete the same message twice.
After reporting this error, the driver will die, then will either attempt
an auto-reset or else require a manual shutdown and restart. If the
problem persists, try to determine which program, networking
subsystem, or operator command causes it; then activate link tracing,