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

448 Chapter20
LAP-B Link Error Messages
LAP-B Link Driver Error Messages
1030 MESSAGE: PSI register test failed during PSI initialization.
CAUSE: Bad PSI hardware.
ACTION: Run the Sherlock diagnostics on the PSI and call your
Hewlett-Packard representative if a failure is detected.
1032 MESSAGE: User invoked dump caused the driver to fail.
CAUSE: A user manually instructed the driver to dump via diagnostic
utilities when the driver had not encountered previous errors.
ACTION: If the dump was taken as a snapshot of a problem, call your
Hewlett-Packard representative, and save the raw dump file to show to
the HP person.
1033 MESSAGE: Dump-sequence failure.
CAUSE: Possible causes for this problem are as follows:
1. The dump module is missing.
2. The driver encountered an error while attempting to produce a
dump. The driver has unlocked itself and reported to upper levels
the error which originally caused the dump attempt; these levels will
now destroy the driver. Any dump file produced is probably
incomplete.
ACTION: Possible actions for this problem are as follows:
1. Run NMMAINT.PUB.SYS to verify the dump module is present.
2. Write down the error information displayed on the console, submit
an CR, and call your Hewlett-Packard representative.
1034 MESSAGE: An input message is being ignored.
CAUSE: A message received by the driver was not recognized or
processing of it could not begin. It is also possible the source port is not
operating with the required capabilities. The message was logged and
dropped.
ACTION: The diagnostic system logfile should contain a partial image of
the ignored message. Write down the information from this logfile as
well as the error information displayed on the console, submit an CR,
and call your Hewlett-Packard representative.
1035 MESSAGE: No TAB data structures available.
CAUSE: TAB data structures are used whenever the driver attempts to
start new hardware activity. There is a limited number of these data
structures available. Unexpected use of incorrect port and subqueues
may have created excessive pending hardware activity. This problem
may also be reported if a buffer-manager buffer could not be obtained.
ACTION: Unsupported programs should not contact the driver through
incorrect subqueues. This problem should produce a dump; keep the