2 * Text: "%s: An I/O-error occurred on the CTCM device\n"
5 * @1: bus ID of the CTCM device
7 * An I/O error was detected on one of the subchannels of the CTCM device.
8 * Depending on the error, the CTCM device driver might attempt an automatic
11 * Check the status of the CTCM device, for example, with ifconfig. If the
12 * device is not operational, perform a manual recovery. See "Device Drivers,
13 * Features, and Commands" for details about how to recover a CTCM device.
17 * Text: "%s: An adapter hardware operation timed out\n"
20 * @1: bus ID of the CTCM device
22 * The CTCM device uses an adapter to physically connect to its communication
23 * peer. An operation on this adapter timed out.
25 * Check the status of the CTCM device, for example, with ifconfig. If the
26 * device is not operational, perform a manual recovery. See "Device Drivers,
27 * Features, and Commands" for details about how to recover a CTCM device.
31 * Text: "%s: An error occurred on the adapter hardware\n"
34 * @1: bus ID of the CTCM device
36 * The CTCM device uses an adapter to physically connect to its communication
37 * peer. An operation on this adapter returned an error.
39 * Check the status of the CTCM device, for example, with ifconfig. If the
40 * device is not operational, perform a manual recovery. See "Device Drivers,
41 * Features, and Commands" for details about how to recover a CTCM device.
45 * Text: "%s: The communication peer has disconnected\n"
50 * The remote device has disconnected. Possible reasons are that the remote
51 * interface has been closed or that the operating system instance with the
52 * communication peer has been rebooted or shut down.
54 * Check the status of the peer device. Ensure that the peer operating system
55 * instance is running and that the peer interface is operational.
59 * Text: "%s: The remote operating system is not available\n"
64 * The operating system instance with the communication peer has disconnected.
65 * Possible reasons are that the operating system instance has been rebooted
68 * Ensure that the peer operating system instance is running and that the peer
69 * interface is operational.
73 * Text: "%s: The adapter received a non-specific IRQ\n"
76 * @1: bus ID of the CTCM device
78 * The adapter hardware used by the CTCM device received an IRQ that cannot
79 * be mapped to a particular device. This is a hardware problem.
81 * Check the status of the CTCM device, for example, with ifconfig. Check if
82 * the connection to the remote device still works. If the CTCM device is not
83 * operational, set it offline and back online. If this does not resolve the
84 * problem, perform a manual recovery. See "Device Drivers, Features, and
85 * Commands" for details about how to recover a CTCM device. If this problem
86 * persists, gather Linux debug data, collect the hardware logs, and report the
87 * problem to your support organization.
91 * Text: "%s: A check occurred on the subchannel\n"
94 * @1: bus ID of the CTCM device
96 * A check condition has been detected on the subchannel.
98 * Check if the connection to the remote device still works. If the CTCM device
99 * is not operational, set it offline and back online. If this does not resolve
100 * the problem, perform a manual recovery. See "Device Drivers, Features, and
101 * Commands" for details about how to recover a CTCM device. If this problem
102 * persists, gather Linux debug data and report the problem to your support
107 * Text: "%s: The communication peer is busy\n"
108 * Severity: Informational
112 * A busy target device was reported. This might be a temporary problem.
114 * If this problem persists or is reported frequently ensure that the target
115 * device is working properly.
119 * Text: "%s: The specified target device is not valid\n"
124 * A target device was called with a faulty device specification. This is an
125 * adapter hardware problem.
127 * Gather Linux debug data, collect the hardware logs, and contact IBM support.
131 * Text: "An I/O operation resulted in error %04x\n"
135 * @2: error information
137 * A hardware operation ended with an error.
139 * Check the status of the CTCM device, for example, with ifconfig. If the
140 * device is not operational, perform a manual recovery. See "Device Drivers,
141 * Features, and Commands" for details about how to recover a CTCM device.
142 * If this problem persists, gather Linux debug data, collect the hardware logs,
143 * and report the problem to your support organization.
147 * Text: "%s: Initialization failed with RX/TX init handshake error %s\n"
150 * @1: bus ID of the CTCM device
151 * @2: error information
153 * A problem occurred during the initialization of the connection. If the
154 * connection can be established after an automatic recovery, a success message
157 * If the problem is not resolved by the automatic recovery process, check the
158 * local and remote device. If this problem persists, gather Linux debug data
159 * and report the problem to your support organization.
163 * Text: "%s: The network backlog for %s is exceeded, package dropped\n"
166 * @1: bus ID of the CTCM device
167 * @2: calling function
169 * There is more network traffic than can be handled by the device. The device
170 * is closed and some data has not been transmitted. The device might be
171 * recovered automatically.
173 * Investigate and resolve the congestion. If necessary, set the device
174 * online to make it operational.
178 * Text: "%s: The XID used in the MPC protocol is not valid, rc = %d\n"
181 * @1: bus ID of the CTCM device
184 * The exchange identification (XID) used by the CTCM device driver when
185 * in MPC mode is not valid.
187 * Note the error information provided with this message and contact your
188 * support organization.
191 /*? Text: "CTCM driver unloaded\n" */
192 /*? Text: "%s: %s Internal error: net_device is NULL, ch = 0x%p\n" */
193 /*? Text: "%s / register_cu3088_discipline failed, ret = %d\n" */
194 /*? Text: "%s: %s: Internal error: Can't determine channel for interrupt device %s\n" */
195 /*? Text: "CTCM driver initialized\n" */
196 /*? Text: "%s: setup OK : r/w = %s/%s, protocol : %d\n" */
197 /*? Text: "%s: Connected with remote side\n" */
198 /*? Text: "%s: Restarting device\n" */