* See the errno man page to find out what caused the problem.
*/
/*? Text: "%s: Got subchannel machine check but no sch_event handler provided.\n" */
+
+/*?
+ * Text: "%s: Setting the device online failed because it is boxed\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: Device bus-ID
+ * Description:
+ * Initialization of a device did not complete because it did not respond in
+ * time or it was reserved by another operating system.
+ * User action:
+ * Make sure that the device is working correctly, then try again to set it
+ * online. For devices that support the reserve/release mechanism (for example
+ * DASDs), you can try to override the reservation of the other system by
+ * writing 'force' to the 'online' sysfs attribute of the affected device.
+ */
+
+/*?
+ * Text: "%s: Setting the device online failed because it is not operational\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: Device bus-ID
+ * Description:
+ * Initialization of a device did not complete because it is not present or
+ * not operational.
+ * User action:
+ * Make sure that the device is present and working correctly, then try again
+ * to set it online.
+ */
+
+/*?
+ * Text: "%s: The device stopped operating while being set offline\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: Device bus-ID
+ * Description:
+ * While the device was set offline, it was not present or not operational.
+ * The device is now inactive, but setting it online again might fail.
+ * User action:
+ * None.
+ */
+
+/*?
+ * Text: "%s: The device entered boxed state while being set offline\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: Device bus-ID
+ * Description:
+ * While the device was set offline, it did not respond in time or it was
+ * reserved by another operating system. The device is now inactive, but
+ * setting it online again might fail.
+ * User action:
+ * None.
+ */
* Text: "The CPU configuration topology of the machine is:"
* Severity: Informational
* Description:
- * The first six values of the topology information represent fields Mag1 to
- * Mag6 of system-information block (SYSIB) 15.1.2. These fields specify the
+ * The first six values of the topology information represent fields Mag6 to
+ * Mag1 of system-information block (SYSIB) 15.1.2. These fields specify the
* maximum numbers of topology-list entries (TLE) at successive topology nesting
* levels. The last value represents the MNest value of SYSIB 15.1.2 which
* specifies the maximum possible nesting that can be configured through
*/
/*?
- * Text: "%s: New DASD with %ld byte/block, total size %ld KB\n"
+ * Text: "%s: New DASD with %ld byte/block, total size %ld KB%s\n"
* Severity: Informational
* Parameter:
* @1: bus ID of the DASD
* @2: bytes per block
* @3: size
+ * @4: access mode
* Description:
* A DASD with the indicated block size and total size has been set online.
+ * If the DASD is configured as read-only to the real or virtual hardware,
+ * the message includes an indication of this hardware access mode. The
+ * hardware access mode is independent from the 'readonly' attribute of
+ * the device in sysfs.
* User action:
* None.
*/
* @2: return code
* Description:
* Initializing the DASD with the DIAG discipline failed. Possible reasons for
- * this problem are that the device is read-only, has a device type other
- * than FBA or ECKD, or has a block size other than one of the supported sizes:
+ * this problem are that the device has a device type other than FBA or ECKD,
+ * or has a block size other than one of the supported sizes:
* 512 byte, 1024 byte, 2048 byte, or 4096 byte.
* User action:
* Ensure that the device can be written to and has a supported device type
* User action:
* Remove the unsupported discipline from the parameter string.
*/
+
+/*?
+ * Text: "%s: The access mode of a DIAG device changed to read-only"
+ * Severity: Warning
+ * Parameter:
+ * @1: bus ID of the DASD
+ * Description:
+ * A device changed its access mode from writeable to
+ * read-only while in use.
+ * User action:
+ * Set the device offline, ensure that the device is configured correctly in
+ * z/VM, then set the device online again.
+ */
* User action:
* Look up the SRC in the storage server documentation.
*/
+
+/*?
+ * Text: "%s: Reading device feature codes failed with rc=%d\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: bus ID of the DASD
+ * @2: return code
+ * Description:
+ * The device feature codes state which advanced features are supported by a
+ * device.
+ * Examples for advanced features are PAV or high performance FICON.
+ * Some early devices do not provide feature codes and no advanced features are
+ * available on these devices.
+ * User action:
+ * None, if the DASD does not provide feature codes. If the DASD provides
+ * feature codes, make sure that it is working correctly, then set it offline
+ * and back online.
+ */
+
+/*?
+ * Text: "%s: A channel path group could not be established\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: bus ID of the DASD
+ * Description:
+ * Initialization of a DASD did not complete because a channel path group
+ * could not be established.
+ * User action:
+ * Make sure that the DASD is working correctly, then try again to set it
+ * online. If initialization still fails, reboot.
+ */
+
+/*?
+ * Text: "%s: The DASD is not operating in multipath mode\n"
+ * Severity: Informational
+ * Parameter:
+ * @1: bus ID of the DASD
+ * Description:
+ * The DASD channel path group could not be configured to use multipath mode.
+ * This might negatively affect I/O performance on this DASD.
+ * User action:
+ * Make sure that the DASD is working correctly, then try again to set it
+ * online. If initialization still fails, reboot.
+ */
+
+/*?
+ * Text: "%s: Detecting the DASD disk layout failed because of an I/O error\n"
+ * Severity: Error
+ * Parameter:
+ * @1: bus ID of the DASD
+ * Description:
+ * The disk layout of the DASD could not be detected because of an unexpected
+ * I/O error. The DASD device driver treats the device like an unformatted DASD,
+ * and partitions on the device are not accessible.
+ * User action:
+ * If the DASD is formatted, make sure that the DASD is working correctly,
+ * then set it offline and back online. If the DASD is unformatted, format the
+ * DASD, for example, with dasdfmt.
+ * ATTENTION: Formatting irreversibly destroys all data on the DASD.
+ */
*/
/*?
- * Text: "Linux is running under KVM in 64-bit mode\n"
- * Severity: Informational
- * Description:
- * The 64-bit kernel detected that it is running under the KVM hypervisor.
- * User action:
- * None.
- */
-
-/*?
* Text: "Defining the Linux kernel NSS failed with rc=%d\n"
* Severity: Error
* Parameter:
* For other return codes, see the help and message documentation for
* the CP SAVESYS command.
*/
+
+/*? Text: "Linux is running under KVM in 64-bit mode\n" */
+
* @1: bus ID of the unit record device
* @1: z/VM virtual unit record device driver
* Description:
- * A request to suspend a unit record device being currently in use is
- * rejected.
+ * Linux cannot be suspended while a unit record device is in use.
* User action:
- * Terminate applications working on z/VM spool files queues (e.g. the
- * vmur user space tool) and then try to suspend the system again.
+ * Stop all applications that work on z/VM spool file queues, for example, the
+ * vmur tool. Then try again to suspend Linux.
*/
/*? Text: "%s loaded.\n" */
* adapter. Check your SAN setup and consider reducing the number of ports
* visible to the FCP adapter by using more restrictive zoning in the SAN.
*/
+
+/*?
+ * Text: "%s: A port opened with WWPN 0x%016Lx returned data that identifies it as WWPN 0x%016Lx\n"
+ * Severity: Warning
+ * Parameter:
+ * @1: bus ID of the zfcp device
+ * @2: expected WWPN
+ * @3: reported WWPN
+ * Description:
+ * A remote port was opened successfully, but it reported an
+ * unexpected WWPN in the returned port login (PLOGI) data. This
+ * condition might have been caused by a change applied to the SAN
+ * configuration while the port was being opened.
+ * User action:
+ * If this condition is only temporary and access to the remote port
+ * is possible, no action is required. If the condition persists,
+ * identify the storage system with the specified WWPN and contact the
+ * support organization of the storage system.
+ */
projects / linux-flexiantxendom0-3.2.10.git / commitdiff