Chapter 41 GUARDIO Messages

Cause  A protocol error occurred between channel %c and device controller %dev during an execute input/output (I/O) instruction. The exact status is returned in the channel status word. A controller or a device may have failed.

Effect  The operation aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An illegal or unknown IIO/HIIO operation was sensed from unit %u in controller %dev on channel %c. The operation did not complete. The cause of the incomplete operation is unknown.

Effect  The state of the input/output (I/O) is unknown.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  There were excessive erroneous interrupts on channel %c. This problem usually results from a failing controller that is connected to the processor specified in the header.

Either the controller does not identify itself when polled or the controller asserts a continuous stream of interrupts to the channel.

The operating system does not know which controller is failing.

Effect  The operating system disables the processor's channel. All input/output (I/O) processes in the processor switch to their configured backups. Channel-based I/O can no longer be performed through this processor and channel. However, the processor remains up, and processes can run in the processor.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  There were excessive erroneous interrupts on channel %c. This problem usually results from a failing controller connected to the processor specified in the message header.

Either the controller does not identify itself when polled or the controller asserts a continuous stream of interrupts to the channel.

The operating system doesn't know which controller is failing.

Effect  The operating system resets the processor's channel. This action causes the failing controller to reset its internal status and resume normal operation.

If normal operation does not resume, the operating system kills the channel for the specified processor.

Recovery  If this condition persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The execute input/output (EIO) instruction timed out while trying to access the processor I/O channel %c. There may be an incorrect I/O configuration in the generating processor or a partial failure of the channel or device controller.

Effect  None.

Recovery  If this condition persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The sender processor detected what appeared to be a continually interrupting controller, and the system issued an execute I/O (EIO) “kill” command to disable controller %dev.

If the sender of this message is the monitor process (process ID is 0), the system killed the controller due to excessive interrupts on the subchannel.

If the sender of this message is the owner input/output (I/O) process (process ID is not 0), the system killed the controller because an ownership error occurred during an EIO retry.

Effect  The sender processor can't use this controller or any device attached to it until the associated processor module is reloaded.

Recovery  Reload the processor module, then contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  Device controller %dev rejected the input/output (I/O) operation because an operation is in progress.

Effect  The controller, device, or I/O process may fail.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  Device controller %dev detected a parity error on the execute input/output instruction. If continuous parity errors occur on a specific controller, controller hardware may have failed.

Effect  The operation aborts.

Recovery  Contact the Global Mission Critical Solution Center (GMCSC)and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A controller-ownership error occurred during execution of the execute input/output instruction.

Effect  The reporting processor attempts to take ownership of the controller and retry the EIO. If the retry fails, controller %dev is killed.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  During data transfer, channel %c detected an attempt to write to an unmapped memory page. This error may indicate a corrupt destination address in the input/output controller for unit %dev, a failure of the processor memory control unit, or a failure of the controlling input/output process.

Effect  The operation aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected a protocol error during communication with device controller %dev.

Effect  The requested operation is not performed. The device controller probably failed.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A parity error occurred during data transfer between channel %c and device controller %dev over the IOBUS. The channel, device controller, or IOBUS cabling between the channel and the controller may have failed.

Effect  The operation in progress aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  Controller %dev asserted a data-reconnect operation when the input/output controller status for unit %u indicated that no operation was in progress. If the controller is a programmable reconnect address controller (RAC), its calculation logic failed or it was incorrectly installed.

Effect  The controller asserting the data-reconnect fails.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A timeout occurred during a data-reconnect operation.

Effect  The operation in progress aborts. The controller may fail.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected an uncorrectable memory error while attempting to access the input/output controller during an operation.

Effect  The input/output operation in progress aborts. This event is probably followed by a processor freeze.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The current input/output controller (IOC) page is marked absent. The line input/output (LIOC) instruction, the software responsible for performing the LIOC instruction, or the processor memory controller may fail.

Effect  The operation aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A memory-access breakpoint was encountered when an input/output operation accessed the input/output controller.

Effect  The operation aborts.

Recovery  Informational message only; no corrective action is needed.

Cause  A memory-access breakpoint was encountered during a device-to-memory data transfer.

Effect  The operation aborts.

Recovery  Informational message only; no corrective action is needed.

Cause  A memory-access breakpoint was encountered during a memory-to-device data transfer.

Effect  The operation aborts.

Recovery  Informational message only; no corrective action is needed.

Cause  A device-ownership error was sensed during the execution of the input/instruction. This event may indicate a device controller failure.

Effect  If there are excessive ownership errors, the operating system kills the channel.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A protocol error occurred between channel %c and device controller %dev. The channel sent PADO, and the device controller did not return PADI. This error usually indicates a controller failure.

Effect  The operation in progress aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A protocol error occurred between channel %c and device controller %dev. A device returned PADI without returning “stop in handshake” during controller-to-channel control protocol. This error indicates that the controller may have failed.

Effect  The operation in progress aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An IN reconnect attempt was made when the input/output controller (IOC) expected an OUT operation.

Effect  The IN transfer fails.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A protocol error occurred between channel %c and controller %dev. The channel sent an end-of-transmission (EOT), and the device controller did not return stop-in (STI). This event indicates that unit %u failed.

Effect  The operation aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  Controller %dev asserted “service in handshake” and “stop in handshake” during data-reconnect protocol. This event usually indicates a device controller failure.

Effect  The operation in progress aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An uncorrectable memory error occurred during data transfer between memory and unit %u on controller %dev from channel %c.

