/*?
 * Text: "%s: An I/O-error occurred on the CTCM device\n"
 * Severity: Error
 * Parameter:
 *   @1: bus ID of the CTCM device
 * Description:
 * An I/O error was detected on one of the subchannels of the CTCM device.
 * Depending on the error, the CTCM device driver might attempt an automatic
 * recovery.
 * User action:
 * Check the status of the CTCM device, for example, with ifconfig. If the
 * device is not operational, perform a manual recovery. See "Device Drivers,
 * Features, and Commands" for details about how to recover a CTCM device.
 */

/*?
 * Text: "%s: An adapter hardware operation timed out\n"
 * Severity: Error
 * Parameter:
 *   @1: bus ID of the CTCM device
 * Description:
 * The CTCM device uses an adapter to physically connect to its communication
 * peer. An operation on this adapter timed out.
 * User action:
 * Check the status of the CTCM device, for example, with ifconfig. If the
 * device is not operational, perform a manual recovery. See "Device Drivers,
 * Features, and Commands" for details about how to recover a CTCM device.
 */

/*?
 * Text: "%s: An error occurred on the adapter hardware\n"
 * Severity: Error
 * Parameter:
 *   @1: bus ID of the CTCM device
 * Description:
 * The CTCM device uses an adapter to physically connect to its communication
 * peer. An operation on this adapter returned an error.
 * User action:
 * Check the status of the CTCM device, for example, with ifconfig. If the
 * device is not operational, perform a manual recovery. See "Device Drivers,
 * Features, and Commands" for details about how to recover a CTCM device.
 */

/*?
 * Text: "%s: The communication peer has disconnected\n"
 * Severity: Notice
 * Parameter:
 *   @1: channel ID
 * Description:
 * The remote device has disconnected. Possible reasons are that the remote
 * interface has been closed or that the operating system instance with the
 * communication peer has been rebooted or shut down.
 * User action:
 * Check the status of the peer device. Ensure that the peer operating system
 * instance is running and that the peer interface is operational.
 */

/*?
 * Text: "%s: The remote operating system is not available\n"
 * Severity: Notice
 * Parameter:
 *   @1: channel ID
 * Description:
 * The operating system instance with the communication peer has disconnected.
 * Possible reasons are that the operating system instance has been rebooted
 * or shut down.
 * User action:
 * Ensure that the peer operating system instance is running and that the peer
 * interface is operational.
 */

/*?
 * Text: "%s: The adapter received a non-specific IRQ\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the CTCM device
 * Description:
 * The adapter hardware used by the CTCM device received an IRQ that cannot
 * be mapped to a particular device. This is a hardware problem.
 * User action:
 * Check the status of the CTCM device, for example, with ifconfig. Check if
 * the connection to the remote device still works. If the CTCM device is not
 * operational, set it offline and back online. If this does not resolve the
 * problem, perform a manual recovery. See "Device Drivers, Features, and
 * Commands" for details about how to recover a CTCM device. If this problem
 * persists, gather Linux debug data, collect the hardware logs, and report the
 * problem to your support organization.
 */

/*?
 * Text: "%s: A check occurred on the subchannel\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the CTCM device
 * Description:
 * A check condition has been detected on the subchannel.
 * User action:
 * Check if the connection to the remote device still works. If the CTCM device
 * is not operational, set it offline and back online. If this does not resolve
 * the problem, perform a manual recovery. See "Device Drivers, Features, and
 * Commands" for details about how to recover a CTCM device. If this problem
 * persists, gather Linux debug data and report the problem to your support
 * organization.
 */

/*?
 * Text: "%s: The communication peer is busy\n"
 * Severity: Informational
 * Parameter:
 *   @1: channel ID
 * Description:
 * A busy target device was reported. This might be a temporary problem.
 * User action:
 * If this problem persists or is reported frequently ensure that the target
 * device is working properly.
 */

/*?
 * Text: "%s: The specified target device is not valid\n"
 * Severity: Error
 * Parameter:
 *   @1: channel ID
 * Description:
 * A target device was called with a faulty device specification. This is an
 * adapter hardware problem.
 * User action:
 * Gather Linux debug data, collect the hardware logs, and contact IBM support.
 */

/*?
 * Text: "An I/O operation resulted in error %04x\n"
 * Severity: Error
 * Parameter:
 *   @1: channel ID
 *   @2: error information
 * Description:
 * A hardware operation ended with an error.
 * User action:
 * Check the status of the CTCM device, for example, with ifconfig. If the
 * device is not operational, perform a manual recovery. See "Device Drivers,
 * Features, and Commands" for details about how to recover a CTCM device.
 * If this problem persists, gather Linux debug data, collect the hardware logs,
 * and report the problem to your support organization.
 */

/*?
 * Text: "%s: Initialization failed with RX/TX init handshake error %s\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the CTCM device
 *   @2: error information
 * Description:
 * A problem occurred during the initialization of the connection. If the
 * connection can be established after an automatic recovery, a success message
 * is issued.
 * User action:
 * If the problem is not resolved by the automatic recovery process, check the
 * local and remote device. If this problem persists, gather Linux debug data
 * and report the problem to your support organization.
 */

/*?
 * Text: "%s: The network backlog for %s is exceeded, package dropped\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the CTCM device
 *   @2: calling function
 * Description:
 * There is more network traffic than can be handled by the device. The device
 * is closed and some data has not been transmitted. The device might be
 * recovered automatically.
 * User action:
 * Investigate and resolve the congestion. If necessary, set the device
 * online to make it operational.
 */

/*?
 * Text: "%s: The XID used in the MPC protocol is not valid, rc = %d\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the CTCM device
 *   @2: return code
 * Description:
 * The exchange identification (XID) used by the CTCM device driver when
 * in MPC mode is not valid.
 * User action:
 * Note the error information provided with this message and contact your
 * support organization.
 */

/*? Text: "CTCM driver unloaded\n" */
/*? Text: "%s: %s Internal error: net_device is NULL, ch = 0x%p\n" */
/*? Text: "%s / Initializing the ctcm device driver failed, ret = %d\n" */
/*? Text: "%s: %s: Internal error: Can't determine channel for interrupt device %s\n" */
/*? Text: "CTCM driver initialized\n" */
/*? Text: "%s: setup OK : r/w = %s/%s, protocol : %d\n" */
/*? Text: "%s: Connected with remote side\n" */
/*? Text: "%s: Restarting device\n" */
/*? Text: "netif_stop_queue() cannot be called before register_netdev()\n" */
/*? Text: "flen=%u proglen=%u pass=%u image=%pK from=%s pid=%d\n" */
/*? Text: "%s selects TX queue %d, but real number of TX queues is %d\n" */
/*? Text: "%s: %d output lines suppressed due to ratelimiting\n" */
