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

454 Chapter20
LAP-B Link Error Messages
LAP-B Link Driver Error Messages
this information, call your Hewlett-Packard representative.
1062 MESSAGE: Bad top plane buffer pool in configuration data.
CAUSE: The driver requires the valid buffer-pool ID of a pool to be used
for card trace and other internal I/O, to appear in a configuration buffer
passed during startup, but the ID it found was zero. The module
configurator should not have sent the configure message if the buffer
pool could not be opened. Alternately, configuration buffer formats may
be mismatched.
ACTION: Run NMMAINT.PUB.SYS to verify the versions of the driver,
module configurator, and download file. If the problem cannot be solved
from this information, call your Hewlett-Packard representative.
1063 MESSAGE: Timeout during startup.
CAUSE: The driver startup timer expired between the time the driver
received its configure message and the time it completed all hardware
and software startup. Probably the PSI hung due to a hardware failure,
download bug, or corrupt download data not otherwise detected.
Though unlikely, it is also possible that completions for driver requests
were excessively delayed due to heavy system loading.
ACTION: The driver normally allows about 30 seconds for all of startup.
In a heavily loaded system, this problem might appear intermittently;
try restarting the link. If the problem persists, call your
Hewlett-Packard representative.
1064 MESSAGE: Timeout during selftest.
CAUSE: The driver selftest timer expired between the time the driver
received its do_bind message and the time the hardware completed
selftest. Probably the PSI failed selftest so badly it was unable to report
the selftest error.
ACTION: The driver normally allows about 30 seconds for selftest to
complete. Your PSI hardware is probably dead; write down the error
information displayed on the console, submit an CR, and call your
Hewlett-Packard representative.
1065 MESSAGE: Local timer popped.
CAUSE: This timeout should only occur if the PSI hardware hangs due
to a hardware failure or a bug in the downloaded code. The driver
solicited activity from the hardware local timeout seconds ago, and
that activity has still not completed. The driver has stopped the
hardware and requested a dump.
ACTION: This problem should produce a dump; file an CR, keep the raw
dump, and call your Hewlett-Packard representative.