LAP-B Link Driver Error Messages

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: A catastrophic internal resource error was detected.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Either the download file is corrupt, or the PSI hardware has failed.

ACTION: Replace the download file from your latest system update tape, and run the Sherlock diagnostics on the PSI. Call your Hewlett-Packard representative if a failure is detected.

CAUSE: Either the download file is corrupt, or the PSI hardware has failed.

ACTION: Replace the download file from your latest system update tape, and run the Sherlock diagnostics on the PSI. Call your Hewlett-Packard representative if a failure is detected.

CAUSE: Either the download file is corrupt, or the PSI hardware has failed.

ACTION: Replace the download file from your latest system update tape and run the Sherlock diagnostics on the PSI and call your Hewlett-Packard representative if a failure is detected.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Either the download file is corrupt, or there is an incorrect version of the download file.

ACTION: Replace the download file from your latest system update tape. You should also check the version of the download file with NMMAINT and call your Hewlett-Packard representative if incorrect.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: The version of the PSI is not compatible with this driver.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Bad PSI hardware.

ACTION: Run the Sherlock diagnostics on the PSI hardware and call your Hewlett-Packard representative if an error is detected.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Bad PSI hardware.

ACTION: Run the Sherlock diagnostics on the PSI and call your Hewlett-Packard representative if a failure is detected.

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.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

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 SR, and call your Hewlett-Packard representative.

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 raw dump file along with the error information displayed on the console, call your Hewlett-Packard representative, and submit an SR.

CAUSE: Hardware was successfully downloaded, but the downloaded code turned out to be for a different driver. Someone may have incorrectly renamed a download file to have the name of the file expected by the driver, or your download file or installed driver may be extremely old and not matched.

ACTION: Run NMMAINT.PUB.SYS to verify the version of the download file and driver. If the file is incorrect, attempt to restore a copy from a system backup tape. If this does not solve the problem, you may need to update your system and download file; call your Hewlett-Packard representative.

CAUSE: Hardware was successfully downloaded but the revision of the download file cannot be used with the version of the corresponding installed driver because their interfaces are incompatible.

ACTION: Check to see if operators forgot to restore the latest download file during a recent system update. If not, try restoring the file from a system backup tape. If this does not solve the problem, you may need to update your system and download file; call your Hewlett-Packard representative.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: The driver attempted to free memory which the buffer manager did not recognize as a valid buffer, due to a driver problem or memory data corruption. Also, a problem somewhere may have caused the driver to attempt to free a buffer which was not in use.

ACTION: A system dump will probably be required; call your Hewlett-Packard representative.

CAUSE: A call to obtain a timer resource returned in error. Too many timers may be in use.

ACTION: If you suspect your system may be low on timer resources due to heavy loading, try restarting the link later. If repeated attempts fail, warmstart your system. If the problem persists, a system dump will be required; call your Hewlett-Packard representative.

CAUSE: The system rejected an attempt by the driver to reset a timer supposedly owned by the driver. Memory data corruption may have occurred.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The driver tried to free a timer which was not recognized by the system as a valid timer. Memory data corruption may have occurred.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The driver could not obtain a reply-message frame from the source port of a newly arrived request message, or from a transport port in the case of a driver-detected asynchronous event. If the system is otherwise operating well, modules attempting to communicate with the driver may not be operating with the required capabilities.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: A call to the system message-send routine returned in error. The destination port may belong to a process which no longer exists or is not operating with the required capabilities.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: A call to the system message-freeing routine returned in error. The port may belong to a process which no longer exists or is not operating with the required capabilities, or the message frame was not recognized by the system as a valid message frame.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The system rejected an attempt by the driver to locate message frames on its own port. Memory data corruption may have occurred.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The driver attempted to enter a state which it should never be able to get into, and ceased operations instead. Memory data corruption, a driver bug, or a problem with the execution priorities of the driver and/or its hardware may exist.

ACTION: This problem should produce a dump. Keep the raw dump along with the error information displayed on the console, call your Hewlett-Packard representative, and submit an SR.

CAUSE: The driver was notified that power returned after a power failure of any duration.

ACTION: The driver is not capable of recovering from power failures, and modem connections were probably lost. Restart the link.

CAUSE: The driver had to reject a request message because it had previously become broken for another reason. The rejected request could not be processed while the driver was broken.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The driver received a request message during a short time interval after shutdown completed, but before the driver's port had been destroyed by the system. The driver should not be receiving new requests after shutdown, and it cannot successfully complete them.

