[mirror_ubuntu-zesty-kernel.git] / Documentation / kmsg / s390 / monreader

/*?
 * Text: "Reading monitor data failed with rc=%i\n"
 * Severity: Error
 * Parameter:
 *   @1: return code
 * Description:
 * The z/VM *MONITOR record device driver failed to read monitor data
 * because the IUCV REPLY function failed. The read function against
 * the monitor record device returns EIO. All monitor data that has been read
 * since the last read with 0 size is incorrect.
 * User action:
 * Disregard all monitor data that has been read since the last read with
 * 0 size. If the device driver has been compiled as a separate module, unload
 * and reload the monreader module. If the device driver has been compiled
 * into the kernel, reboot Linux. For more information about possible causes
 * of the error see the IUCV section in "z/VM CP Programming Services" and
 * the *MONITOR section in "z/VM Performance".
 */

/*?
 * Text: "z/VM *MONITOR system service disconnected with rc=%i\n"
 * Severity: Error
 * Parameter:
 *   @1: IPUSER SEVER return code
 * Description:
 * The z/VM *MONITOR record device driver receives monitor records through
 * an IUCV connection to the z/VM *MONITOR system service. This connection
 * has been severed and the read function of the z/VM *MONITOR device driver
 * returns EIO. All data received since the last read with 0 size is incorrect.
 * User action:
 * Disregard all monitor data read since the last read with 0 size. Close and
 * reopen the monitor record device. For information about the IPUSER SEVER
 * return codes see "z/VM Performance".
 */

/*?
 * Text: "The read queue for monitor data is full\n"
 * Severity: Warning
 * Description:
 * The read function of the z/VM *MONITOR device driver returns EOVERFLOW
 * because not enough monitor data has been read since the monitor device
 * has been opened. Monitor data already read are valid and subsequent reads
 * return valid data but some intermediate data might be missing.
 * User action:
 * Be aware that monitor data might be missing. Assure that you regularly
 * read monitor data after opening the monitor record device.
 */

/*?
 * Text: "Connecting to the z/VM *MONITOR system service failed with rc=%i\n"
 * Severity: Error
 * Parameter:
 *   @1: IUCV CONNECT return code
 * Description:
 * The z/VM *MONITOR record device driver receives monitor records through
 * an IUCV connection to the z/VM *MONITOR system service. This connection
 * could not be established when the monitor record device was opened. If
 * the return code is 15, your z/VM guest virtual machine is not authorized
 * to connect to the *MONITOR system service.
 * User action:
 * If the return code is 15, ensure that the IUCV *MONITOR statement is
 * included in the z/VM directory entry for your z/VM guest virtual machine.
 * For other IUCV CONNECT return codes see the IUCV section in "CP Programming
 * Services" and the *MONITOR section in "z/VM  Performance".
 */

/*?
 * Text: "Disconnecting the z/VM *MONITOR system service failed with rc=%i\n"
 * Severity: Warning
 * Parameter:
 *   @1: IUCV SEVER return code
 * Description:
 * The z/VM *MONITOR record device driver receives monitor data through an
 * IUCV connection to the z/VM *MONITOR system service. This connection
 * could not be closed when the monitor record device was closed. You might
 * not be able to resume monitoring.
 * User action:
 * No immediate action is necessary. If you cannot open the monitor record
 * device in the future, reboot Linux. For information about the IUCV SEVER
 * return codes see the IUCV section in "CP Programming Services" and the
 * *MONITOR section in "z/VM  Performance".
 */

/*?
 * Text: "The z/VM *MONITOR record device driver cannot be loaded without z/VM\n"
 * Severity: Error
 * Description:
 * The z/VM *MONITOR record device driver uses z/VM system services to provide
 * monitor data about z/VM guest operating systems to applications on Linux.
 * On Linux instances that run in environments other than the z/VM hypervisor,
 * the z/VM *MONITOR record device driver does not provide any useful
 * function and the corresponding monreader module cannot be loaded.
 * User action:
 * Load the z/VM *MONITOR record device driver only on Linux instances that run
 * as guest operating systems of the z/VM hypervisor. If the z/VM *MONITOR
 * record device driver has been compiled into the kernel, ignore this message.
 */

/*?
 * Text: "The z/VM *MONITOR record device driver failed to register with IUCV\n"
 * Severity: Error
 * Description:
 * The z/VM *MONITOR record device driver receives monitor data through an IUCV
 * connection and needs to register with the IUCV device driver. This
 * registration failed and the z/VM *MONITOR record device driver was not
 * loaded. A possible cause of this problem is insufficient memory.
 * User action:
 * Free some memory and try again to load the module. If the z/VM *MONITOR
 * record device driver has been compiled into the kernel, you might have to
 * configure more memory and reboot Linux. If you do not want to read monitor
 * data, ignore this message.
 */

/*?
 * Text: "The specified *MONITOR DCSS %s does not have the required type SC\n"
 * Severity: Error
 * Parameter:
 *   @1: DCSS name
 * Description:
 * The DCSS that was specified with the monreader.mondcss kernel parameter or
 * with the mondcss module parameter cannot be a *MONITOR DCSS because it is
 * not of type SC.
 * User action:
 * Confirm that you are using the name of the DCSS that has been configured as
 * the *MONITOR DCSS on the z/VM hypervisor. If the default name, MONDCSS, is
 * used, omit the monreader.mondcss or mondcss parameter.
 */