Effect  The operation in progress aborts. There is a hard memory failure in IOSPACE, which may result in a processor freeze.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  Channel %c detected an attempt to read zero bytes during a data transfer. Controller %dev may be failing.

Effect  No data is transferred from the device.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel detected an attempt to write zero bytes during a data transfer. Controller %dev is probably failing.

Effect  No data is transferred to the device.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  One or more I/O interrupts failed with a condition code less (CCL) channel parity error, which indicates a channel failure.

Effect  If the system detects too many channel errors in a short time, the I/O interrupt handler attempts to reset the channel. If the channel reset fails, the system kills the channel. If the channel is killed, the processor is still up but is unable to perform I/O.

Recovery  If the channel is killed, reload the processor, taking into consideration any applications already running on that processor. Otherwise, do not reload the processor (Reloading the processor may result in the loss of important data.)

Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  There was an abnormal processor input/output (I/O) channel operation, or the system has an abnormal device controller or physical device.

Effect  The I/O channel, device controller, or physical device continues functioning abnormally.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected a protocol error during communication with device controller %dev. The channel attempted to interrogate a requesting controller during controller reconnect. The device controller responded with a reconnect address controller (RAC) word containing a combination of bits in RAC.<4:5> (Read/Write Reconnect). The RAC word does not indicate a read or write reconnect. This error may indicate a failure of the device controller or the channel microcode.

Effect  The requested operation is not performed.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected an abnormal operating condition. The exact nature of the error condition is unknown.

Effect  The input/output operation aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The same device has had a continuous reconnect pending over the last two operations. At the first attempt to reconnect, the device was aborted by the channel but the interprocessor unit (IPU) was not interrupted. When the device attempted to reconnect again, the IPU was interrupted.

Effect  The device controller indicated that the device reconnect address controller (RAC) has failed and has been killed by the operating system.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected an uncorrectable memory error while attempting to access the input/output controller (IOC).

Effect  The I/O operation in progress is aborted. The processor has probably frozen.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  One of the following failed: the line input/output controller (LIOC) instruction, the software responsible for performing the LIOC instruction, the processor Memory Controller (NonStop II), or the processor SPAD (TXP).

Effect  The current IOC page is marked absent.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A timeout occurred during a READ ADDRESS COMMAND TBUS function with a Rank 0 controller.

Effect  The operation in progress is aborted.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A timeout occurred during a READ ADDRESS COMMAND TBUS function with a Rank 1 controller.

Effect  The operation in progress is aborted.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The reconnect controller interface (RCI) was asserted, but no device responded to the reconnect poll. The controller that asserted the RCI has probably failed.

Effect  The channel doesn't know which controller failed. If this condition persists, the operating system brings down the channel.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A device illegally sent a handshake during a reconnect poll (RPOL) of a Rank 0 device. The device that asserted a handshake has probably failed. The channel does not know which controller failed; however, the controller is probably a Rank 0 controller.

Effect  The operation aborts.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A device illegally sent a handshake during a reconnect poll (RPOL) of a Rank 1 device. The controller that asserted the handshake probably failed. The channel does not know which controller has failed; however, the controller is probably a Rank 1 controller.

Effect  The operation fails.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected an unknown reconnect poll sequencer (RPS) freeze. The channel hardware is probably failing.

Effect  If the RPS failed, it may not be usable again until the processor is reloaded or the channel is reset. However, the channel tries to restart the RPS.

If this error occurs regularly, the operating system kills the channel.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A reconnect poll sequencer was detected with an unknown TBUS function. There was a hardware failure in the reconnect poll sequencer (RPS).

Effect  If the RPS failed, it may not be usable again until the processor is reloaded or the channel is reset. However, the channel tries to restart the RPS.

If this error occurs regularly, the operating system kills the channel.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A device did not handshake correctly or a parity error occurred on the data returned during a reconnect address controller (RAC) TBUS function.

Effect  Data may be corrupted.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A device did not handshake correctly during a TBUS SELECT function.

Effect  If the reconnect-poll sequencer (RPS) failed, it may not be usable again until the processor is reloaded or the channel is reset. However, the channel tries to restart the RPS.

If this error occurs regularly, the operating system kills the channel.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  One or more input/output (I/O) interrupts failed with a condition code less (CCL) channel parity error, which indicates a channel failure.

Effect  If the system detects too many channel errors in a short time, the I/O interrupt handler attempts to reset the channel; if the channel reset fails, the system kills the channel. If the channel is killed, the processor is still up but is unable to perform I/O.

Recovery  If the channel is down, reload the processor, taking into consideration any applications already running on that processor. Otherwise, do not reload the processor. (Reloading the processor may result in the loss of important data.)

Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The processor is receiving a continuous interrupt from the unit %u on controller %dev on channel %c.

Effect  The device port is brought down.

Recovery  This message indicates a hardware problem. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A protocol error occurred between channel %c and device controller %dev. A controller returned “pad in” without returning “stop in handshake.”

Effect  The operation in progress aborts. This usually indicates a controller failure.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The controller returned an invalid address and reconnect address controller (RAC) command word.

Effect  The operation fails.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An I/O controller was relocated using TMDS from where it was to a new location for diagnostic purposes or for channel load balancing.

Effect  The controller is configured for its new location.

Recovery  This is an informational message only; no corrective action is needed.

Cause  Three or more IOPONs have occurred on the controller within 10.2 minutes.

Effect  The IOPONs from the controller are ignored.

Recovery  Replace the controller.