ACTION: If this problem occurs repeatedly, call your Hewlett-Packard representative.

CAUSE: Hardware was not ready to process a request message which required hardware participation.

ACTION: Retry the request at a later time. If the problem persists, call your Hewlett-Packard representative.

CAUSE: The driver could not obtain enough context storage to begin processing a request, so the request was rejected. Unexpected use of incorrect port subqueues may have created excessive pending hardware activity.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The driver received a sequencing message at the wrong time. This was a startup, shutdown, or dump-control message which arrived out-of-sequence.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: The driver recognized a request message but the feature it requested is not applicable to that driver. The message descriptor was known but the message and/or its subfunction code(s) are unimplemented.

ACTION: Call your Hewlett-Packard representative and explain what you were trying to do.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: The configuration buffer passed to the driver during startup was not correctly formatted for the driver it was sent to. That driver did not find its own subsystem number in the expected buffer field.

ACTION: Run NMMAINT.PUB.SYS to verify the software versions are correct between the driver and module-configurator. Also check your configuration screens and if necessary restore NMCONFIG.PUB.SYS from a system backup tape. If the problem does not go away, call your Hewlett-Packard representative.

CAUSE: Data was requested from the driver but the length of the buffer specified in the request was too small to accept all the data. The driver is not capable of returning partial data. The driver also imposes a minimum-size limit on trace buffers.

ACTION: If the problem occurred when starting trace, try specifying a larger trace-buffer size. There may be a version-mismatch between your driver and other supporting software; call your Hewlett-Packard representative.

CAUSE: The driver received a trace-disable request when trace was already off. The trace-manager module should not have passed the request to the driver when trace was off.

ACTION: This is intended as a warning. You do not need to turn trace off when it is not on.

CAUSE: The driver received a trace-enable request when trace was already on. The trace-manager module should not have passed the request to the driver when trace was on. The driver does not support altering the active trace-level in this manner.

ACTION: This is intended as a warning. You cannot turn trace on when it is already on.

CAUSE: The driver requires the valid memory address of an open download file to appear in a configuration buffer passed during startup, but the address it found was zero. The module configurator should not have sent the configure message if it could not open the download file. 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.

CAUSE: The driver requires the valid buffer-pool ID of a pool to be used for read/write datacomm line frames, to appear in a configuration buffer passed during startup, but the ID it found was zero. The transport should not have invoked the module configurator if the buffer pool could not be opened. Alternately, configuration buffer formats may be mismatched.

ACTION: Check to see if the transport reported any initialization errors. 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.

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.

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.

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 SR, and call your Hewlett-Packard representative.

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 SR, keep the raw dump, and call your Hewlett-Packard representative.

CAUSE: The driver detected an error, but did not say what type of error was detected.

ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.

CAUSE: Before attempting to autodial, the PSI detected something wrong. Specifically, the PSI detected an active ACR line before attempting to autodial.

ACTION: Check your autodialer and the modem.

CAUSE: The autodial phone number was entered into your configuration screen incorrectly.

ACTION: Check autodial phone number entry in your configuration screen for this link.

CAUSE: The autodial was not completed. This may happen when the remote system's modem is not turned on or not functional.

ACTION: Check with your remote system to ensure that its modems are turned on and functional.

CAUSE: Your local autodial modem has not been turned on.

ACTION: Turn on your local autodial modem.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Either no cable is attached, a non-autodial cable is attached, or a bad autodial cable is attached.

ACTION: Check to see if the cable is properly attached. If it is, try another cable. If you still get this error, write down the error information displayed on the console, submit an SR, and call you local Hewlett-Packard representative.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: Unexpected use of driver subqueues may create this problem.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: Bad Asynchronous event quad completed by the PSI.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: The driver received a command or is in a state where it cannot continue operation.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: A completion by the PSI was received in an invalid state.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: Possible causes for this problem are as follows:

ACTION: Possible actions for this problem are as follows:

CAUSE: The driver received a bad meta language tag while binding with NS.

ACTION: Write down the console error message, submit an SR and call your Hewlett-Packard representative.

CAUSE: The driver received a bind message while it was already bound.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: The driver was requested to perform a command when the PSI card was not ready.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: The module dependent field returned by the PSI does not make any sense.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.

CAUSE: The driver was asked to execute a command without being bound to upper layer.

ACTION: Write down the error information displayed on the console, submit an SR and contact your Hewlett-Packard representative.