/*? Text: "%s: %d output lines suppressed due to ratelimiting\n" */
Commit	Line	Data
aea13bde MS	1	/*?
	2	* Text: "Reading monitor data failed with rc=%i\n"
	3	* Severity: Error
	4	* Parameter:
	5	* @1: return code
	6	* Description:
	7	* The z/VM *MONITOR record device driver failed to read monitor data
	8	* because the IUCV REPLY function failed. The read function against
	9	* the monitor record device returns EIO. All monitor data that has been read
	10	* since the last read with 0 size is incorrect.
	11	* User action:
	12	* Disregard all monitor data that has been read since the last read with
	13	* 0 size. If the device driver has been compiled as a separate module, unload
	14	* and reload the monreader module. If the device driver has been compiled
	15	* into the kernel, reboot Linux. For more information about possible causes
	16	* of the error see the IUCV section in "z/VM CP Programming Services" and
	17	* the *MONITOR section in "z/VM Performance".
	18	*/
	19
	20	/*?
	21	* Text: "z/VM *MONITOR system service disconnected with rc=%i\n"
	22	* Severity: Error
	23	* Parameter:
	24	* @1: IPUSER SEVER return code
	25	* Description:
	26	* The z/VM *MONITOR record device driver receives monitor records through
	27	* an IUCV connection to the z/VM *MONITOR system service. This connection
	28	* has been severed and the read function of the z/VM *MONITOR device driver
	29	* returns EIO. All data received since the last read with 0 size is incorrect.
	30	* User action:
	31	* Disregard all monitor data read since the last read with 0 size. Close and
	32	* reopen the monitor record device. For information about the IPUSER SEVER
	33	* return codes see "z/VM Performance".
	34	*/
	35
	36	/*?
	37	* Text: "The read queue for monitor data is full\n"
	38	* Severity: Warning
	39	* Description:
	40	* The read function of the z/VM *MONITOR device driver returns EOVERFLOW
	41	* because not enough monitor data has been read since the monitor device
	42	* has been opened. Monitor data already read are valid and subsequent reads
	43	* return valid data but some intermediate data might be missing.
	44	* User action:
	45	* Be aware that monitor data might be missing. Assure that you regularly
	46	* read monitor data after opening the monitor record device.
	47	*/
	48
	49	/*?
	50	* Text: "Connecting to the z/VM *MONITOR system service failed with rc=%i\n"
	51	* Severity: Error
	52	* Parameter:
	53	* @1: IUCV CONNECT return code
	54	* Description:
	55	* The z/VM *MONITOR record device driver receives monitor records through
	56	* an IUCV connection to the z/VM *MONITOR system service. This connection
	57	* could not be established when the monitor record device was opened. If
	58	* the return code is 15, your z/VM guest virtual machine is not authorized
	59	* to connect to the *MONITOR system service.
	60	* User action:
	61	* If the return code is 15, ensure that the IUCV *MONITOR statement is
	62	* included in the z/VM directory entry for your z/VM guest virtual machine.
	63	* For other IUCV CONNECT return codes see the IUCV section in "CP Programming
	64	* Services" and the *MONITOR section in "z/VM Performance".
65	*/
66
67	/*?
68	* Text: "Disconnecting the z/VM *MONITOR system service failed with rc=%i\n"
69	* Severity: Warning
70	* Parameter:
71	* @1: IUCV SEVER return code
72	* Description:
73	* The z/VM *MONITOR record device driver receives monitor data through an
74	* IUCV connection to the z/VM *MONITOR system service. This connection
75	* could not be closed when the monitor record device was closed. You might
76	* not be able to resume monitoring.
77	* User action:
78	* No immediate action is necessary. If you cannot open the monitor record
79	* device in the future, reboot Linux. For information about the IUCV SEVER
80	* return codes see the IUCV section in "CP Programming Services" and the
81	* *MONITOR section in "z/VM Performance".
82	*/
83
84	/*?
85	* Text: "The z/VM *MONITOR record device driver cannot be loaded without z/VM\n"
86	* Severity: Error
87	* Description:
88	* The z/VM *MONITOR record device driver uses z/VM system services to provide
89	* monitor data about z/VM guest operating systems to applications on Linux.
90	* On Linux instances that run in environments other than the z/VM hypervisor,
91	* the z/VM *MONITOR record device driver does not provide any useful
92	* function and the corresponding monreader module cannot be loaded.
93	* User action:
94	* Load the z/VM *MONITOR record device driver only on Linux instances that run
95	* as guest operating systems of the z/VM hypervisor. If the z/VM *MONITOR
96	* record device driver has been compiled into the kernel, ignore this message.
97	*/
98
99	/*?
100	* Text: "The z/VM *MONITOR record device driver failed to register with IUCV\n"
101	* Severity: Error
102	* Description:
103	* The z/VM *MONITOR record device driver receives monitor data through an IUCV
104	* connection and needs to register with the IUCV device driver. This
105	* registration failed and the z/VM *MONITOR record device driver was not
106	* loaded. A possible cause of this problem is insufficient memory.
107	* User action:
108	* Free some memory and try again to load the module. If the z/VM *MONITOR
109	* record device driver has been compiled into the kernel, you might have to
110	* configure more memory and reboot Linux. If you do not want to read monitor
111	* data, ignore this message.
112	*/
113
114	/*?
115	* Text: "The specified *MONITOR DCSS %s does not have the required type SC\n"
116	* Severity: Error
117	* Parameter:
118	* @1: DCSS name
119	* Description:
120	* The DCSS that was specified with the monreader.mondcss kernel parameter or
121	* with the mondcss module parameter cannot be a *MONITOR DCSS because it is
122	* not of type SC.
123	* User action:
124	* Confirm that you are using the name of the DCSS that has been configured as
125	* the *MONITOR DCSS on the z/VM hypervisor. If the default name, MONDCSS, is
126	* used, omit the monreader.mondcss or mondcss parameter.
127	*/
128	/? Text: "%s: %d output lines suppressed due to ratelimiting\n" /