Kernel Messages - SUSE Linux Enterprise Server 12 · System z® specific Linux kernel modules on...

Linux on System z

Kernel Messageson SUSE Linux Enterprise Server 12

SC34-2747-00

��

Linux on System z

Kernel Messageson SUSE Linux Enterprise Server 12

SC34-2747-00

��

NoteBefore using this document, be sure to read the information in “Notices” on page 127.

This edition applies to SUSE Linux Enterprise Server 12 and to all subsequent releases and modifications untilotherwise indicated in new editions.

© Copyright IBM Corporation 2009, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . vOther relevant Linux on IBM System z publications v

Chapter 1. Displaying a message manpage . . . . . . . . . . . . . . . . 1

Chapter 2. Summary of prefixes . . . . 3

Chapter 3. aes_s390 . . . . . . . . . 9

Chapter 4. af_iucv . . . . . . . . . . 11

Chapter 5. ap . . . . . . . . . . . . 13

Chapter 6. appldata . . . . . . . . . 15

Chapter 7. cio. . . . . . . . . . . . 17

Chapter 8. claw . . . . . . . . . . . 19

Chapter 9. cpcmd . . . . . . . . . . 25

Chapter 10. cpu . . . . . . . . . . . 27

Chapter 11. cpum_cf . . . . . . . . . 29

Chapter 12. ctcm . . . . . . . . . . 31

Chapter 13. dasd-eckd . . . . . . . . 33

Chapter 14. dasd-fba. . . . . . . . . 49

Chapter 15. dasd . . . . . . . . . . 51

Chapter 16. dcssblk . . . . . . . . . 57

Chapter 17. extmem . . . . . . . . . 59

Chapter 18. hvc_iucv . . . . . . . . 63

Chapter 19. hypfs . . . . . . . . . . 65

Chapter 20. iucv. . . . . . . . . . . 67

Chapter 21. lcs . . . . . . . . . . . 69

Chapter 22. monreader . . . . . . . . 71

Chapter 23. monwriter . . . . . . . . 73

Chapter 24. netiucv . . . . . . . . . 75

Chapter 25. os_info . . . . . . . . . 77

Chapter 26. perf . . . . . . . . . . . 79

Chapter 27. qeth . . . . . . . . . . 81

Chapter 28. s390dbf . . . . . . . . . 87

Chapter 29. sclp_cmd . . . . . . . . 89

Chapter 30. sclp_config . . . . . . . 91

Chapter 31. scm_block . . . . . . . . 93

Chapter 32. setup . . . . . . . . . . 95

Chapter 33. tape. . . . . . . . . . . 97

Chapter 34. tape_34xx . . . . . . . . 99

Chapter 35. tape_3590 . . . . . . . 103

Chapter 36. time . . . . . . . . . . 105

Chapter 37. vmlogrdr . . . . . . . . 107

Chapter 38. vmur . . . . . . . . . . 109

Chapter 39. vmwatchdog . . . . . . 111

Chapter 40. xpram . . . . . . . . . 113

Chapter 41. zdump . . . . . . . . . 115

Chapter 42. zfcp . . . . . . . . . . 117

Chapter 43. zpci . . . . . . . . . . 123

Accessibility . . . . . . . . . . . . 125

Notices . . . . . . . . . . . . . . 127Trademarks . . . . . . . . . . . . . . 128

© Copyright IBM Corp. 2009, 2014 iii

iv Kernel Messages - SUSE Linux Enterprise Server 12

About this publication

This message reference document contains the messages that are issued by IBM®

System z® specific Linux kernel modules on SUSE Linux Enterprise Server 12.

On SUSE Linux Enterprise Server 12, these messages are issued with messagenumbers, which consist of a module identifier, a dot, and six hexadecimal digits. Inthis message reference the messages are grouped by the issuing module and listedin descending sort order.

Reasonable effort has been made to capture all kernel messages that are issuedwith message numbers on SUSE Linux Enterprise Server 12. For message numbersthat are not included in this book see the kernel messages book atwww.ibm.com/developerworks/linux/linux390/documentation_dev.html.

You can find the latest version of this publication on the developerWorks® websiteat www.ibm.com/developerworks/linux/linux390/documentation_suse.html

Other relevant Linux on IBM System z publicationsSeveral Linux on IBM System z publications for SUSE Linux Enterprise Server 12are available on developerWorks.

You can find the latest versions of these publications on developerWorks atwww.ibm.com/developerworks/linux/linux390/documentation_suse.htmlor on IBM Knowledge Center atibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_suse.htmlv Device Drivers, Features, and Commands on SUSE Linux Enterprise Server 12,

SC34-2745v Using the Dump Tools on SUSE Linux Enterprise Server 12, SC34-2746

For each of the following publications, you can find the version that most closelyreflects SUSE Linux Enterprise Server 12:v How to use FC-attached SCSI devices with Linux on System z, SC33-8413v libica Programmer's Reference, SC34-2602v Exploiting Enterprise PKCS #11 using openCryptoki, SC34-2713v Secure Key Solution with the Common Cryptographic Architecture Application

Programmer's Guide, SC33-8294v Linux on System z Troubleshooting, SC34-2612v Linux Health Checker User's Guide, SC34-2609v How to Improve Performance with PAV, SC33-8414v How to Set up a Terminal Server Environment on z/VM, SC34-2596

© Copyright IBM Corp. 2009, 2014 v

http://www.ibm.com/developerworks/linux/linux390/documentation_dev.html

http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html

http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html

http://www.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_suse.html

vi Kernel Messages - SUSE Linux Enterprise Server 12

Chapter 1. Displaying a message man page

This document lists System z specific kernel messages with message identifiers.SUSE Linux Enterprise Server 12 provides an RPM with a man page for each ofthese messages.

Before you begin

Ensure that the RPM with the message man pages is installed on your Linuxsystem. This RPM is called kernel-default-man-<kernel-version>s390x.rpm andshipped on DVD1.

Procedure

Enter a command of this form, to display a message man page:

# man <message_identifier>

Example

Enter the following command to display the man page for message xpram.ab9aa4:

# man xpram.ab9aa4

The corresponding man page looks like this:

xpram.ab9aa4(9) xpram.ab9aa4(9)

Messagexpram.ab9aa4: %d is not a valid number of XPRAM devices

SeverityError

Parameters@1: number of partitions

DescriptionThe number of XPRAM partitions specified for the ’devs’ module parame-ter or with the ’xpram.parts’ kernel parameter must be an integer inthe range 1 to 32. The XPRAM device driver created a maximum of 32 par-titions that are probably not configured as intended.

User actionIf the XPRAM device driver has been complied as a separate module,unload the module and load it again with a correct value for the’devs’ module parameter. If the XPRAM device driver has been compiledinto the kernel, correct the ’xpram.parts’ parameter in the kernelparameter line and restart Linux.

LINUX Linux Messages xpram.ab9aa4(9)

© Copyright IBM Corp. 2009, 2014 1

2 Kernel Messages - SUSE Linux Enterprise Server 12

Chapter 2. Summary of prefixes

The messages in this book are grouped by the prefixes used by the modules thatissue the message.

aes_s390

Messages with a prefix aes_s390 are issued by the kernel module that supports theSystem z hardware-accelerated implementation of the AES cipher algorithms(FIPS-197).

af_iucv

Messages with a prefix af_iucv are issued by the kernel module that supports theAF_IUCV address family for communication and addressing with z/VM® IUCV.

ap

Messages with a prefix ap are issued by the kernel module that supports specialprocessors for cryptographic operations.

appldata

Messages with a prefix appldata are issued by the kernel modules that gatherkernel performance data and statistics, and export this data to z/VM throughAPPLDATA monitor records.

cio

Messages with a prefix cio are issued by the kernel module that provides basic I/Ofunctions for channel-attached devices.

claw

Messages with a prefix claw are issued by the Common Link Access toWorkstation (CLAW) device driver.

cpcmd

Messages with a prefix cpcmd are issued by the cpcmd kernel function.

cpu

Messages with a prefix cpu are issued by the System z specific CPU managementfunctions.

cpum_cf

Messages with a prefix cpum_cf are issued by kernel functions that support thez/Architecture® CPU-measurement counter facility.


ctcm

Messages with a prefix ctcm are issued by the Channel-to-Channel (CTC) devicedriver. CTC connections are high-speed point-to-point connections between twooperating system instances on System z.

dasd-eckd

Messages with a prefix dasd-eckd are issued by the DASD device driver modulethat handles DASDs with the Extended Count Key Data (ECKD™) format.

dasd-fba

Messages with a prefix dasd-fba are issued by the DASD device driver modulethat handles DASDs with the Fixed Block Access (FBA) format.

dasd

Messages with a prefix dasd are issued by the DASD device driver.

dcssblk

Messages with a prefix dcssblk are issued by the z/VM discontiguous savedsegments (DCSS) device driver. The DCSS device driver provides disk-like fixedblock access to z/VM discontiguous saved segments.

extmem

Messages with a prefix extmem are issued by the kernel module that provides aninterface to the z/VM DCSS management functions.

hvc_iucv

Messages with a prefix hvc_iucv are issued by the z/VM IUCV HypervisorConsole (HVC) device driver. This device driver supports terminal access throughthe iucvconn program to instances of Linux on z/VM.

hypfs

Messages with a prefix hypfs are issued by the S/390® hypervisor file system,which provides access to LPAR and z/VM hypervisor data.

iucv

Messages with a prefix iucv are issued by the Inter-User Communication Vehicle(IUCV) device driver. IUCV is a z/VM communication facility that enables aprogram running in one z/VM guest to communicate with another z/VM guest, orwith a control program, or even with itself.

lcs

Messages with a prefix lcs are issued by the LAN channel station device driver.The LCS device driver supports non-QDIO communications through Open SystemsAdapters (OSA).


monreader

Messages with a prefix monreader are issued by the z/VM *MONITOR recordreader device driver. This device driver enables monitoring software on Linux toaccess z/VM *MONITOR records, which contain data about z/VM guest virtualmachines.

monwriter

Messages with a prefix monwriter are issued by the monitor stream applicationdevice driver. Applications can use this device driver to write monitor data in theform of APPLDATA records to the z/VM monitor stream.

netiucv

Messages with a prefix netiucv are issued by the NETIUCV device driver. Thisnetwork device driver uses IUCV to connect instances of Linux on z/VM, or toconnect an instance of Linux on z/VM to another z/VM guest such as a TCP/IPservice machine.

os_info

Messages with a prefix os_info are issued by Linux in kdump mode.

perf

Messages with a prefix perf are issued by kernel functions that support thez/Architecture CPU-measurement facility.

qeth

Messages with a prefix qeth are issued by the qeth device driver. The qeth devicedriver supports a multitude of network connections, for example, connectionsthrough Open Systems Adapters (OSA), HiperSockets™, guest LANs, and virtualswitches.

s390dbf

Messages with a prefix s390dbf are issued by the S/390 debug feature.

sclp_cmd

Messages with a prefix sclp_cmd are issued in the context of SCLP commands.

sclp_config

Messages with a prefix sclp_config are issued by SCLP configuration managementevents.

scm_block

Messages with a prefix scm_block are issued by the storage-class memory (SCM)device driver.

Chapter 2. Summary of prefixes 5

setup

Messages with a prefix “setup” are issued when Linux starts.

tape

Messages with a prefix “tape” are issued by the channel-attached tape devicedriver.

tape_34xx

Messages with a prefix tape_34xx are issued by the channel-attached tape devicedriver and relate to an IBM 3480 or IBM 3490 magnetic tape subsystem.

tape_3590

Messages with a prefix tape_3590 are issued by the channel-attached tape devicedriver and relate to an IBM 3590 or IBM 3592 magnetic tape subsystem.

time

Messages with a prefix “time” are issued by the System z specific time functions.

vmlogrdr

Messages with a prefix vmlogrdr are issued by the z/VM recording device driver.With the z/VM recording device driver, an instance of Linux on z/VM can readfrom the z/VM CP recording services.

vmur

Messages with a prefix vmur are issued by the z/VM virtual unit record devicedriver. This device driver provides Linux with access to z/VM virtual unit recorddevices like punch card readers, card punches, and line printers.

vmwatchdog

Messages with a prefix vmwatchdog are issued by the watchdog device driver.With the watchdog device driver, a watchdog application on an instance of Linuxon z/VM can access the z/VM watchdog timer.

xpram

Messages with a prefix xpram are issued by the XPRAM device driver. This blockdevice driver enables Linux on System z to access expanded storage.

zdump

Messages with a prefix zdump are issued by the zfcpdump functions.

zfcp

Messages with a prefix zfcp are issued by the SCSI-over-Fibre Channel devicedriver (zfcp device driver) for the QDIO-based System z SCSI-over-Fibre Channeladapter. The zfcp device driver supports Fibre Channel-attached SCSI devices onLinux on System z.


zpci

Messages with a prefix zpci are issued by the kernel module that provides PCIesupport.

Chapter 2. Summary of prefixes 7


Chapter 3. aes_s390

Messages with a prefix aes_s390 are issued by thekernel module that supports the System zhardware-accelerated implementation of the AEScipher algorithms (FIPS-197).

aes_s390.cb83bb AES hardware acceleration is onlyavailable for 128-bit keys

Explanation: The advanced encryption standard (AES)algorithm includes three modes with 128-bit, 192-bit,and 256-bit keys. Your hardware system only provideshardware acceleration for the 128-bit key mode. Theaes_s390 module will use the less performant softwarefallback algorithm for the 192-bit and 256-bit keymodes.

User response: None.

Severity: Informational

aes_s390.dc0a3b Allocating AES fallback algorithm<algorithm name> failed

Explanation: The advanced encryption standard (AES)algorithm includes three modes with 128-bit, 192-bit,and 256-bit keys. Your hardware system only provideshardware acceleration for the 128-bit mode. Theaes_s390 module failed to allocate a software fallbackfor the AES modes that are not supported by thehardware. A possible reason for this problem is that theaes_generic module that provides the fallbackalgorithms is not available.

User response: Use the 128-bit mode only or ensurethat the aes_generic module is available and loadedand reload the aes_s390 module.

Severity: Error

aes_s390.e37463 Allocating XTS fallback algorithm<algorithm name> failed

Explanation: The aes_s390 module failed to allocate asoftware fallback for the AES modes that are notsupported by the hardware. A possible reason for thisproblem is that the aes_generic module that providesthe fallback algorithms is not available.

User response: Ensure that the aes_generic module isavailable and loaded and reload the aes_s390 module.

Severity: Error



Chapter 4. af_iucv

Messages with a prefix af_iucv are issued by thekernel module that supports the AF_IUCVaddress family for communication and addressingwith z/VM IUCV.

af_iucv.5c08c7 Application <application name> onz/VM guest <z/VM user ID> exceedsmessage limit

Explanation: Messages or packets destined for theapplication have accumulated and reached themaximum value. The default for the message limit is65535. You can specify a different limit as the value forMSGLIMIT within the IUCV statement of the z/VMvirtual machine on which the application runs.

User response: Ensure that you do not send datafaster than the application retrieves them. Ensure thatthe message limit on the z/VM guest virtual machineon which the application runs is high enough.

Severity: Error



Chapter 5. ap

Messages with a prefix ap are issued by thekernel module that supports special processorsfor cryptographic operations.

ap.3677f7 The hardware system does not supportAP instructions

Explanation: The ap module addresses AP adaptersthrough AP instructions. The hardware system onwhich the Linux instance runs does not support APinstructions. The ap module cannot detect any APadapters.

User response: Load the ap module only if yourLinux instance runs on hardware that supports APinstructions. If the ap module has been compiled intothe kernel, ignore this message.

Severity: Warning

ap.7564a4 <AP domain index> is not a validcryptographic domain

Explanation: The cryptographic domain specified forthe 'domain=' module or kernel parameter must be aninteger in the range 0 to 15.

User response: Reload the cryptographic device driverwith a correct module parameter. If the device driverhas been compiled into the kernel, correct the value inthe kernel parameter line and reboot Linux.

Severity: Warning

ap.fce52f Registering adapter interrupts for AP<AP device ID> failed

Explanation: The hardware system supports APadapter interrupts but failed to enable an adapter forinterrupts. Possible causes for this error are: i) The APadapter firmware does not support AP interrupts. ii)An AP adapter firmware update to a firmware levelthat supports AP adapter interrupts failed. iii) The APadapter firmware has been successfully updated to alevel that supports AP interrupts but the new firmwarehas not been activated.

User response: Ensure that the firmware on your APadapters support AP interrupts and that any firmwareupdates have completed successfully. If necessary,deconfigure your cryptographic adapters andreconfigure them to ensure that any firmware updatesbecome active, then reload the ap module. If the apmodule has been compiled into the kernel, rebootLinux.

Severity: Error



Chapter 6. appldata

Messages with a prefix appldata are issued by thekernel modules that gather kernel performancedata and statistics, and export this data to z/VMthrough APPLDATA monitor records.

appldata.0ae163 Stopping the data collection for<appldata module> failed with rc=<returncode>

Explanation: The specified data collection moduleused the z/VM diagnose call DIAG 0xDC to stopwriting data. z/VM returned an error and the datacollection continues.

User response: See the section about DIAGNOSECode X'DC' in "z/VM CP Programming Services".

Severity: Error

appldata.81e326 Maximum OS record size <no ofbytes> exceeds the maximum record size<no of bytes>

Explanation: The OS record size grows with thenumber of CPUs and is adjusted by the appldata_osmodule in response to CPU hotplug events. For morethan 110 CPUs the record size would exceed themaximum record size of 4024 bytes that is supportedby the z/VM hypervisor. To prevent the maximumsupported record size from being exceeded while datacollection is in progress, you cannot load theappldata_os module on Linux instances that areconfigured for a maximum of more than 110 CPUs.

User response: If you do not want to collect operatingsystem data, you can ignore this message. If you wantto collect operating system data, reconfigure yourLinux instance to support less than 110 CPUs.

Severity: Error

appldata.887845 Stopping a faulty OS data collectionfailed with rc=<return code>

Explanation: After a CPU hotplug event, the recordsize for the running operating system data collection isno longer correct. The appldata_os module tried to stopthe faulty data collection but received an error from thez/VM diagnose call DIAG 0xDC. Any data collectedwith the current record size might be faulty.

User response: Try to restart appldata_os monitoring.For information about stopping and starting datacollections see "Device Drivers, Features, andCommands". For information about the return codessee the section about DIAGNOSE Code X'DC' in"z/VM CP Programming Services".

Severity: Error

appldata.ccf8e3 Starting a new OS data collectionfailed with rc=<return code>

Explanation: After a CPU hotplug event, the recordsize for the running operating system data collection isno longer correct. The appldata_os module tried to starta new data collection with the correct record size butreceived an error from the z/VM diagnose call DIAG0xDC. Any data collected with the current record sizemight be faulty.

User response: Start a new data collection with thecappldata_os module. For information about startingdata collections see "Device Drivers, Features, andCommands". For information about the return codessee the section about DIAGNOSE Code X'DC' in"z/VM CP Programming Services".

Severity: Error

appldata.f26e28 Starting the data collection for<appldata module> failed with rc=<returncode>

Explanation: The specified data collection moduleused the z/VM diagnose call DIAG 0xDC to startwriting data. z/VM returned an error and the datacollection could not start. If the return code is 5, yourz/VM guest virtual machine is not authorized to writedata records.

User response: If the return code is 5, ensure thatyour z/VM guest virtual machine's entry in the z/VMdirectory includes the OPTION APPLMON statement.For other return codes see the section aboutDIAGNOSE Code X'DC' in "z/VM CP ProgrammingServices".

Severity: Error



Chapter 7. cio

Messages with a prefix cio are issued by thekernel module that provides basic I/O functionsfor channel-attached devices.

cio.0e0832 <device number>: No interrupt wasreceived within <timeout value>(CS=<channel status>, DS=<device status>,CHPID=<channel subsystemID>.<CHPID>)

Explanation: Internal I/Os are used by the commonI/O layer to ensure that devices are operational andaccessible. The common I/O layer did not receive aninterrupt for an internal I/O during the specifiedtimeout period. As a result, the device might assume astate that makes the device unusable to Linux until theproblem is resolved.

User response: Make sure that the device is workingcorrectly and try the action again.

Severity: Warning

cio.0f6270 No CCW console was found

Explanation: Linux did not find the expected CCWconsole and tries to use an alternative console. Apossible reason why the console was not found is thatthe console has been specified in the cio_ignore list.

User response: None, if an appropriate alternativeconsole has been found, and you want to use thisalternative console. If you want to use the CCWconsole, ensure that is not specified in the cio_ignorelist, explicitly specify the console with the 'condev='kernel parameter, and reboot Linux.

Severity: Warning

cio.1c5e61 <Device bus-ID>: The device enteredboxed state while being set offline

Explanation: While the device was set offline, it didnot respond in time or it was reserved by anotheroperating system. The device is now inactive, butsetting it online again might fail.


Severity: Warning

cio.2943d5 Processing <configuration change> forchannel path <channel subsystemID>.<CHPID>

Explanation: A configuration change is in progress forthe given channel path.


Severity: Notice

cio.2b995e <device bus-ID> is not a valid device forthe cio_ignore kernel parameter

Explanation: The device specification for thecio_ignore kernel parameter is syntactically incorrect orspecifies an unknown device. This device is notexcluded from being sensed and analyzed.

User response: Correct your device specification in thekernel parameter line to have the device excludedwhen you next reboot Linux. You can write the correctdevice specification to /proc/cio_ignore to add thedevice to the list of devices to be excluded. This doesnot immediately make the device inaccessible but thedevice is ignored if it disappears and later reappears.

Severity: Warning

cio.390dcf <Device bus-ID>: The device stoppedoperating while being set offline

Explanation: While the device was set offline, it wasnot present or not operational. The device is nowinactive, but setting it online again might fail.


Severity: Warning

cio.582533 Logging for subchannel 0.<subchannel setID>.<subchannel number> was triggered

Explanation: Model-dependent logs and traces may becaptured for the specified subchannel.


Severity: Notice

cio.5b32ec 0.<from subchannel set ID>.<from devicenumber> to 0.<to subchannel set ID>.<todevice number> is not a valid range forcio_ignore

Explanation: The device range specified for thecio_ignore kernel parameter is syntactically incorrect.No devices specified with this range are excluded frombeing sensed and analyzed.

User response: Correct your range specification in thekernel parameter line to have the range of devicesexcluded when you next reboot Linux. You can writethe correct range specification to /proc/cio_ignore toadd the range of devices to the list of devices to beexcluded. This does not immediately make the devices


in the range inaccessible but any of these devices areignored if they disappear and later reappear.

Severity: Warning

cio.7a35c2 Logging for subchannel 0.<subchannel setID>.<subchannel number> failed witherrno=<errno>

Explanation: Capturing model-dependent logs andtraces could not be triggered for the specifiedsubchannel.

User response: See the errno man page to find outwhat caused the problem.

Severity: Warning

cio.8665f1 The CSS device driver initializationfailed with errno=<Return code>

Explanation: The channel subsystem bus could not beestablished.

User response: See the errno man page to find outwhat caused the problem.

Severity: Alert

cio.8e4d4c <Device bus-ID>: Setting the deviceonline failed because it is boxed

Explanation: Initialization of a device did notcomplete because it did not respond in time or it wasreserved by another operating system.

User response: Make sure that the device is workingcorrectly, then try again to set it online. For devices thatsupport the reserve/release mechanism (for exampleDASDs), you can try to override the reservation of theother system by writing 'force' to the 'online' sysfsattribute of the affected device.

Severity: Warning

cio.96a34f <Device bus-ID>: Setting the deviceonline failed because it is notoperational

Explanation: Initialization of a device did notcomplete because it is not present or not operational.

User response: Make sure that the device is presentand working correctly, then try again to set it online.

Severity: Warning

cio.b5d5f6 Channel measurement facility initializedusing format <format> (mode <mode>)

Explanation: The channel measurement facility hasbeen initialized successfully. Format 'extended' shouldbe used for z990 and later mainframe systems. Format'basic' is intended for earlier mainframes. Mode'autodetected' means that the format has been set

automatically. Mode 'parameter' means that the formathas been set according to the 'format=' kernelparameter.



cio.7a35c2 • cio.b5d5f6


Chapter 8. claw

Messages with a prefix claw are issued by theCommon Link Access to Workstation (CLAW)device driver.

claw.182198 <bus ID of the CLAW device>: Setting thewrite subchannel online failed witherror code <errno>

Explanation: Setting the Common Link Access toWorkstation (CLAW) device online failed with an errorfor the write subchannel. This problem occurs, forexample, if the write subchannel used to create theCLAW group device is not defined as a CLAW writesubchannel in the hardware definitions. The CLAWwrite subchannel must be for a 3088 device of typex'61' and have an uneven bus ID. The bus ID of thewrite subchannel can be found from the symbolic link/sys/bus/ccwgroup/drivers/claw/<device-bus-ID>/cdev1 where <device-bus-ID> is the bus ID of theCLAW device.

User response: Confirm that you are using the correctbus ID for the write subchannel. If necessary, ungroupthe device and recreate it with the correct bus ID.Assure that the write subchannel has been definedcorrectly to the real or virtual hardware, for example, inyour IOCDS or in your z/VM configuration. Assurethat a valid number of write buffers has been assignedto the device. See 'Device Drivers, Features, andCommands' for details about the read buffers. See theerrno man page for information about the error code.

Severity: Warning

claw.24e119 <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> disconnected

Explanation: The Common Link Access to Workstation(CLAW) device driver received a device status wordDEV_STAT_UNIT_CHECK and sense code 0x41. Thisindicates that the remote network interface is no longeravailable.

User response: Ensure that the remote channeladapter is operational and activate the remote interface.For information about the sense code see/Documentation/s390/cds.txt in the Linux source tree.Search for 'SNS0' to locate the information.

Severity: Warning

claw.379c1e <bus ID of the CLAW device>: Setting theread subchannel online failed with errorcode <errno>

Explanation: Setting the Common Link Access to

Workstation (CLAW) device online failed with an errorfor the read subchannel. This problem occurs, forexample, if the read subchannel used to create theCLAW group device is not defined as a CLAW readsubchannel in the hardware definitions. The CLAWread subchannel must be for a 3088 device of type x'61'and have an even bus ID. The bus ID of the readsubchannel matches the bus ID of the CLAW device.

User response: Confirm that you are using the correctbus ID for the read subchannel. If necessary, ungroupthe device and recreate it with the correct bus ID.Assure that the read subchannel has been definedcorrectly to the real or virtual hardware, for example, inyour IOCDS or in your z/VM configuration. Assurethat a valid number of read buffers has been assignedto the device. See 'Device Drivers, Features, andCommands' for details about the read buffers. See theerrno man page for information about the error code.

Severity: Warning

claw.37e392 <bus ID of the CLAW device>: The statusof the remote channel adapter is notvalid

Explanation: During an operation, the Common LinkAccess to Workstation (CLAW) device driver receivederrno EINVAL from the common I/O layer. Thisindicates that the remote channel adapter was offline ornot operational.

User response: Check for related error messages tofind the cause of the problem. If necessary, restart theremote channel adapter.

Severity: Error

claw.3f4182 <bus ID of the CLAW device>: The localread buffer is smaller than the remotewrite buffer

Explanation: You set the buffer size for the localCommon Link Access to Workstation (CLAW) deviceimplicitly by setting the connection type. Forconnection type 'packed' the buffer size is 32 KB, forthe other connection types the buffer size is 4 KB. Theconnection cannot be established because the readbuffer size of the local CLAW device does not matchthe write buffer size of the communication peer.

User response: Confirm that you are using the correctconnection type for the local CLAW device. Ensure thatthe write buffer size of the remote CLAW device is setaccordingly. Restart the CLAW device, local or remote,for which you have made corrections.

Severity: Warning


claw.4b316e <bus ID of the CLAW device>: Allocating abuffer for incoming data failed

Explanation: A Common Link Access to Workstation(CLAW) data packet was received but the CLAWdevice driver could not allocate a receive buffer. Apossible cause of this problem is memory constraints.The data packet is dropped but the connection remainsoperational.

User response: Ensure that sufficient memory isavailable. If this problem occurs frequently, restart theremote CLAW device. If this does not resolve the error,gather logs and traces from the remote CLAW device toobtain further diagnostic data.


claw.50a02b <bus ID of the device>: The device is not aCLAW device

Explanation: The Common Link Access to Workstation(CLAW) device driver received a channel interrupt(IRQ) for a subchannel that is not a CLAW read orwrite subchannel. A CLAW subchannel must beconfigured for a 3088 device of type x'61' and have aneven bus ID.

User response: Assure that the subchannels have beendefined correctly to the real or virtual hardware, forexample, in your IOCDS or in your z/VMconfiguration.

Severity: Warning

claw.5355ea <bus ID of the CLAW device>:Deactivating <network interface name>completed with incorrect subchannelstatus (read <read subchannel status>,write <write subchannel status>)

Explanation: When the Common Link Access toWorkstation (CLAW) device driver closes a CLAWdevice, the device driver frees all storage that is usedfor the device. A successful closing operation results instatus DEVICE END and CHANNEL END for both theread and write subchannel. At least one of thesestatuses is missing for a subchannel. Data might havebeen lost and there might be problems when thenetwork interface is activated again.

User response: If the network interface cannot beactivated, vary the subchannels for the device offlineand back online, for example, with chchp. If this doesnot resolve the problem, reset the remote channeladapter.

Severity: Warning

claw.55352b <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> uses an incorrect API version<CLAW API version>

Explanation: The Common Link Access to Workstation(CLAW) device driver received aSYSTEM_VALIDATE_REQUEST packet from theremote channel adapter. The packet included anunexpected version ID for the CLAW API. The versionID must be '2' for all packets.

User response: Ensure that the remote channeladapter is at the latest firmware level. Restart theremote channel adapter and activate the remoteinterface. If the problem persists, examine thesubchannel trace for further diagnostic information.

Severity: Warning

claw.5bd403 <bus ID of the CLAW device>: Creating aCLAW group device failed with errorcode <errno>

Explanation: The Common Link Access to Workstation(CLAW) device driver failed to create a CLAW groupdevice. A possible cause of this problem is memoryconstraints.

User response: Ensure that there is sufficient freememory. See the errno man page and look for relatedmessages to find out what caused the problem. If youcannot resolve the problem, contact your supportorganization.

Severity: Warning

claw.68529a <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> rejected the connection

Explanation: The remote CLAW device rejected theconnection because of a mismatch between the settingsof the local CLAW device and the remote CLAWdevice.

User response: Check the settings of both the localand the remote CLAW device and ensure that thesettings are consistent. Restart the CLAW device, localor remote for which you have made the correction.

Severity: Warning

claw.6c9677 <bus ID of the CLAW device>: Anuninitialized CLAW device received anIRQ, c-<subchannel status> d-<devicestatus>

Explanation: A Common Link Access to Workstation(CLAW) device was not initialized when it received achannel interrupt (IRQ). The IRQ is ignored. This mightbe a temporary condition while the device comesonline or is taken offline.

claw.4b316e • claw.6c9677


User response: If this problem occurs frequently, usethe status information from the message and thechannel and device traces to analyze the problem. See"Principles of Operation" for details about of the statusinformation.

Severity: Warning

claw.6d0a8f <bus ID of the CLAW device>: Activatingthe CLAW device failed

Explanation: Activating the Common Link Access toWorkstation (CLAW) device failed. A possible cause ofthis problem is memory constraints.

User response: Free some memory and try again toactivate the CLAW device. If the problem persists,contact your support organization.

Severity: Warning

claw.70b434 <bus ID of the CLAW device>: The CLAWdevice for <network interface name>received an unexpected IRQ

Explanation: A Common Link Access to Workstation(CLAW) device received a channel interrupt (IRQ)while the CLAW device driver had assigned a status tothe device in which it cannot process IRQs. The IRQ isignored.

User response: Restart the remote channel adapter. Ifthe problem persists, use s390dbf traces and CCWtraces to diagnose the problem.

Severity: Warning

claw.70e156 <bus ID of the CLAW device>: Validating<network interface name> failed because ofa frame size conflict

Explanation: You set the frame size for the localCommon Link Access to Workstation (CLAW) deviceimplicitly by setting the connection type. Forconnection type 'packed' the frame size is 32 KB, forthe other connection types the frame size is 4 KB. Theconnection cannot be activated because the the framesize of the local CLAW device does not match theframe size of the communication peer.

User response: Confirm that you are using the correctconnection type for the local CLAW device. Ensure thatthe frame size of the remote CLAW device is setaccordingly. Restart the CLAW device, local or remote,for which you have have made corrections.

Severity: Warning

claw.7466e6 <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> failed

Explanation: The remote Common Link Access toWorkstation (CLAW) device reported an error condition

that cannot be recovered automatically.

User response: Restart the remote CLAW device. Ifthis does not resolve the error, gather logs and tracesfrom the remote CLAW device to obtain furtherdiagnostic data.

Severity: Warning

claw.74be71 <bus ID of the CLAW device>: The remotechannel adapter is not available

Explanation: During an operation, the Common LinkAccess to Workstation (CLAW) device driver receivederrno ENODEV from the common I/O layer. Thismeans that the remote channel adapter was notoperational or offline.

User response: Check the remote channel adapter and,if necessary, restart it.

Severity: Error

claw.76b4f5 <bus ID of the CLAW device>: The remotechannel adapter for <network interfacename> has been reset

Explanation: The Common Link Access to Workstation(CLAW) device driver received a device status wordDEV_STAT_UNIT_CHECK and sense code 0x40. Thisindicates that the remote channel adapter has beenreset.

User response: When the remote channel adapter isoperational again, activate the remote interface. Forinformation about the sense code see/Documentation/s390/cds.txt in the Linux source tree.Search for 'SNS0' to locate the information.

Severity: Warning

claw.7797f9 <bus ID of the CLAW device>: <networkinterface name> rejected a request to openmultiple connections

Explanation: The Common Link Access to Workstation(CLAW) device rejected a request by its communicationpeer to open more than one connection. The CLAWdevice driver only supports a single connection foreach CLAW device.

User response: Reconfigure the remote CLAW deviceto only use one connection. Restart the remote CLAWdevice.


claw.7c1758 Registering with the S/390 debugfeature failed with error code <errno>

Explanation: The Common Link Access to Workstation(CLAW) device driver failed to register with the S/390debug feature. No debug traces will be available forCLAW.

claw.6d0a8f • claw.7c1758

Chapter 8. claw 21

User response: Enter 'lsmod | grep dbf' or anequivalent command to check if the S/390 debugfeature loaded. If the output does not show the dbfmodule, the S/390 debug feature has not been loaded,unload the CLAW device driver, load the debugfeature, then reload the CLAW device driver. See theerrno man page for information about the error code.

Severity: Error

claw.7f27d6 <bus ID of the CLAW device>: The remotechannel adapter for <network interfacename> is faulty

Explanation: The Common Link Access to Workstation(CLAW) device driver received a device status wordDEV_STAT_UNIT_CHECK and sense code 0x30. Thisindicates that the remote channel adapter is faulty.

User response: Check and restart the remote channeladapter and activate the remote interface. If theproblem persists, perform device diagnosis for theremote channel adapter and examine the subchanneltrace for further diagnostic information. Forinformation about the sense code see/Documentation/s390/cds.txt in the Linux source tree.Search for 'SNS0' to locate the information.

Severity: Warning

claw.81d266 <bus ID of the CLAW device>: The CLAWdevice received an unexpected IRQ,c-<subchannel status> d-<device status>

Explanation: A Common Link Access to Workstation(CLAW) device received a channel interrupt (IRQ)while it was in a state in which it cannot process IRQs.The IRQ is ignored. This might be a temporarycondition.

User response: If this problem occurs frequently, usethe status information from the message and thechannel and device traces to analyze the problem. See"Principles of Operation" for details about the statusinformation.

Severity: Warning

claw.858a92 <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> rejected a connection request

Explanation: The remote CLAW device detected aninconsistency in the configurations of the local and theremote CLAW device and rejected a connection request.

User response: Examine the settings of your local andremote CLAW device. Correct the erroneous setting andrestart the CLAW device, local or remote, for whichyou have made corrections.

Severity: Warning

claw.887cf5 <bus ID of the CLAW device>: Validating<network interface name> failed because ofa version conflict

Explanation: The Common Link Access to Workstation(CLAW) network interface cannot be activated becausethe remote CLAW device does not support CLAWversion 2. The CLAW device driver requires CLAWversion 2.

User response: Ensure that the remote channeladapter supports CLAW version 2 and that the remoteCLAW device is configured for CLAW version 2.

Severity: Warning

claw.89e5ba <bus ID of the CLAW device>: Adaptername <adapter name in the local CLAWdevice settings> for <network interfacename> does not match the remote hostname <host name in the remote CLAWdevice settings>

Explanation: The adapter name in the local CommonLink Access to Workstation (CLAW) device settingsmust match the host name in the CLAW device settingsof the communication peer. The CLAW device driverdiscovered a mismatch between these settings. Theconnection cannot be established.

User response: Check the configuration of the CLAWdevice and of its communication peer. Correct theerroneous setting and restart the CLAW device, local orremote, for which you have made corrections.

Severity: Warning

claw.9bd9c2 <bus ID of the CLAW device>: <networkinterface name> rejected a connectionrequest because it is already active

Explanation: The Common Link Access to Workstation(CLAW) device rejected a connection request by itscommunication peer because the connection is alreadyactive. The CLAW device driver only supports a singleconnection for each CLAW device. This might be aruntime problem.

User response: None if there is an active connection.If no connection can be established, restart the remotechannel adapter.


claw.a84a95 <bus ID of the CLAW device>: The localwrite buffer is smaller than the remoteread buffer

Explanation: You set the buffer size for the localCommon Link Access to Workstation (CLAW) deviceimplicitly by setting the connection type. Forconnection type 'packed' the buffer size is 32 KB, forthe other connection types the buffer size is 4 KB. Theconnection cannot be established because the write

claw.7f27d6 • claw.a84a95


buffer size of the local CLAW device does not matchthe read buffer size of the communication peer.

User response: Confirm that you are using the correctconnection type for the local CLAW device. Ensure thatthe read buffer size of the remote CLAW device is setaccordingly. Restart the CLAW device, local or remote,for which you have made corrections.

Severity: Warning

claw.a94684 <bus ID of the CLAW device>: Validating<network interface name> failed because ofa host or adapter name mismatch

Explanation: The Common Link Access to Workstation(CLAW) network interface cannot be activated becausethere is a mismatch between a host name and thecorresponding adapter name. The local host name mustmatch the remote adapter name and the local adaptername must match the remote host name.

User response: Correct the erroneous setting andrestart the CLAW device, local or remote, for whichyou have made corrections.

Severity: Warning

claw.abecae <bus ID of the CLAW device>: A datastreaming timeout occurred for <networkinterface name>

Explanation: The Common Link Access to Workstation(CLAW) device driver received a device status wordDEV_STAT_UNIT_CHECK and sense code 0x24. Thisindicates a data streaming timeout. The remote channeladapter or the channel might be faulty.

User response: Restart the remote channel adapterand activate the remote interface. If the problempersists, examine the subchannel trace for furtherdiagnostic information. For information about the sensecode see /Documentation/s390/cds.txt in the Linuxsource tree. Search for 'SNS0' to locate the information.

Severity: Warning

claw.b13754 <bus ID of the CLAW device>: Settings for<network interface name> validated(version=<CLAW API version>, remotedevice=<identifier for the remote CLAWdevice>, rc=<return code received from theremote CLAW device>, adaptername=<adapter name>, host name=<hostname>)

Explanation: The settings of the local Common LinkAccess to Workstation (CLAW) device have beenvalidated by the communication peer. The messagesummarizes the content of the response. If the returncode is zero, the validation was successful and theconnection is activated.

User response: If the return code is not equal to zero,

look for related warning messages.


claw.b322ac <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> sent a faulty frame of length<incorrect frame length value>

Explanation: The remote Common Link Access toWorkstation (CLAW) device sent a frame with anincorrect value in the length field. This problem mightresult from data errors or incorrect packing. Theconnection remains operational.

User response: If this problem occurs frequently,restart the remote CLAW device. If this does notresolve the error, gather logs and traces from theremote CLAW device to obtain further diagnostic data.

Severity: Warning

claw.b40a6a <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> rejected a connection requestbecause of a type mismatch

Explanation: The remote Common Link Access toWorkstation (CLAW) device rejected a request to opena connection. A connection can only be opened if thesame connection type has been set for both the localand the remote CLAW device.

User response: Ensure that the connection types forthe local and remote CLAW device match. Restart theCLAW device, local or remote, for which you havechanged the connection type.

Severity: Warning

claw.b85501 <bus ID of the CLAW device>: Thecommunication peer of <network interfacename> sent an unknown command code

Explanation: The remote Common Link Access toWorkstation (CLAW) device sent a command code thatis not defined. This might indicate that the remoteCLAW device is malfunctioning. The connectionremains operational.

User response: If this problem occurs frequently,restart the remote CLAW device. If this does notresolve the error, gather logs and traces from theremote CLAW device to obtain further diagnostic data.

Severity: Warning

claw.c06c67 <bus ID of the CLAW device>: A read dataparity error occurred for <networkinterface name>

Explanation: The Common Link Access to Workstation(CLAW) device driver received a device status wordDEV_STAT_UNIT_CHECK and sense code 0x10. This

claw.a94684 • claw.c06c67

Chapter 8. claw 23

indicates a read data parity error. The remote channeladapter might be faulty.

User response: Ensure that all cables are securelyplugged. Check and restart the remote channel adapterand activate the remote interface. If the problempersists, perform device diagnosis for the remotechannel adapter and examine the subchannel trace forfurther diagnostic information. For information aboutthe sense code see /Documentation/s390/cds.txt in theLinux source tree. Search for 'SNS0' to locate theinformation.

Severity: Warning

claw.ce65ab <bus ID of the CLAW device>: Host name<host name in the local CLAW devicesettings> for <network interface name> doesnot match the remote adapter name<adapter name in the remote CLAW devicesettings>

Explanation: The host name in the local CommonLink Access to Workstation (CLAW) device settingsmust match the adapter name in the CLAW devicesettings of the communication peer. The CLAW devicedriver discovered a mismatch between these settings.The connection cannot be established.

User response: Check the configuration of the CLAWdevice and of its communication peer. Correct theerroneous setting and restart the CLAW device, local orremote, for which you have made corrections.

Severity: Warning

claw.d99a9c <bus ID of the CLAW device>: <networkinterface name> rejected a connectionrequest because of a type mismatch

Explanation: The Common Link Access to Workstation(CLAW) device rejected a request by its communicationpeer to open a connection. A connection can only beopened if the same connection type has been set forboth the local and the remote CLAW device.

User response: Ensure that the connection types forthe local and remote CLAW device match. Restart theCLAW device, local or remote, for which you havechanged the connection type.


claw.e52567 <bus ID of the CLAW device>: A datatransfer parity error occurred for<network interface name>

Explanation: The Common Link Access to Workstation(CLAW) device driver received a device status wordDEV_STAT_UNIT_CHECK and sense code 0x20. Thisindicates a data parity error. The remote channeladapter or the channel might be faulty.

User response: Ensure that all cables are securely

plugged. Restart the remote channel adapter andactivate the remote interface. If the problem persists,examine the subchannel trace for further diagnosticinformation. For information about the sense code see/Documentation/s390/cds.txt in the Linux source tree.Search for 'SNS0' to locate the information.

Severity: Warning

claw.f10136 <bus ID of the CLAW device>: Activating<network interface name> failed because ofan incorrect link ID=<link ID returnedfrom the remote CLAW device>

Explanation: The remote Common Link Access toWorkstation (CLAW) device accepted a connectionrequest but returned an incorrect link ID. The CLAWdevice driver only supports a single connection at atime (link ID=1) for each network interface.

User response: Restart the remote CLAW device andtry again to activate the network interface.

Severity: Warning

claw.f26e3d <bus ID of the CLAW device>: Thecommon device layer returned errorcode <errno>

Explanation: During an I/O operation, the CommonLink Access to Workstation (CLAW) device driverreceived an errno from the common I/O layer. Thisindicates a problem with the remote channel adapter.

User response: See the errno man page to find outwhat the error code means. Check for related messages.Restart the remote channel adapter. If the problempersists, examine the subchannel trace for furtherdiagnostic information.

Severity: Error

claw.ce65ab • claw.f26e3d


Chapter 9. cpcmd

Messages with a prefix cpcmd are issued by thecpcmd kernel function.

cpcmd.5984fe The cpcmd kernel function failed toallocate a response buffer

Explanation: IPL code, console detection, and devicedrivers like vmcp or vmlogrdr use the cpcmd kernelfunction to send commands to the z/VM controlprogram (CP). If a program that uses the cpcmdfunction does not allocate a contiguous response bufferbelow 2 GB guest real storage, cpcmd creates a bouncebuffer to be used as the response buffer. Because of lowmemory or memory fragmentation, cpcmd could notcreate the bounce buffer.

User response: Look for related page allocation failuremessages and at the stack trace to find out whichprogram or operation failed. Free some memory andretry the failed operation. Consider allocating morememory to your z/VM guest virtual machine.

Severity: Warning



Chapter 10. cpu

Messages with a prefix cpu are issued by theSystem z specific CPU management functions.

cpu.33a262 <number of configured CPUs> configuredCPUs, <number of standby CPUs> standbyCPUs

Explanation: The kernel detected the given number ofconfigured and standby CPUs.



cpu.3748dd The CPU configuration topology of themachine is:

Explanation: The first six values of the topologyinformation represent fields Mag6 to Mag1 ofsystem-information block (SYSIB) 15.1.2. These fieldsspecify the maximum numbers of topology-list entries(TLE) at successive topology nesting levels. The lastvalue represents the MNest value of SYSIB 15.1.2 whichspecifies the maximum possible nesting that can beconfigured through dynamic changes. For details seethe SYSIB 15.1.2 information in the "Principles ofOperation."



cpu.e2917c CPU <CPU number> exceeds themaximum <maximum CPU number> andis excluded from the dump

Explanation: The Linux kernel is used as a systemdumper but it runs on more CPUs than it has beencompiled for with the CONFIG_NR_CPUS kernelconfiguration option. The system dump will be createdbut information on one or more CPUs will be missing.

User response: Update the system dump kernel to anewer version that supports more CPUs or reduce thenumber of installed CPUs and reproduce the problemthat should be analyzed. If you send the system dumpthat prompted this message to a support organization,be sure to communicate that the dump does notinclude all CPU information.

Severity: Warning



Chapter 11. cpum_cf

Messages with a prefix cpum_cf are issued bykernel functions that support the z/ArchitectureCPU-measurement counter facility.

cpum_cf.094d6c Registering the cpum_cf PMU failedwith rc=<error code>

Explanation: The device driver could not register thePerformance Measurement Unit (PMU) for theCPU-measurement counter facility. A possible cause ofthis problem is memory constraints.

User response: If the error code is -12 (ENOMEM),consider assigning more memory to your Linuxinstance.

Severity: Error

cpum_cf.1606b2 Enabling the performance measuringunit failed with rc=<error condition>

Explanation: The device driver failed to enable CPUcounter sets with the load counter controls (lcctl)instruction. See the section about lcctl in "TheLoad-Program-Parameter and the CPU-MeasurementFacilities", SA23-2260, for an explanation of the errorconditions.

User response: Stop the performance measurementprograms and try again.

Severity: Error

cpum_cf.74a342 Registering for CPU-measurementalerts failed with rc=<error code>

Explanation: The device driver could not register toreceive CPU-measurement alerts. Alerts make youaware of measurement errors. A possible cause of thisproblem is memory constraints.

User response: If the error code is -12 (ENOMEM),consider assigning more memory to your Linuxinstance.

Severity: Error

cpum_cf.a9d681 CPU[<cpu number>] Counter datawas lost

Explanation: CPU counter data was lost because ofmachine internal high-priority activities.


Severity: Error

cpum_cf.db48c1 Disabling the performancemeasuring unit failed with rc=<errorcondition>

Explanation: The device driver failed to disable CPUcounter sets with the load counter controls (lcctl)instruction. See the section about lcctl in "TheLoad-Program-Parameter and the CPU-MeasurementFacilities", SA23-2260, for an explanation of the errorconditions.

User response: Stop the performance measurementprograms and try again.

Severity: Error



Chapter 12. ctcm

Messages with a prefix ctcm are issued by theChannel-to-Channel (CTC) device driver. CTCconnections are high-speed point-to-pointconnections between two operating systeminstances on System z.

ctcm.06c639 <bus ID of the CTCM device>: The adapterreceived a non-specific IRQ

Explanation: The adapter hardware used by theCTCM device received an IRQ that cannot be mappedto a particular device. This is a hardware problem.

User response: Check the status of the CTCM device,for example, with ifconfig. Check if the connection tothe remote device still works. If the CTCM device isnot operational, set it offline and back online. If thisdoes not resolve the problem, perform a manualrecovery. See "Device Drivers, Features, andCommands" for details about how to recover a CTCMdevice. If this problem persists, gather Linux debugdata, collect the hardware logs, and report the problemto your support organization.

Severity: Warning

ctcm.0e17de <bus ID of the CTCM device>: An erroroccurred on the adapter hardware

Explanation: The CTCM device uses an adapter tophysically connect to its communication peer. Anoperation on this adapter returned an error.

User response: Check the status of the CTCM device,for example, with ifconfig. If the device is notoperational, perform a manual recovery. See "DeviceDrivers, Features, and Commands" for details abouthow to recover a CTCM device.

Severity: Error

ctcm.3c5812 <bus ID of the CTCM device>:Initialization failed with RX/TX inithandshake error <error information>

Explanation: A problem occurred during theinitialization of the connection. If the connection can beestablished after an automatic recovery, a successmessage is issued.

User response: If the problem is not resolved by theautomatic recovery process, check the local and remotedevice. If this problem persists, gather Linux debugdata and report the problem to your supportorganization.

Severity: Warning

ctcm.4b5292 <bus ID of the CTCM device>: A checkoccurred on the subchannel

Explanation: A check condition has been detected onthe subchannel.

User response: Check if the connection to the remotedevice still works. If the CTCM device is notoperational, set it offline and back online. If this doesnot resolve the problem, perform a manual recovery.See "Device Drivers, Features, and Commands" fordetails about how to recover a CTCM device. If thisproblem persists, gather Linux debug data and reportthe problem to your support organization.

Severity: Warning

ctcm.58aa19 <channel ID>: The remote operatingsystem is not available

Explanation: The operating system instance with thecommunication peer has disconnected. Possible reasonsare that the operating system instance has beenrebooted or shut down.

User response: Ensure that the peer operating systeminstance is running and that the peer interface isoperational.

Severity: Notice

ctcm.8079b5 <bus ID of the CTCM device>: An adapterhardware operation timed out

Explanation: The CTCM device uses an adapter tophysically connect to its communication peer. Anoperation on this adapter timed out.


Severity: Error

ctcm.95ba79 <bus ID of the CTCM device>: AnI/O-error occurred on the CTCM device

Explanation: An I/O error was detected on one of thesubchannels of the CTCM device. Depending on theerror, the CTCM device driver might attempt anautomatic recovery.



Severity: Error

ctcm.ad45a0 <channel ID>: The communication peeris busy

Explanation: A busy target device was reported. Thismight be a temporary problem.

User response: If this problem persists or is reportedfrequently ensure that the target device is workingproperly.


ctcm.afe161 <channel ID>: The communication peerhas disconnected

Explanation: The remote device has disconnected.Possible reasons are that the remote interface has beenclosed or that the operating system instance with thecommunication peer has been rebooted or shut down.

User response: Check the status of the peer device.Ensure that the peer operating system instance isrunning and that the peer interface is operational.

Severity: Notice

ctcm.c97a8e An I/O operation resulted in error<channel ID>

Explanation: A hardware operation ended with anerror.

User response: Check the status of the CTCM device,for example, with ifconfig. If the device is notoperational, perform a manual recovery. See "DeviceDrivers, Features, and Commands" for details abouthow to recover a CTCM device. If this problempersists, gather Linux debug data, collect the hardwarelogs, and report the problem to your supportorganization.

Severity: Error

ctcm.defd4f <bus ID of the CTCM device>: The XIDused in the MPC protocol is not valid,rc = <return code>

Explanation: The exchange identification (XID) usedby the CTCM device driver when in MPC mode is notvalid.

User response: Note the error information providedwith this message and contact your supportorganization.

Severity: Warning

ctcm.ec4b8d <bus ID of the CTCM device>: Thenetwork backlog for <calling function> isexceeded, package dropped

Explanation: There is more network traffic than can behandled by the device. The device is closed and somedata has not been transmitted. The device might berecovered automatically.

User response: Investigate and resolve the congestion.If necessary, set the device online to make itoperational.

Severity: Warning

ctcm.fde68a <channel ID>: The specified target deviceis not valid

Explanation: A target device was called with a faultydevice specification. This is an adapter hardwareproblem.

User response: Gather Linux debug data, collect thehardware logs, and contact IBM support.

Severity: Error

ctcm.ad45a0 • ctcm.fde68a


Chapter 13. dasd-eckd

Messages with a prefix dasd-eckd are issued bythe DASD device driver module that handlesDASDs with the Extended Count Key Data (ECKD) format.

dasd-eckd.00f842 <bus ID of the DASD>: An I/Ocontrol call used incorrect flags 0x<flags>

Explanation: The DASD format I/O control was usedincorrectly.

User response: Contact the owner of the formattingtool.

Severity: Warning

dasd-eckd.01a684 <bus ID of the DASD>: FORMAT 4 -No sync byte in key area

Explanation: This is an operating system independentmessage that is issued by the storage system.

User response: For more information see thedocumentation of your storage system.

Severity: Warning

dasd-eckd.01f692 <bus ID of the DASD>: FORMAT 9 -Reserved



Severity: Warning

dasd-eckd.02c01a <bus ID of the DASD>: FORMAT 7 -No response to selection after a pollinterruption



Severity: Warning

dasd-eckd.0471ed <bus ID of the DASD>: FORMAT 0 -Reserved



Severity: Warning

dasd-eckd.04ae78 <bus ID of the DASD>: FORMAT 7 -Missing end operation; device transferincomplete



Severity: Warning

dasd-eckd.05b6e3 <bus ID of the DASD>: FORMAT 8 -End operation with transfer count zero



Severity: Warning

dasd-eckd.05c8ba <bus ID of the DASD>: FORMAT 6 -Overrun on channel F



Severity: Warning

dasd-eckd.06e412 <bus ID of the DASD>: FORMAT 0 -Status Not As Required: reason <reasoncode>

Explanation: This is an operating system independentmessage that is issued by the storage system. There areseveral potential reasons for this message; byte 8contains the reason code.


Severity: Warning

dasd-eckd.07541e <bus ID of the DASD>: FORMAT 0 -CCW Count less than required

Explanation: The CCW count of a command is lessthan required. This is an operating system independentmessage that is issued by the storage system.



Severity: Warning

dasd-eckd.08b7b8 <bus ID of the DASD>: FORMAT 4- No sync byte in data area



Severity: Warning

dasd-eckd.08d1ee <bus ID of the DASD>: FORMAT 9 -Head address did not compare



Severity: Warning

dasd-eckd.094439 <bus ID of the DASD>: FORMAT 3 -Reserved



Severity: Warning

dasd-eckd.0ad5d2 <bus ID of the DASD>: FORMAT 4- No sync byte in home address area



Severity: Warning

dasd-eckd.0af728 <bus ID of the DASD>: FORMAT 6 -Overrun on channel B



Severity: Warning

dasd-eckd.0d6cb0 <bus ID of the DASD>: FORMAT F- Subsystem Processing Error

Explanation: A firmware logic error has been detected.This is an operating system independent message thatis issued by the storage system.


Severity: Warning

dasd-eckd.0e881a <bus ID of the DASD>: FORMAT 7 -Invalid tag-in for an immediatecommand sequence



Severity: Warning

dasd-eckd.0ec8bb <bus ID of the DASD>: Readingdevice feature codes failed (rc=<returncode>) for new path <path mask>

Explanation: A new path has been made available tothe a device. A command to read the device featurecodes on this device returned an error. The new pathwill not be used for I/O.

User response: Set the new path offline and onlineagain to repeat the path verification. Alternatively, setthe device offline and online again to verify allavailable paths for this device. If this problem persists,gather Linux debug data and report the problem toyour support organization.

Severity: Warning

dasd-eckd.126bfe <bus ID of the DASD>: ERP chain atBEGINNING of ERP-ACTION

Explanation: This message provides debuginformation for the enhanced error recovery procedure(ERP).

User response: If you do not need this information,you can suppress this message by switching off ERPlogging, for example, by writing '1' to the 'erplog' sysfsattribute of the DASD.

Severity: Error

dasd-eckd.1577ff <bus ID of the DASD>: FORMAT F -Caching terminated

Explanation: The storage system was unable to initiatecaching or had to suspend caching for a 3990 controlunit. If this problem is caused by a failure condition, anadditional message will provide more informationabout the failure. This is an operating systemindependent message that is issued by the storagesystem.

User response: Check for additional messages thatpoint out possible failures. For more information seethe documentation of your storage system.

Severity: Warning

dasd-eckd.08b7b8 • dasd-eckd.1577ff


dasd-eckd.1c04cd <bus ID of the DASD>: FORMAT 4 -Key area error; offset active



Severity: Warning

dasd-eckd.1cfbb8 <bus ID of the DASD>: FORMAT 1 -Offset active cannot be reset



Severity: Warning

dasd-eckd.1dd1a2 <bus ID of the DASD>: FORMAT 2- Reserved



Severity: Warning

dasd-eckd.1fd065 <bus ID of the DASD>: Detectingthe maximum supported data size forzHPF requests failed

Explanation: High Performance FICON® (zHPF)requests are limited to a hardware-dependentmaximum data size. The DASD device driver failed todetect this size and zHPF is not available for thisdevice.

User response: Set the device offline and online again.If this problem persists, gather Linux debug data andreport the problem to your support organization.

Severity: Warning

dasd-eckd.20b59b <bus ID of the DASD>: FORMAT 0- Invalid Command Sequence

Explanation: An incorrect sequence of commands hasoccurred. This is an operating system independentmessage that is issued by the storage system.


Severity: Warning

dasd-eckd.22e514 <bus ID of the DASD>: FORMAT 4 -No syn byte in count address area;offset active



Severity: Warning

dasd-eckd.2567a1 <bus ID of the DASD>: FORMAT 0 -Invalid Command

Explanation: A command was issued that is not in the2107/1750 command set. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.27f2cd <bus ID of the DASD>: The DASDis not operating in multipath mode

Explanation: The DASD channel path group could notbe configured to use multipath mode. This mightnegatively affect I/O performance on this DASD.

User response: Make sure that the DASD is workingcorrectly, then try again to set it online. If initializationstill fails, reboot.


dasd-eckd.292792 <bus ID of the DASD>: FORMAT D- Reserved



Severity: Warning

dasd-eckd.29f189 <bus ID of the DASD>: 0x<command>is not a known command

Explanation: This problem is likely to be caused by aprogramming error.

User response: Contact your support organization.

Severity: Error

dasd-eckd.2aa01a <bus ID of the DASD>: New DASD<device type>/<device model> (CU <controlunit type>/<control unit model>) with<number of cylinders> cylinders, <tracksper cylinder> heads, <sectors per track>sectors<access mode>

dasd-eckd.1c04cd • dasd-eckd.2aa01a

Chapter 13. dasd-eckd 35

Explanation: A DASD with the shown characteristicshas been set online. If the DASD is configured asread-only to the real or virtual hardware, the messageincludes an indication of this hardware access mode.The hardware access mode is independent from the'readonly' attribute of the device in sysfs.



dasd-eckd.2dd933 <bus ID of the DASD>: FORMAT 1- Device check-2 error or Set Sector isnot complete



Severity: Warning

dasd-eckd.2ebc2e <bus ID of the DASD>: FORMAT 5 -Data Check in the count area; offsetactive



Severity: Warning

dasd-eckd.308a03 <bus ID of the DASD>: FORMAT 5 -Reserved



Severity: Warning

dasd-eckd.331a2a <bus ID of the DASD>: FORMAT 1 -Reserved



Severity: Warning

dasd-eckd.36ac9b <bus ID of the DASD>: Start track<track number> used in formattingexceeds end track

Explanation: The DASD format I/O control was usedincorrectly by a formatting tool.


Severity: Warning

dasd-eckd.39c600 <bus ID of the DASD>: FORMAT 8 -Unexpected end operation response code



Severity: Warning

dasd-eckd.3dd39b <bus ID of the DASD>: FORMAT 7- RCC 1 and RCC 2 sequences notsuccessful



Severity: Warning

dasd-eckd.3ea257 <bus ID of the DASD>: FORMAT 1 -Device not ready



Severity: Warning

dasd-eckd.400105 <bus ID of the DASD>: FORMAT 6 -Overrun on channel C



Severity: Warning

dasd-eckd.412b53 <bus ID of the DASD>: DASD with<block size> KB/block, <DASD size> KBtotal size, <track size> KB/track, <disclayout>

Explanation: A DASD with the shown characteristicshas been set online.



dasd-eckd.4170f2 <bus ID of the DASD>: The UID ofthe DASD has changed

Explanation: The Unique Identifier (UID) of a DASDthat is currently in use has changed. This indicates thatthe physical disk has been replaced.

dasd-eckd.2dd933 • dasd-eckd.4170f2


User response: None if the replacement wasintentional. If the disk change is not expected, stopusing the disk to prevent possible data loss.

Severity: Error

dasd-eckd.423705 <bus ID of the DASD>: FORMAT 0 -Channel Returned with Incorrect retryCCW

Explanation: A command portion of the CCWreturned after a command retry sequence does notmatch the command for which retry was signaled. Thisis an operating system independent message that isissued by the storage system.


Severity: Warning

dasd-eckd.423d5b <bus ID of the DASD>: FORMAT 7- Missing end operation; device transfercomplete



Severity: Warning

dasd-eckd.42a207 <bus ID of the DASD>: Thespecified record was not found

Explanation: The record to be accessed does not exist.The DASD might be unformatted or defect.

User response: Try to format the DASD or replace it.ATTENTION: Formatting irreversibly destroys all dataon the DASD.

Severity: Error

dasd-eckd.43830c <bus ID of the DASD>: FORMAT F -Caching reinitiated

Explanation: Caching has been automaticallyreinitiated following an error. This is an operatingsystem independent message that is issued by thestorage system.


Severity: Warning

dasd-eckd.459c47 <bus ID of the DASD>: log SIM -SRC: <sense byte><sense byte><sensebyte><sense byte>

Explanation: This System Information Message (SIM)is generated by the storage system. The SystemReference Code (SRC) defines the error in detail.

User response: Look up the SRC in the storage serverdocumentation.

Severity: Warning

dasd-eckd.45f2d1 <bus ID of the DASD>: The disklayout of the DASD is not supported

Explanation: The DASD device driver only supportsthe following disk layouts: CDL, LDL, FBA, CMS, andCMS RESERVED.


Severity: Warning

dasd-eckd.46d841 <bus ID of the DASD>: FORMAT 5 -Data Check in the key area



Severity: Warning

dasd-eckd.47fcac <bus ID of the DASD>: ERP <pointerto ERP> (<ERP status>) refers to <cqr>



Severity: Error

dasd-eckd.481dec <bus ID of the DASD>: FORMAT F -Cache fast write access not authorized

Explanation: A request for Cache Fast Write Dataaccess cannot be satisfied because of missing accessauthorization for the storage system. This is anoperating system independent message that is issuedby the storage system.


Severity: Warning

dasd-eckd.487b65 <bus ID of the DASD>: SIM - SRC:<sense byte><sense byte><sense byte><sensebyte>

Explanation: This error message is a SystemInformation Message (SIM) generated by the storagesystem. The System Reference Code (SRC) defines theerror in detail.

dasd-eckd.423705 • dasd-eckd.487b65


User response: Look up the SRC in the storage serverdocumentation.

Severity: Error

dasd-eckd.4a5b55 <bus ID of the DASD>: FORMAT 7 -DASD controller not available ondisconnected command chain



Severity: Warning

dasd-eckd.4aeb6d <bus ID of the DASD>: FORMAT 8- DASD controller failed to set or resetthe long busy latch



Severity: Warning

dasd-eckd.4cdcde <bus ID of the DASD>: ERP chain atEND of ERP-ACTION



Severity: Error

dasd-eckd.5005eb <bus ID of the DASD>: FORMAT 8 -Reserved



Severity: Warning

dasd-eckd.538dcc <bus ID of the DASD>: FORMAT 4 -Reserved



Severity: Warning

dasd-eckd.55aa2f <bus ID of the DASD>: FORMAT 1 -Missing device address bit



Severity: Warning

dasd-eckd.5806f8 <bus ID of the DASD>: FORMAT 8 -DPS checks after a system reset orselective reset



Severity: Warning

dasd-eckd.58865b <bus ID of the DASD>: FORMAT 1 -Cylinder address did not compare



Severity: Warning

dasd-eckd.58c328 <bus ID of the DASD>: FORMAT 0 -Invalid Defective/Alternate TrackPointer

Explanation: A defective track has been accessed. Thesubsystem generates an invalid Defective/AlternateTrack Pointer as a part of RAID Recovery. This is anoperating system independent message that is issuedby the storage system.


Severity: Warning

dasd-eckd.5cf324 <bus ID of the DASD>: FORMAT F -Volume is suspended duplex

Explanation: The duplex pair volume has entered thesuspended duplex state because of a failure. This is anoperating system independent message that is issuedby the storage system.


Severity: Warning

dasd-eckd.4a5b55 • dasd-eckd.5cf324


dasd-eckd.5efa1b <bus ID of the DASD>: FORMAT 4 -No sync byte in count address area



Severity: Warning

dasd-eckd.637cf1 <bus ID of the DASD>: Readingdevice feature codes failed withrc=<return code>

Explanation: The device feature codes state whichadvanced features are supported by a device. Examplesfor advanced features are PAV or high performanceFICON. Some early devices do not provide featurecodes and no advanced features are available on thesedevices.

User response: None, if the DASD does not providefeature codes. If the DASD provides feature codes,make sure that it is working correctly, then set it offlineand back online.

Severity: Warning

dasd-eckd.648dca <bus ID of the DASD>: FORMAT 6 -Overrun on channel D



Severity: Warning

dasd-eckd.65917e <bus ID of the DASD>: Datarecovered during retry with PCI fetchmode active

Explanation: A data error has been recovered on thestorages system but the Linux file system cannot beinformed about the data mismatch. To prevent Linuxfrom running with incorrect data, the DASD devicedriver will trigger a kernel panic.

User response: Reset your real or virtual hardwareand reboot Linux.

Severity: Emerg

dasd-eckd.65b8de <bus ID of the DASD>: FORMAT 7- Reserved



Severity: Warning

dasd-eckd.680aac <bus ID of the DASD>: Allocatingmemory for private DASD data failed

Explanation: The DASD device driver maintains datastructures for each DASD it manages. There is notenough memory to allocate these data structures forone or more DASD.

User response: Free some memory and try theoperation again.

Severity: Warning

dasd-eckd.6e3fdc <bus ID of the DASD>: FORMAT 6 -Overrun on channel G



Severity: Warning

dasd-eckd.6eae2d <bus ID of the DASD>: is offline ornot installed - INTERVENTIONREQUIRED!!

Explanation: The DASD to be accessed is not in anaccessible state. The I/O operation will wait until thedevice is operational again. This is an operating systemindependent message that is issued by the storagesystem.

User response: Make the DASD accessible again. Fordetails see the storage system documentation.

Severity: Error

dasd-eckd.7109ed <bus ID of the DASD>: FORMAT 1 -Interruption cannot be reset



Severity: Warning

dasd-eckd.72eaa3 <bus ID of the DASD>: FORMAT 6 -Overrun on channel A



Severity: Warning

dasd-eckd.5efa1b • dasd-eckd.72eaa3


dasd-eckd.74be4d <bus ID of the DASD>: FORMAT 8- DPS cannot be filled



Severity: Warning

dasd-eckd.75ca81 <bus ID of the DASD>: FORMAT 0 -Device Error Source

Explanation: The device has completed soft errorlogging. This is an operating system independentmessage that is issued by the storage system.


Severity: Warning

dasd-eckd.792e2f <bus ID of the DASD>: FORMAT 8 -End operation with transfer count notzero



Severity: Warning

dasd-eckd.7b19bf <bus ID of the DASD>: FORMAT 3 -Allegiance terminated

Explanation: Allegiance terminated because of a ResetAllegiance or an Unconditional Reserve command onanother channel. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.7bb394 <bus ID of the DASD>: FORMAT 7- Invalid DCC selection response ortimeout



Severity: Warning

dasd-eckd.7c1681 <bus ID of the DASD>: FORMAT 0 -Storage Path Restart

Explanation: An operation for an active channelprogram was queued in a Storage Control when awarm start was received by the path. This is anoperating system independent message that is issuedby the storage system.


Severity: Warning

dasd-eckd.7eabfd <bus ID of the DASD>: FORMAT 0 -Diagnostic of Special CommandViolates File Mask

Explanation: A command is not allowed under theAccess Authorization specified by the File Mask. This isan operating system independent message that isissued by the storage system.


Severity: Warning

dasd-eckd.7f0765 <bus ID of the DASD>: Track 0 hasno records following the VTOC

Explanation: Linux has identified a volume table ofcontents (VTOC) on the DASD but cannot read anydata records following the VTOC. A possible cause ofthis problem is that the DASD has been used withanother System z operating system.

User response: Format the DASD for usage withLinux, for example, with dasdfmt. ATTENTION:Formatting irreversibly destroys all data on the DASD.

Severity: Warning

dasd-eckd.81757d <bus ID of the DASD>: FORMAT 1 -Device Status 1 not as expected



Severity: Warning

dasd-eckd.840169 <bus ID of the DASD>: FORMAT 6 -Overrun on channel E



Severity: Warning

dasd-eckd.74be4d • dasd-eckd.840169


dasd-eckd.869e5e <bus ID of the DASD>: FORMAT 6 -Overrun on channel H



Severity: Warning

dasd-eckd.87ddea <bus ID of the DASD>: A channelpath group could not be established

Explanation: Initialization of a DASD did notcomplete because a channel path group could not beestablished.

User response: Make sure that the DASD is workingcorrectly, then try again to set it online. If initializationstill fails, reboot.

Severity: Warning

dasd-eckd.894a4b <bus ID of the DASD>: FORMAT 7 -3990 microcode time out when stoppingselection



Severity: Warning

dasd-eckd.8b4bdf <bus ID of the DASD>: FORMAT 2- Microcode detected error <error code>



Severity: Warning

dasd-eckd.910d5f <bus ID of the DASD>: FORMAT 0 -Data Pinned for Device

Explanation: Modified data in cache or in persistentstorage exists for the DASD. The data cannot bedestaged to the device. This track is the first trackpinned for this device. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.948ccf <bus ID of the DASD>: FORMAT 4 -Key area error



Severity: Warning

dasd-eckd.96f088 <bus ID of the DASD>: FORMAT 7 -RCC 1 sequence not successful



Severity: Warning

dasd-eckd.9957b7 <bus ID of the DASD>: FORMAT 1 -Head address does not compare



Severity: Warning

dasd-eckd.9a48d5 <bus ID of the DASD>: FORMAT 4 -No syn byte in data area; offset active



Severity: Warning

dasd-eckd.9bb776 <bus ID of the DASD>: FORMAT 4- Data area error; offset active



Severity: Warning

dasd-eckd.9e183a <bus ID of the DASD>: FORMAT 4 -Count area error



Severity: Warning

dasd-eckd.869e5e • dasd-eckd.9e183a


dasd-eckd.9f31f9 <bus ID of the DASD>: FORMAT 7 -RCC initiated by a connection checkalert



Severity: Warning

dasd-eckd.a0ce75 <bus ID of the DASD>: FORMAT 4 -No sync byte in key area; offset active



Severity: Warning

dasd-eckd.a28dc6 <bus ID of the DASD>: The DASDcache mode was set to <operation mode>(<number of cylinders> cylinder prestage)

Explanation: The DASD cache mode has beenchanged. See the storage system documentation forinformation about the different cache operation modes.



dasd-eckd.a3c651 <bus ID of the DASD>: FORMAT 9 -Device check-2 error



Severity: Warning

dasd-eckd.a4325c <bus ID of the DASD>: FORMAT 0 -Reset Notification

Explanation: A system reset or its equivalent wasreceived on an interface. The Unit Check that generatesthis sense is posted to the next channel initiatedselection following the resetting event. This is anoperating system independent message that is issuedby the storage system.


Severity: Warning

dasd-eckd.a56dba <bus ID of the DASD>: The DASDcannot be formatted with block size<block size>

Explanation: The block size specified for a formatinstruction is not valid. The block size must be between512 and 4096 byte and must be a power of 2.

User response: Call the format command with asupported block size.

Severity: Warning

dasd-eckd.a77e4f <bus ID of the DASD>: FORMAT 1 -Track physical address did not compare



Severity: Warning

dasd-eckd.a9cbd8 <bus ID of the DASD>: FORMAT 1 -Drive motor switch is off



Severity: Warning

dasd-eckd.aac43a <bus ID of the DASD>: FORMAT 0 -Device Fenced - device = <sense data byte4>

Explanation: The device shown in sense byte 4 hasbeen fenced. This is an operating system independentmessage that is issued by the storage system.


Severity: Warning

dasd-eckd.ac6397 <bus ID of the DASD>: FORMAT 1 -Index missing



Severity: Warning

dasd-eckd.acd228 <bus ID of the DASD>: FORMAT 7 -extra RCC required


User response: For more information see the

dasd-eckd.9f31f9 • dasd-eckd.acd228


documentation of your storage system.

Severity: Warning

dasd-eckd.adb621 <bus ID of the DASD>: ERP failedfor the DASD

Explanation: An error recovery procedure (ERP) wasperformed for the DASD but failed.

User response: Check the message log for previousrelated error messages.

Severity: Error

dasd-eckd.b14557 <bus ID of the DASD>: FORMAT 4 -Data area error



Severity: Warning

dasd-eckd.b22b7e <bus ID of the DASD>: An I/Orequest was rejected because writing isinhibited

Explanation: An I/O request was returned with anerror indication of 'command reject' and 'writeinhibited'. The most likely reason for this error is afailed write request to a device that was attached asread-only in z/VM.

User response: Set the device offline, ensure that thedevice is configured correctly in z/VM, then set thedevice online again.

Severity: Error

dasd-eckd.b281ed <bus ID of the DASD>: The DASDis not formatted

Explanation: A DASD has been set online but it hasnot been formatted yet. You must format the DASDbefore you can use it.

User response: Format the DASD, for example, withdasdfmt.

Severity: Warning

dasd-eckd.b3193d <bus ID of the DASD>: An erroroccurred in the DASD device driver,reason=<reason code>

Explanation: This problem indicates a program errorin the DASD device driver.

User response: Note the reason code and contact yoursupport organization.

Severity: Error

dasd-eckd.b3f650 <bus ID of the DASD>: The newlyadded channel path <logical path mask>will not be used because it leads to adifferent device <UID>

Explanation: The newly added channel path has adifferent UID than the DASD device. This indicates anincorrect cabling. This path is not going to be used.

User response: Check the cabling of the DASD device.Disconnect and reconnect the cable.

Severity: Error

dasd-eckd.b81b6c <bus ID of the DASD>: The DASDcannot be reached on any path(lpum=<last path used mask>/opm=<onlinepath mask>)

Explanation: After a path to the DASD failed, theerror recovery procedure of the DASD device drivertried but failed to reconnect the DASD through analternative path.

User response: Ensure that the cabling between thestorage server and the mainframe system is securely inplace. Check the file systems on the DASD when it isaccessible again.

Severity: Error

dasd-eckd.b98207 <bus ID of the DASD>: FORMAT 7 -Invalid tag-in for an extended commandsequence



Severity: Warning

dasd-eckd.bba496 <bus ID of the DASD>: FORMAT 9- Track physical address did notcompare while oriented



Severity: Warning

dasd-eckd.bbe891 <bus ID of the DASD>: FORMAT F- Subsystem status cannot bedetermined

Explanation: The status of a DASD Fast Write orPPRC volume cannot be determined. This is anoperating system independent message that is issuedby the storage system.

User response: For more information see the

dasd-eckd.adb621 • dasd-eckd.bbe891


documentation of your storage system.

Severity: Warning

dasd-eckd.be85b8 <bus ID of the DASD>: FORMAT F- Cache or nonvolatile storageequipment failure

Explanation: An equipment failure has occurred in thecache storage or nonvolatile storage of the storagesystem. This is an operating system independentmessage that is issued by the storage system.


Severity: Warning

dasd-eckd.bfc2cb <bus ID of the DASD>: FORMAT F -Nonvolatile storage terminated

Explanation: The storage director has stopped usingnonvolatile storage or cannot initiate nonvolatilestorage. If this problem is caused by a failure, anadditional message will provide more informationabout the failure. This is an operating systemindependent message that is issued by the storagesystem.

User response: Check for additional messages thatpoint out possible failures. For more information seethe documentation of your storage system.

Severity: Warning

dasd-eckd.c28ccc <bus ID of the DASD>: FORMAT 0 -DPS Installation Check

Explanation: This operating system independentmessage is issued by the storage system for one of thefollowing reasons: - A 3380 Model D or E DASD doesnot have the Dynamic Path Selection (DPS) feature inthe DASD A-unit. - The device type of an attachedDASD is not supported by the firmware. - A type 3390DASD is attached to a 3 MB channel.


Severity: Warning

dasd-eckd.c3ebff <bus ID of the DASD>: FORMAT 5 -Data Check in the data area



Severity: Warning

dasd-eckd.c55c2f <bus ID of the DASD>: Unable toallocate DCTL-CQR

Explanation: This is an internal error.


Severity: Error

dasd-eckd.c67479 <bus ID of the DASD>: FORMAT 1 -Seek incomplete



Severity: Warning

dasd-eckd.c87cc2 <bus ID of the DASD>: FORMAT 5 -Data Check in the key area; offset active



Severity: Warning

dasd-eckd.c9cc06 <bus ID of the DASD>: FORMAT 1 -Device status 1 not valid



Severity: Warning

dasd-eckd.c9f7f5 <bus ID of the DASD>: FORMAT 7 -Invalid tag-in during selection sequence



Severity: Warning

dasd-eckd.ca8dfc <bus ID of the DASD>: FORMAT 7 -Permanent path error (DASD controllernot available)



Severity: Warning

dasd-eckd.be85b8 • dasd-eckd.ca8dfc


dasd-eckd.cf8d3d <bus ID of the DASD>: FORMAT 5 -Data Check in the count area



Severity: Warning

dasd-eckd.d1a88a <bus ID of the DASD>: Detectingthe DASD disk layout failed because ofan I/O error

Explanation: The disk layout of the DASD could notbe detected because of an unexpected I/O error. TheDASD device driver treats the device like anunformatted DASD, and partitions on the device arenot accessible.

User response: If the DASD is formatted, make surethat the DASD is working correctly, then set it offlineand back online. If the DASD is unformatted, formatthe DASD, for example, with dasdfmt. ATTENTION:Formatting irreversibly destroys all data on the DASD.

Severity: Error

dasd-eckd.d2af02 <bus ID of the DASD>: FORMAT 0 -Channel requested ... <reason code>

Explanation: This is an operating system independentmessage that is issued by the storage system. Thepossible reason codes indicate the following problems:00 No Message. 01 The channel has requested unitcheck sense data. 02 The channel has requested retryand retry is exhausted. 03 A SA Check-2 error hasoccurred. This sense is presented with EquipmentCheck. 04 The channel has requested retry and retry isnot possible.


Severity: Warning

dasd-eckd.d2bf98 <bus ID of the DASD>: ERP <ERPpointer> has run out of retries and failed

Explanation: The error recovery procedure (ERP) triedto recover an error but the number of retries for theI/O was exceeded before the error could be resolved.

User response: Check for related previous errormessages.

Severity: Error

dasd-eckd.d35646 <bus ID of the DASD>: FORMAT 8 -No interruption from device during acommand chain



Severity: Warning

dasd-eckd.d4a740 <bus ID of the DASD>: Writeinhibited path encountered

Explanation: This is an informational message.



dasd-eckd.d4d6d2 <bus ID of the DASD>: FORMAT F- DASD Fast Write inhibited

Explanation: DASD Fast Write is not allowed becauseof a nonvolatile storage battery check condition. This isan operating system independent message that isissued by the storage system.


Severity: Warning

dasd-eckd.d608df <bus ID of the DASD>: Start tracknumber <track number> used informatting is too big



Severity: Warning

dasd-eckd.d66c5d <bus ID of the DASD>: FORMAT 4 -No sync byte in home address area;offset active



Severity: Warning

dasd-eckd.d74b52 <bus ID of the DASD>: FORMAT F- Track format incorrect

Explanation: A track format error occurred while datawas being written to the DASD or while a duplex pairwas being established. This is an operating system

dasd-eckd.cf8d3d • dasd-eckd.d74b52


independent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.d7a598 <bus ID of the DASD>: FORMAT 5 -Data Check in the home address area



Severity: Warning

dasd-eckd.d82ca0 <bus ID of the DASD>: FORMAT 2 -Support facility errors



Severity: Warning

dasd-eckd.dc4849 <bus ID of the DASD>: Themaximum data size for zHPF requests<size in bytes> on a new path <path mask>is below the active maximum <size inbytes>

Explanation: High Performance FICON (zHPF)requests are limited to a hardware-dependentmaximum data size. The maximum of the new path isbelow the previously established common maximumfor the existing paths for this device. This could causerequests on the new path to fail. The new path will notbe used for I/O.

User response: Set the device offline and online againto establish a new common maximum data size for thedevice.

Severity: Warning

dasd-eckd.dcc26f <bus ID of the DASD>: FORMAT 0 -Invalid Parameter

Explanation: A data argument of a command is notvalid. This is an operating system independent messagethat is issued by the storage system.


Severity: Warning

dasd-eckd.e0558d <bus ID of the DASD>: FORMAT 9 -Cylinder address did not compare



Severity: Warning

dasd-eckd.e0679b <bus ID of the DASD>: FORMAT 8 -Short busy time-out during deviceselection



Severity: Warning

dasd-eckd.e181a1 <bus ID of the DASD>: FORMAT 4 -Home address area error



Severity: Warning

dasd-eckd.e698e6 <bus ID of the DASD>: FORMAT 8 -Error correction code hardware fault



Severity: Warning

dasd-eckd.e951ba <bus ID of the DASD>: FORMAT 4 -Count area error; offset active



Severity: Warning

dasd-eckd.ec6f52 <bus ID of the DASD>: Stop tracknumber <track number> used informatting is too big



dasd-eckd.d7a598 • dasd-eckd.ec6f52


Severity: Warning

dasd-eckd.ed1a53 <bus ID of the DASD>: FORMAT 5 -Data Check in the home address area;offset active



Severity: Warning

dasd-eckd.f02333 <bus ID of the DASD>: The cylinderdata for accessing the DASD isinconsistent

Explanation: An error occurred in the storage systemhardware.


Severity: Error

dasd-eckd.f0ba2c <bus ID of the DASD>: FORMAT 4 -Home address area error; offset active



Severity: Warning

dasd-eckd.f4346b <bus ID of the DASD>: The devicereservation was lost

Explanation: This Linux instance has lost itsreservation of the device to another operating systeminstance. Depending on the reservation policy for thedevice, I/O might be blocked until the other operatingsystem instance surrenders the reservation or all I/Orequests might fail until the device is reset.

User response: None, if this situation is handled bysystem automation software. If this situation is nothandled by automation, check thelast_known_reservation_state attribute of the device insysfs. If the value is 'lost', verify that the device is nolonger reserved by another operating system instance,then set the device offline and online again. For anyother value of the last_known_reservation_state noaction is required. I/O will resume when the devicereservation is surrendered by the other operatingsystem instance.

Severity: Error

dasd-eckd.f453eb <bus ID of the DASD>: FORMAT 1 -Device did not respond to selection



Severity: Warning

dasd-eckd.f4a01e <bus ID of the DASD>: FORMAT 0 -Command Invalid on SecondaryAddress

Explanation: A command or order not allowed on aPPRC secondary device has been received by thesecondary device. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.f4ccb9 <bus ID of the alias>: An Aliasdevice was reassigned to a new basedevice with UID: <UID of new basedevice>

Explanation: The alias device with the indicated busID has been reassigned. The UID of the new basedevice is shown in the message.



dasd-eckd.f546ed <bus ID of the DASD>: Detectingthe maximum data size for zHPFrequests failed (rc=<return code>) for anew path <path mask>

Explanation: High Performance FICON (zHPF)requests are limited to a hardware-dependentmaximum data size. A command to detect this size fora new path returned an error. The new path will not beused for I/O.

User response: Set the new path offline and onlineagain to repeat the path verification. Alternatively, setthe device offline and online again to verify allavailable paths for this device. If this problem persists,gather Linux debug data and report the problem toyour support organization.

Severity: Warning

dasd-eckd.ed1a53 • dasd-eckd.f546ed


dasd-eckd.f58554 <bus ID of the DASD>: FORMAT 5 -Data Check in the data area; offsetactive



Severity: Warning

dasd-eckd.f59fd6 <bus ID of the DASD>: FORMAT 6 -Reserved



Severity: Warning

dasd-eckd.f6f541 <bus ID of the DASD>: FORMAT F -Caching status reset to default

Explanation: The storage director has assigned twonew subsystem status devices and resets the status toits default value. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.f716c1 <bus ID of the DASD>: The storageserver does not support raw-track access

Explanation: The DASD cannot be accessed inraw-track access mode because the storage server doesnot have all required features for this access mode. Inraw-track access mode, the DASD device driveraccesses complete ECKD tracks. By default, the DASDdevice driver accesses only the data fields of ECKDdevices and omits the count and key data fields.

User response: Ensure that the raw_track_access sysfsattribute of the DASD has the value 0 to access thedevice in default ECKD mode.

Severity: Error

dasd-eckd.f99a70 <bus ID of the DASD>: FORMAT F -Operation Terminated

Explanation: The storage system ends an operationrelated to an active channel program when terminationand redrive are required and logging is not desired.This is an operating system independent message thatis issued by the storage system.


Severity: Warning

dasd-eckd.fba34e <bus ID of the DASD>: Accessingthe DASD failed because of a hardwareerror

Explanation: An error occurred in the storage systemhardware.


Severity: Error

dasd-eckd.fe3f84 <bus ID of the DASD>: Not allchannel paths lead to the same device,path <logical path mask> leads to device<UID> instead of <UID>

Explanation: Some channel paths have a different UIDthan others. This indicates an incorrect cabling. TheDASD device is not enabled.

User response: Check cabling of the DASD device andretry to enable the device.

Severity: Error

dasd-eckd.ffd164 <bus ID of the DASD>: FORMAT 2 -3990 check-2 error



Severity: Warning

dasd-eckd.f58554 • dasd-eckd.ffd164


Chapter 14. dasd-fba

Messages with a prefix dasd-fba are issued by theDASD device driver module that handles DASDswith the Fixed Block Access (FBA) format.

dasd-fba.680aac <bus ID of the DASD>: Allocatingmemory for private DASD data failed

Explanation: The DASD device driver maintains datastructures for each DASD it manages. There is notenough memory to allocate these data structures forone or more DASD.

User response: Free some memory and try theoperation again.

Severity: Warning

dasd-fba.f36f2f <bus ID of the DASD>: New FBADASD <device type>/<device model> (CU<control unit type>/<control unit model>)with <size> MB and <bytes per block>B/blk<access mode>

Explanation: A DASD with the shown characteristicshas been set online. If the DASD is configured asread-only to the real or virtual hardware, the messageincludes an indication of this hardware access mode.The hardware access mode is independent from the'readonly' attribute of the device in sysfs.





Chapter 15. dasd

Messages with a prefix dasd are issued by theDASD device driver.

dasd.04422e Registering the device driver with majornumber <DASD major> failed

Explanation: Major number 94 is reserved for theDASD device driver. The DASD device driver failed toregister with this major number. Another device drivermight have used major number 94.

User response: Determine which device driver usesmajor number 94 instead of the DASD device driverand unload this device driver. Then try again to loadthe DASD device driver.

Severity: Warning

dasd.0ae5e4 Discipline <discipline name> cannot beused without z/VM

Explanation: The discipline that is specified with thedasd= kernel or module parameter is only available forLinux instances that run as guest operating systems ofthe z/VM hypervisor.

User response: Remove the unsupported disciplinefrom the parameter string.


dasd.1211d0 <value> is not a supported value for/proc/dasd/statistics

Explanation: An incorrect value has been written to/proc/dasd/statistics. The supported values are: 'seton', 'set off', and 'reset'.

User response: Write a supported value to/proc/dasd/statistics.

Severity: Warning

dasd.157e58 <bus ID of the DASD>: cqr <request>timed out (<timeout value>), <number ofretries left> retries remaining

Explanation: A try of the error recovery procedure(ERP) for the channel queued request (cqr) timed outand failed to recover the error. ERP continues for theDASD.

User response: Ignore this message if it occursinfrequently and if the recovery succeeds during one ofthe retries. If this error persists, check for relatedprevious error messages and report the problem toyour support organization. The timeout can be changedby writing a new value to the sysfs 'expires' attribute of

the DASD. The value specifies the timeout in seconds.

Severity: Error

dasd.1ac0f4 <bus ID of the DASD>: Flushing theDASD request queue failed for request<pointer to request>

Explanation: As part of the unloading process, theDASD device driver flushes the request queue. Thisfailed because a previously started I/O operation couldnot be canceled.

User response: Try again to unload the DASD devicedriver or to shut down Linux.

Severity: Error

dasd.1c9171 <bus ID of the DASD>: DIAGinitialization failed with rc=<returncode>

Explanation: Initializing the DASD with the DIAGdiscipline failed. Possible reasons for this problem arethat the device has a device type other than FBA orECKD, or has a block size other than one of thesupported sizes: 512 byte, 1024 byte, 2048 byte, or 4096byte.

User response: Ensure that the device can be writtento and has a supported device type and block size. Fordetails about the return code see the section about theINITIALIZE function for DIAGNOSE Code X'250' in"z/VM CP Programming Services". If you cannotresolve the error, note the error code and contact yoursupport organization.

Severity: Warning

dasd.1e2d81 'nopav' is not supported on z/VM

Explanation: For Linux instances that run as guestoperating systems of the z/VM hypervisor ParallelAccess Volume (PAV) support is controlled by z/VMnot by Linux.

User response: Remove 'nopav' from the dasd=module or kernel parameter specification.


dasd.2529f2 <bus ID of the DASD>: Accessing theDASD failed because it is in probeonlymode

Explanation: The dasd= module or kernel parameterspecified the probeonly attribute for the DASD you aretrying to access. The DASD device driver cannot accessDASDs that are in probeonly mode.


User response: Change the dasd= parameter as toomit probeonly for the DASD and reload the DASDdevice driver. If the DASD device driver has beencompiled into the kernel, reboot Linux.


dasd.2741d8 <bus ID of the DASD>: DIAG ERP failedwith rc=<return code>

Explanation: An error in the DIAG processing couldnot be recovered by the error recovery procedure (ERP)of the DIAG discipline.

User response: Note the return code, check for relatedI/O errors, and report this problem to your supportorganization.

Severity: Warning

dasd.2f6a90 The probeonly mode has been activated

Explanation: The probeonly mode of the DASD devicedriver has been activated. In this mode the devicedriver rejects any 'open' syscalls with EPERM.



dasd.3dba87 The autodetection mode has beenactivated

Explanation: The autodetection mode of the DASDdevice driver has been activated. In this mode theDASD device driver sets all detected DASDs online.



dasd.3e7d29 <bus ID of the DASD> Setting the DASDonline with discipline <discipline> failedwith rc=<return code>

Explanation: The DASD could not be set onlinebecause of previous errors.

User response: Look for previous error messages. Ifyou cannot resolve the error, note the return code andcontact your support organization.

Severity: Warning

dasd.401b68 <bus ID of the DASD>: A channel path tothe device has become operational

Explanation: At least one channel path of this devicehas become operational again. The DASD device driverresumes I/O operations to the device and processes theI/O requests that were queued while there was nooperational channel path.



dasd.50a6e5 <bus ID of the DASD>: Formatting unit<start track> failed with rc=<return code>

Explanation: The formatting process might have beeninterrupted by a signal, for example, CTRL+C. If theprocess was not interrupted intentionally, an I/O errormight have occurred.

User response: Retry to format the device. If the errorpersists, check the log file for related error messages. Ifyou cannot resolve the error, note the return code andcontact your support organization.

Severity: Error

dasd.518c6a The dasd= parameter value <parametervalue> has an invalid ending

Explanation: The specified value for the dasd= kernelor module parameter is not correct.

User response: Check the module or the kernelparameter.

Severity: Warning

dasd.5303a1 PAV support has be deactivated

Explanation: The 'nopav' keyword has been specifiedwith the dasd= kernel or module parameter. TheParallel Access Volume (PAV) support of the DASDdevice driver has been deactivated.



dasd.5c0c98 <bus ID of the DASD>: default ERP hasrun out of retries and failed

Explanation: The error recovery procedure (ERP) triedto recover an error but the number of retries for theI/O was exceeded before the error could be resolved.


Severity: Error

dasd.68f0f6 <bus ID of the DASD>: A transport erroroccurred for cqr <pointer to request>

Explanation: A channel queued request (cqr) failedbecause the connection to the device was lost and the'failfast' flag is set for the request. This flag can resultfrom, for example: - A software layer above the DASDdevice driver; for example, in a host based mirroringsetup. - Value 1 for the 'failfast' sysfs attribute of theDASD. This setting applies to all requests on theDASD.

User response: Ensure that each channel path to thedevice has been set up correctly and that the relatedphysical cable connections are in place. If the 'failfast'attribute of the DASD is set to 1, verify that this setting

dasd.2741d8 • dasd.68f0f6


is intentional and change it to 0 if required.

Severity: Error

dasd.696eb5 <option> is not a supported deviceoption

Explanation: The dasd= parameter includes anunknown option for a DASD or a device range.Options are specified in parenthesis and immediatelyfollow a device or device range.

User response: Check the dasd= syntax and removeany unsupported options from the dasd= parameterspecification.

Severity: Warning

dasd.75373e <bus ID of the DASD>: Cancellingrequest <pointer to request> failed withrc=<return code of previous function>

Explanation: In response to a user action, the DASDdevice driver tried but failed to cancel a previouslystarted I/O operation.

User response: Try the action again.

Severity: Error

dasd.781738 High Performance FICON support hasbeen deactivated

Explanation: The 'nofcx' keyword has been specifiedwith the dasd= kernel or module parameter. The HighPerformance FICON (transport mode) support of theDASD device driver has been deactivated.



dasd.7854c0 <bus ID of the DASD>: The DASD cannotbe set offline while it is in use

Explanation: The DASD cannot be set offline becauseit is in use by an internal process. An action to free theDASD might not have completed yet.

User response: Wait some time and set the DASDoffline later.

Severity: Warning

dasd.78e1df A closing parenthesis ')' is missing inthe dasd= parameter

Explanation: The specification for the dasd= kernel ormodule parameter has an opening parenthesis '(' *without a matching closing parenthesis ')'.

User response: Correct the parameter value.

Severity: Warning

dasd.939f75 The statistics have been reset

Explanation: The DASD statistics data have beenreset.



dasd.966201 The statistics feature has been switchedon

Explanation: The statistics feature of the DASD devicedriver has been switched on.



dasd.9d6a8a <bus ID of the DASD>: No verifiedchannel paths remain for the device

Explanation: All verified channel paths to the devicehave become non-operational. Any other paths to thedevice have previously been identified as not usable.The DASD device driver suspends I/O operations andqueues I/O requests for this device until at least onechannel path becomes operational again.

User response: Ensure that each channel path to thedevice has been set up correctly and that the relatedphysical cable connections are in place. Set all paths tothe device offline and online again to repeat the pathverification. Alternatively, set the device offline andonline again to verify all available paths for this device.If this problem persists, gather Linux debug data andreport the problem to your support organization.

Severity: Warning

dasd.a2cf19 <bus ID of the DASD>: Unable toterminate request <pointer to request> onsuspend

Explanation: As part of the suspend process, theDASD device driver terminates requests on the requestqueue. This failed because a previously started I/Ooperation could not be canceled. The suspend processwill be stopped.

User response: Try again to suspend the system.

Severity: Error

dasd.a35e01 <bus ID of the DASD> Setting the DASDonline failed because of a missingdiscipline

Explanation: The DASD was to be set online with aDASD device driver discipline that is not available.

User response: Ensure that all DASD modules areloaded correctly.

Severity: Warning

dasd.696eb5 • dasd.a35e01

Chapter 15. dasd 53

dasd.a3baba <bus ID of the DASD>: I/O operationshave been resumed on the DASD

Explanation: The DASD is no longer in state quiesceand I/O operations can be performed on the device.



dasd.a3bece <bus ID of the DASD>: The DASD cannotbe formatted while it is enabled

Explanation: The DASD you try to format is enabled.Enabled devices cannot be formatted.


Severity: Warning

dasd.a6cafa The statistics feature has been switchedoff

Explanation: The statistics feature of the DASD devicedriver has been switched off.



dasd.a7b0fb <bus ID of the DASD>: The DASD hasbeen put in the quiesce state

Explanation: No I/O operation is possible on thisdevice.

User response: Resume the DASD to enable I/Ooperations.


dasd.adb621 <bus ID of the DASD>: ERP failed for theDASD

Explanation: An error recovery procedure (ERP) wasperformed for the DASD but failed.

User response: Check the message log for previousrelated error messages.

Severity: Error

dasd.b13a1f <bus ID of the DASD>: A timeout erroroccurred for cqr <pointer to request>

Explanation: A channel queued request (cqr) failedbecause it timed out. One possible reason for this erroris that a request did not complete within the timeoutinterval specified for the DASD. The timeout interval isset as the value of the 'timeout' sysfs attribute of aDASD. A value of 0 disables the timeout function. Thetimeout function can be used; for example, bymirroring setups; to quickly process a request queue fora DASD that has become unavailable.

User response: Check the message log for previousrelated error messages. Verify that the storage serverand the connection from host to storage server areoperational. If the 'timeout' sysfs attribute of the DASDhas been set to a value other than 0, verify that thissetting is intentional and change it if required.

Severity: Error

dasd.b3193d <bus ID of the DASD>: An error occurredin the DASD device driver,reason=<reason code>

Explanation: This problem indicates a program errorin the DASD device driver.

User response: Note the reason code and contact yoursupport organization.

Severity: Error

dasd.bba7e6 <bus ID of the DASD>: The specifiedDASD is a partition and cannot beformatted

Explanation: The DASD you try to format is apartition. Partitions cannot be formatted separately. Youcan only format a complete DASD including all itspartitions.

User response: Format the complete DASD.ATTENTION: Formatting irreversibly destroys all dataon all partitions of the DASD.

Severity: Warning

dasd.c0aa71 <bus ID of the DASD> Setting the DASDonline failed because of missing DIAGdiscipline

Explanation: The DASD was to be set online withdiscipline DIAG but this discipline of the DASD devicedriver is not available.

User response: Ensure that the dasd_diag_modmodule is loaded. If your Linux system does notinclude this module, you cannot set DASDs online withthe DIAG discipline.

Severity: Warning

dasd.c1bf11 <bus ID of the DASD>: The DASD cannotbe set offline with open count <count>

Explanation: The DASD is being used by one or moreprocesses and cannot be set offline.

User response: Ensure that the DASD is not in useanymore, for example, unmount all partitions. Then tryagain to set the DASD offline.

Severity: Warning

dasd.a3baba • dasd.c1bf11


dasd.c533c6 <bus ID of the DASD>: No operationalchannel path is left for the device

Explanation: All channel paths to the device havebecome non-operational. The DASD device driversuspends I/O operations and queues I/O requests forthis device until at least one channel path becomesoperational again.

User response: Ensure that each channel path to thedevice has been set up correctly and that the relatedphysical cable connections are in place.

Severity: Warning

dasd.c81491 <bus ID of the DASD>: Device type<device type> is not supported in DIAGmode

Explanation: Only DASD of type FBA and ECKD aresupported in DIAG mode.

User response: Set the sysfs 'use_diag' attribute of theDASD to 0 and try again to access the DASD.

Severity: Warning

dasd.d0c64e <bus ID of the DASD>: A 64-bit DIAGcall failed

Explanation: 64-bit DIAG calls require a 64-bit z/VMversion.

User response: Use z/VM 5.2 or later or set the sysfs'use_diag' attribute of the DASD to 0 to switch offDIAG.

Severity: Warning

dasd.d303ec <bus ID of the DASD>: The access modeof a DIAG device changed to read-only

Explanation: A device changed its access mode fromwriteable to read-only while in use.

User response: Set the device offline, ensure that thedevice is configured correctly in z/VM, then set thedevice online again.

Severity: Warning

dasd.da6176 <bus ID of the DASD>: cqr <request>timed out (<timeout value>) but cannotbe ended, retrying in 5 s

Explanation: A try of the error recovery procedure(ERP) for the channel queued request (cqr) timed outand failed to recover the error. The I/O requestsubmitted during the try could not be canceled. TheERP waits for 5 seconds before trying again.

User response: Ignore this message if it occursinfrequently and if the recovery succeeds during one ofthe retries. If this error persists, check for relatedprevious error messages and report the problem to

your support organization. The timeout can be changedby writing a new value to the sysfs 'expires' attribute ofthe DASD. The value specifies the timeout in seconds.

Severity: Error

dasd.de3a76 The DASD device driver could not beinitialized

Explanation: The initialization of the DASD devicedriver failed because of previous errors.



dasd.df34c6 The IPL device is not a CCW device

Explanation: The value for the dasd= parametercontains the 'ipldev' keyword. During the boot processthis keyword is replaced with the device from whichthe IPL was performed. The 'ipldev' keyword is notvalid if the IPL device is not a CCW device.

User response: Do not specify the 'ipldev' keywordwhen performing an IPL from a device other than aCCW device.

Severity: Error

dasd.e8d084 <bus ID of the DASD>: Accessing theDASD failed because of an incorrectformat (rc=<return code>)

Explanation: The format of the DASD is not correct.

User response: Check the device format. For detailsabout the return code see the section about theINITIALIZE function for DIAGNOSE Code X'250' in"z/VM CP Programming Services". If you cannotresolve the error, note the return code and contact yoursupport organization.

Severity: Warning

dasd.eac657 <bus ID of the DASD>: New DASD with<bytes per block> byte/block, total size<size> KB<access mode>

Explanation: A DASD with the indicated block sizeand total size has been set online. If the DASD isconfigured as read-only to the real or virtual hardware,the message includes an indication of this hardwareaccess mode. The hardware access mode is independentfrom the 'readonly' attribute of the device in sysfs.



dasd.c533c6 • dasd.eac657

Chapter 15. dasd 55

dasd.f97899 <bus ID of the DASD>: Setting the DASDonline failed with rc=<return code>

Explanation: The DASD could not be set onlinebecause of previous errors.

User response: Look for previous error messages. Ifyou cannot resolve the error, note the return code andcontact your support organization.

Severity: Warning

dasd.ff4c45 <range> is not a valid device range

Explanation: A device range specified with the dasd=parameter is not valid.

User response: Examine the dasd= parameter andcorrect the device range.

Severity: Error

dasd.f97899 • dasd.ff4c45


Chapter 16. dcssblk

Messages with a prefix dcssblk are issued by thez/VM discontiguous saved segments (DCSS)device driver. The DCSS device driver providesdisk-like fixed block access to z/VMdiscontiguous saved segments.

dcssblk.0a9a59 The address range of DCSS <devicename> changed while the system wassuspended

Explanation: After resuming the system, the startaddress or end address of a DCSS does not match theaddress when the system was suspended. DCSSs mustnot be changed after the system was suspended. Thiserror cannot be recovered. The system is stopped witha kernel panic.

User response: Reboot Linux.

Severity: Error

dcssblk.14ff71 Device <device name> cannot beremoved because it is not a knowndevice

Explanation: The DCSS device you are trying toremove is not known to the DCSS device driver.

User response: List the entries under/sys/devices/dcssblk/ to see the names of the existingDCSS devices.

Severity: Warning

dcssblk.1e441c Suspending the system failed becauseDCSS device <device name> is writable

Explanation: A system cannot be suspended if one ormore DCSSs are accessed in exclusive- writable mode.DCSS segment types EW, SW, and EN are alwayswritable and must be removed before a system issuspended.

User response: Remove all DCSSs of segment typesEW, SW, and EN by writing the DCSS name to thesysfs 'remove' attribute. Set the access mode for allDCSSs of segment types SR and ER to read-only bywriting 1 to the sysfs 'shared' attribute of the DCSS.Then try again to suspend the system.

Severity: Error

dcssblk.247a44 Device <device name> cannot beremoved while it is in use

Explanation: You are trying to remove a device that isin use.

User response: Make sure that all users of the deviceclose the device before you try to remove it.

Severity: Warning

dcssblk.257c8b Device <device name> is in use, itsDCSSs will be saved when it becomesidle

Explanation: A save request for the device has beendeferred until the device becomes idle. Then changes toall DCSSs that the device maps to will be savedpermanently.



dcssblk.3c90ef Writing to <device name> failedbecause it is a read-only device

Explanation: The DCSS device is in shared accessmode and cannot be written to. Depending on the typeof the DCSSs that the device maps to, you might beable to change the access mode to exclusive-writable.

User response: If the DCSSs of the device are of typeSC, do not attempt to write to the device. If the DCSSsof the device are of type ER or SR, change the accessmode to exclusive-writable before writing to the device.

Severity: Warning

dcssblk.3d858e DCSS <device name> is of type SCand cannot be loaded asexclusive-writable

Explanation: You cannot load a DCSS device inexclusive-writable access mode if the DCSS devisemaps to one or more DCSSs of type SC.

User response: Load the DCSS in shared access mode.

Severity: Error

dcssblk.50ebd0 Device <device name> has become idleand is being saved now

Explanation: A save request for the DCSSs that mapto a DCSS device has been pending while the devicewas in use. The device has become idle and all changesto the DCSSs are now saved permanently.




dcssblk.6ac195 DCSS device <device name> isremoved after a failed access modechange

Explanation: To change the access mode of a DCSSdevice, all DCSSs that map to the device wereunloaded. Reloading the DCSSs for the new accessmode failed and the device is removed.

User response: Look for related messages to find outwhy the DCSSs could not be reloaded. If necessary, addthe device again.

Severity: Error

dcssblk.7b5aa7 A pending save request for device<device name> has been canceled

Explanation: A save request for the DCSSs that mapto a DCSS device has been pending while the devicewas in use. This save request has been canceled.Changes to the DCSSs will not be saved permanently.



dcssblk.9a4530 All DCSSs that map to device <devicename> are saved

Explanation: A save request has been submitted forthe DCSS device. Changes to all DCSSs that map to thedevice are saved permanently.



dcssblk.dd556f DCSS <name 1> and DCSS <name 2>have incompatible types

Explanation: You can only map a set of two or moreDCSSs to a single DCSS device if either all DCSSs inthe set have the same type or if the set contains DCSSsof the two types EW and EN but no other type. TheDCSS device cannot be created because at least two ofthe specified DCSSs are not compatible.

User response: Check the definitions of the DCSSs onthe z/VM hypervisor to verify that their types arecompatible.

Severity: Error

dcssblk.f259b2 Loaded <DCSS names> with total size<total size in bytes> bytes and capacity<total size in 512 byte sectors> sectors

Explanation: The listed DCSSs have been verified ascontiguous and successfully loaded. The displayedsizes are the sums of all DCSSs.



dcssblk.f85784 Adjacent DCSSs <name 1> and <name2> are not contiguous

Explanation: You can only map a set of two or moreDCSSs to a single DCSS device if the DCSSs in the setform a contiguous memory space. The DCSS devicecannot be created because there is a memory gapbetween two adjacent DCSSs.

User response: Ensure that you have specified allDCSSs that belong to the set. Check the definitions ofthe DCSSs on the z/VM hypervisor to verify that theyform a contiguous memory space.

Severity: Error

dcssblk.6ac195 • dcssblk.f85784


Chapter 17. extmem

Messages with a prefix extmem are issued by thekernel module that provides an interface to thez/VM DCSS management functions.

extmem.06a5dd DCSS <DCSS name> has multiplepage ranges and cannot be loaded orqueried

Explanation: You can only load or query a DCSS withmultiple page ranges if: - The DCSS has 6 or fewerpage ranges - The page ranges form a contiguousaddress space - The page ranges are of type EW or EN

User response: Check the definition of the DCSS tomake sure that the conditions for DCSSs with multiplepage ranges are met.

Severity: Error

extmem.262f7b Loading or querying DCSS <DCSSname> resulted in a hardware error

Explanation: Either the z/VM DIAGNOSE X'64' queryor load call issued for the DCSS returned with an error.

User response: Look for previous extmem message tofind the return code from the DIAGNOSE X'64' queryor load call. For details about the return codes see thesection about DIAGNOSE Code X'64' in "z/VM CPProgramming Services".

Severity: Error

extmem.326775 DCSS <DCSS name> overlaps withused memory resources and cannot bereloaded

Explanation: The DCSS has been unloaded and cannotbe reloaded because it overlaps with another loadedDCSS or with the memory of the z/VM guest virtualmachine (guest storage).

User response: Ensure that no DCSS is loaded thathas overlapping memory resources with the DCSS youwant to reload. If the DCSS overlaps with gueststorage, use the DEF STORE CONFIG z/VM CPcommand to create a sufficient storage gap for theDCSS. For details, see the section about the DCSSdevice driver in "Device Drivers, Features, andCommands".

Severity: Warning

extmem.584f8e Unloading unknown DCSS <DCSSname> failed

Explanation: The specified DCSS cannot be unloaded.The DCSS is known to the DCSS device driver but not

to the DCSS kernel interface. This problem indicates aprogram error in extmem.c.

User response: Report this problem to your supportorganization.

Severity: Error

extmem.6bd595 Loading DCSS <DCSS name> failedwith rc=<return code>

Explanation: The DCSS kernel interface used diagnosecall X'64' to load a DCSS. z/VM failed to load theDCSS and returned an error.

User response: For details about the return codes seethe section about DIAGNOSE Code X'64' in "z/VM CPProgramming Services".

Severity: Warning

extmem.7c6a46 Querying a DCSS type failed withrc=<return code>

Explanation: The DCSS kernel interface used z/VMdiagnose call X'64' to query the type of a DCSS. z/VMfailed to determine the type and returned an error.

User response: Look for related messages to find outwhich DCSS is affected. For details about the returncodes see the section about DIAGNOSE Code X'64' in"z/VM CP Programming Services".

Severity: Warning

extmem.7fb545 DCSS <DCSS name> is already in therequested access mode

Explanation: A request to reload a DCSS with a newaccess mode has been rejected because the new accessmode is the same as the current access mode.



extmem.8b00b5 DCSS <DCSS name> cannot beloaded or queried

Explanation: You cannot load or query the specifiedDCSS because it either is not defined in the z/VMhypervisor, or it is a class S DCSS, or it is above 2047MB and he Linux system is a 31-bit system.

User response: Use the CP command "QUERY NSS" tofind out if the DCSS is a valid DCSS that can beloaded.

Severity: Error


extmem.8e36b2 DCSS <DCSS name> exceeds thekernel mapping range (<kernel mappingrange in bytes>) and cannot be loaded

Explanation: You cannot load the DCSS because itexceeds the kernel mapping range limit.

User response: Ensure that the DCSS range is definedbelow the kernel mapping range.

Severity: Error

extmem.972edd Reloading DCSS <DCSS name>failed with rc=<return code>

Explanation: The DCSS kernel interface used z/VMdiagnose call X'64' to reload a DCSS in a differentaccess mode. The DCSS was unloaded but z/VM failedto reload the DCSS.

User response: For details about the return codes seethe section about DIAGNOSE Code X'64' in "z/VM CPProgramming Services".

Severity: Warning

extmem.99ae11 DCSS <DCSS name> is already loadedin a different access mode

Explanation: The DCSS you are trying to load hasalready been loaded in a different access mode. Youcannot simultaneously load the DCSS in differentmodes.

User response: Reload the DCSS in a different modeor load it with the same mode in which it has alreadybeen loaded.

Severity: Error

extmem.9e2ee4 DCSS <DCSS name> cannot beloaded or queried without z/VM

Explanation: A DCSS is a z/VM resource. Your Linuxinstance is not running as a z/VM guest operatingsystem and, therefore, cannot load DCSSs.

User response: Load DCSSs only on Linux instancesthat run as z/VM guest operating systems.

Severity: Error

extmem.aa62ff DCSS <DCSS name> of range <startingpage address> to <ending page address> andtype <DCSS type> loaded in sharedaccess mode

Explanation: The DCSS was loaded successfully inshared access mode.



extmem.b8acd6 Saving a DCSS failed with DEFSEGresponse code <response-code>

Explanation: The DEFSEG z/VM CP command failedto permanently save changes to a DCSS.

User response: Ensure that the z/VM guest virtualmachine is authorized to issue the CP DEFSEGcommand (typically privilege class E). Look for relatedmessages to find the cause of this error. See alsomessage HCP<response-code>E in the DEFSEG sectionof the "z/VM CP Command and Utility Reference".

Severity: Error

extmem.c55583 Saving a DCSS failed with SAVESEGresponse code <response-code>

Explanation: The SAVESEG z/VM CP commandfailed to permanently save changes to a DCSS.

User response: Ensure that the z/VM guest virtualmachine is authorized to issue the CP SAVESEGcommand (typically privilege class E). Look for relatedmessages to find the cause of this error. See alsomessage HCP<response-code>E in the SAVESEGsection of the "z/VM CP Command and UtilityReference".

Severity: Error

extmem.cb0afe <DCSS name> needs used memoryresources and cannot be loaded orqueried

Explanation: You cannot load or query the DCSSbecause it overlaps with an already loaded DCSS orwith the memory of the z/VM guest virtual machine(guest storage).

User response: Ensure that no DCSS is loaded thathas overlapping memory resources with the DCSS youwant to load or query. If the DCSS overlaps with gueststorage, use the DEF STORE CONFIG z/VM CPcommand to create a sufficient storage gap for theDCSS. For details, see the section about the DCSSdevice driver in "Device Drivers, Features, andCommands".

Severity: Error

extmem.d03247 Saving unknown DCSS <DCSSname> failed

Explanation: The specified DCSS cannot be saved. TheDCSS is known to the DCSS device driver but not tothe DCSS kernel interface. This problem indicates aprogram error in extmem.c.


Severity: Error

extmem.8e36b2 • extmem.d03247


extmem.da1614 DCSS <DCSS name> of range<starting page address> to <ending pageaddress> and type <DCSS type> loaded asexclusive-writable

Explanation: The DCSS was loaded successfully inexclusive-writable access mode.



extmem.e08a4c DCSS <DCSS name> overlaps withused storage and cannot be loaded

Explanation: You cannot load the DCSS because itoverlaps with an already loaded DCSS or with thememory of the z/VM guest virtual machine (gueststorage).

User response: Ensure that no DCSS is loaded thathas overlapping memory resources with the DCSS youwant to load. If the DCSS overlaps with guest storage,use the DEF STORE CONFIG z/VM CP command tocreate a sufficient storage gap for the DCSS. For details,see the section about the DCSS device driver in "DeviceDrivers, Features, and Commands".

Severity: Error

extmem.f0af04 DCSS <DCSS name> is in use andcannot be reloaded

Explanation: Reloading a DCSS in a different accessmode has failed because the DCSS is being used by oneor more device drivers. The DCSS remains loaded withthe current access mode.

User response: Ensure that the DCSS is not used byany device driver then try again to load the DCSS withthe new access mode.

Severity: Warning

extmem.febf72 There is not enough memory to loador query DCSS <DCSS name>

Explanation: The available memory is not enough toload or query the DCSS.

User response: Free some memory and repeat thefailed operation.

Severity: Error

extmem.da1614 • extmem.febf72

Chapter 17. extmem 61


Chapter 18. hvc_iucv

Messages with a prefix hvc_iucv are issued by thez/VM IUCV Hypervisor Console (HVC) devicedriver. This device driver supports terminalaccess through the iucvconn program to instancesof Linux on z/VM.

hvc_iucv.09cae6 A connection request from z/VMuser ID <ID> was refused

Explanation: An IUCV connection request fromanother z/VM guest virtual machine has been refused.The request was from a z/VM guest virtual machinethat is not listed by the "hvc_iucv_allow=" kernelparameter.

User response: Check the "hvc_iucv_allow=" kernelparameter setting. Consider adding the z/VM user IDto the "hvc_iucv_allow=" list in the kernel parameterline and reboot Linux.


hvc_iucv.1bc1e0 hvc_iucv_allow= specifies too manyz/VM user IDs

Explanation: The "hvc_iucv_allow=" kernel parameterspecifies a comma-separated list of z/VM user IDs thatare permitted to connect to the z/VM IUCV hypervisordevice driver. The number of z/VM user IDs that arespecified with the "hvc_iucv_allow=" kernel parameterexceeds the maximum of 500.

User response: Correct the "hvc_iucv_allow=" settingby reducing the z/VM user IDs in the list and rebootLinux.

Severity: Error

hvc_iucv.339854 Creating a new HVC terminal devicefailed with error code=<errno>

Explanation: The device driver initialization failed toallocate a new HVC terminal device. A possible causeof this problem is memory constraints.

User response: If the error code is -12 (ENOMEM),consider assigning more memory to your z/VM guestvirtual machine.

Severity: Error

hvc_iucv.5a5e90 Registering HVC terminal device asLinux console failed

Explanation: The device driver initialization failed toset up the first HVC terminal device for use as Linuxconsole.

User response: If the error code is -12 (ENOMEM),consider assigning more memory to your z/VM guestvirtual machine.

Severity: Error

hvc_iucv.5bc646 Allocating memory failed withreason code=<reason>

Explanation: The z/VM IUCV hypervisor console(HVC) device driver initialization failed, because of ageneral memory allocation failure. The reason codeindicates the memory operation that has failed:kmem_cache (reason code=1), mempool (reasoncode=2), or hvc_iucv_allow= (reason code=3)

User response: Consider assigning more memory toyour z/VM guest virtual machine.

Severity: Error

hvc_iucv.691dff The z/VM IUCV HVC device drivercannot be used without z/VM

Explanation: The z/VM IUCV hypervisor console(HVC) device driver requires the z/VM inter-usercommunication vehicle (IUCV).

User response: Set "hvc_iucv=" to zero in the kernelparameter line and reboot Linux.

Severity: Notice

hvc_iucv.9f5b40 hvc_iucv_allow= does not specify avalid z/VM user ID list

Explanation: The "hvc_iucv_allow=" kernel parameterspecifies a comma-separated list of z/VM user IDs thatare permitted to connect to the z/VM IUCV hypervisordevice driver. The z/VM user IDs in the list must notexceed eight characters and must not contain spaces.

User response: Correct the "hvc_iucv_allow=" settingin the kernel parameter line and reboot Linux.

Severity: Error

hvc_iucv.d4fcff Registering IUCV handlers failedwith error code=<errno>

Explanation: The device driver initialization failed toregister with z/VM IUCV to handle IUCV connections,as well as sending and receiving of IUCV messages.

User response: Check for related IUCV error messagesand see the errno manual page to find out what causedthe problem.

Severity: Error


hvc_iucv.e38b47 <hvc_iucv_devices> is not a validvalue for the hvc_iucv= kernelparameter

Explanation: The "hvc_iucv=" kernel parameterspecifies the number of z/VM IUCV hypervisor console(HVC) terminal devices. The parameter value rangesfrom 0 to 8. If zero is specified, the z/VM IUCV HVCdevice driver is disabled and no IUCV-based terminalaccess is available.

User response: Correct the "hvc_iucv=" setting in thekernel parameter line and reboot Linux.

Severity: Error

hvc_iucv.e38b47


Chapter 19. hypfs

Messages with a prefix hypfs are issued by theS/390 hypervisor file system, which providesaccess to LPAR and z/VM hypervisor data.

hypfs.7a79f0 Initialization of hypfs failed withrc=<error code>

Explanation: Initialization of hypfs failed because ofresource or hardware constraints. Possible reasons forthis problem are insufficient free memory or missinghardware interfaces.

User response: See errno.h for information about theerror codes.

Severity: Error

hypfs.7f5705 The hardware system does not supporthypfs

Explanation: hypfs requires DIAGNOSE Code X'204'but this diagnose code is not available on yourhardware. You need more recent hardware to usehypfs.


Severity: Error

hypfs.90c29b Updating the hypfs tree failed

Explanation: There was not enough memory availableto update the hypfs tree.

User response: Free some memory and try again toupdate the hypfs tree. Consider assigning morememory to your LPAR or z/VM guest virtual machine.

Severity: Error

hypfs.a2406e <mount option> is not a valid mountoption

Explanation: hypfs has detected mount options thatare not valid.

User response: See "Device Drivers Features andCommands" for information about valid mount optionsfor hypfs.

Severity: Error

hypfs.cccfb8 The hardware system does not provideall functions required by hypfs

Explanation: hypfs requires DIAGNOSE Code X'224'but this diagnode code is not available on yourhardware. You need more recent hardware to usehypfs.


Severity: Error



Chapter 20. iucv

Messages with a prefix iucv are issued by theInter-User Communication Vehicle (IUCV) devicedriver. IUCV is a z/VM communication facilitythat enables a program running in one z/VMguest to communicate with another z/VM guest,or with a control program, or even with itself.

iucv.1d65b1 Suspending Linux did not completelyclose all IUCV connections

Explanation: When resuming a suspended Linuxinstance, the IUCV base code found data structuresfrom one or more IUCV connections that existed beforethe Linux instance was suspended. Modules that useIUCV connections must close these connections when aLinux instance is suspended. This problem indicates anerror in a program that used an IUCV connection.


Severity: Warning

iucv.beb348 Defining an interrupt buffer on CPU<CPU number> failed with0x<hexadecimal error value> (<short errorcode explanation>)

Explanation: Defining an interrupt buffer for externalinterrupts failed. Error value 0x03 indicates a problemwith the z/VM directory entry of the z/VM guestvirtual machine. This problem can also be caused by aprogram error.

User response: If the error value is 0x03, examine thez/VM directory entry of your z/VM guest virtualmachine. If the directory entry is correct or if the errorvalue is not 0x03, report this problem to your supportorganization.

Severity: Warning



Chapter 21. lcs

Messages with a prefix lcs are issued by the LANchannel station device driver. The LCS devicedriver supports non-QDIO communicationsthrough Open Systems Adapters (OSA).

lcs.23ff8e <bus ID of the LCS device>: Sending datafrom the LCS device to the LAN failedwith rc=<ccw_device_resume return code indecimal notation>

Explanation: The LAN channel station (LCS) devicedriver could not send data to the LAN using the LCSdevice. This might be a temporary problem. Operationscontinue on the LCS device.

User response: If this problem occurs frequently,initiate a recovery process, for example, by writing '1'to the 'recover' sysfs attribute of the device. If theproblem persists, contact IBM support.

Severity: Error

lcs.2a7553 <bus ID of the LCS device>: The LCSdevice stopped because of an error,dstat=0x<device status>,cstat=0x<subchannel status>

Explanation: The LAN channel station (LCS) devicereported an error. The LCS device driver might start adevice recovery process.

User response: If the device driver does not start arecovery process, initiate a recovery process, forexample, by writing '1' to the 'recover' sysfs attribute ofthe device. If the problem persists, note the statusinformation provided with the message and contactIBM support.

Severity: Warning

lcs.432fb3 <bus ID of the LCS device>: An I/O-erroroccurred on the LCS device

Explanation: The LAN channel station (LCS) devicereported a problem that can be recovered by the LCSdevice driver. Repeated occurrences of this problemindicate a malfunctioning device.

User response: If this problem occurs frequently,initiate a recovery process for the device, for example,by writing '1' to the 'recover' sysfs attribute of thedevice.

Severity: Warning

lcs.4abb3d <bus ID of the LCS device>: Shuttingdown the LCS device failed

Explanation: A request to shut down a LAN channelstation (LCS) device resulted in an error. The error islogged in the LCS trace at trace level 4.

User response: Try again to shut down the device. Ifthe error persists, see the LCS trace to find out whatcauses the error.

Severity: Error

lcs.618a07 <bus ID of the LCS device>: A commandtimed out on the LCS device



Severity: Warning

lcs.64a3d7 <bus ID of the LCS device>: Allocating asocket buffer to interface <networkinterface> failed

Explanation: LAN channel station (LCS) devicesrequire a socket buffer (SKB) structure for storingincoming data. The LCS device driver failed to allocatean SKB structure to the LCS device. A likely cause ofthis problem is memory constraints.

User response: Free some memory and repeat thefailed operation.

Severity: Error

lcs.b44620 <bus ID of the LCS device>: An erroroccurred on the LCS device, rc=<returncode>



Severity: Warning


lcs.c375fd <bus ID of the LCS device>: Detecting anetwork adapter for LCS devices failedwith rc=<lcs_detect return code in decimalnotation> (0x<lcs_detect return code inhexadecimal notation>)

Explanation: The LCS device driver could notinitialize a network adapter.

User response: Note the return codes from the errormessage and contact IBM support.

Severity: Error

lcs.e47e1f <bus ID of the LCS device>: Starting anLCS device resulted in an error,rc=<ccw_device_start return code in decimalnotation>!

Explanation: The LAN channel station (LCS) devicedriver failed to initialize an LCS device. The device isnot operational.

User response: Initiate a recovery process, forexample, by writing '1' to the 'recover' sysfs attribute ofthe device. If the problem persists, contact IBMsupport.

Severity: Error

lcs.f3f094 <bus ID of the LCS device>: A recoveryprocess has been started for the LCSdevice

Explanation: The LAN channel station (LCS) device isshut down and restarted. The recovery process mighthave been initiated by a user or started automaticallyas a response to a device problem.

User response: Wait until a message indicates thecompletion of the recovery process.

Severity: Warning

lcs.c375fd • lcs.f3f094


Chapter 22. monreader

Messages with a prefix monreader are issued bythe z/VM *MONITOR record reader devicedriver. This device driver enables monitoringsoftware on Linux to access z/VM *MONITORrecords, which contain data about z/VM guestvirtual machines.

monreader.0111fc The specified *MONITOR DCSS<DCSS name> does not have therequired type SC

Explanation: The DCSS that was specified with themonreader.mondcss kernel parameter or with themondcss module parameter cannot be a *MONITORDCSS because it is not of type SC.

User response: Confirm that you are using the nameof the DCSS that has been configured as the*MONITOR DCSS on the z/VM hypervisor. If thedefault name, MONDCSS, is used, omit themonreader.mondcss or mondcss parameter.

Severity: Error

monreader.029e2e The read queue for monitor data isfull

Explanation: The read function of the z/VM*MONITOR device driver returns EOVERFLOWbecause not enough monitor data has been read sincethe monitor device has been opened. Monitor dataalready read are valid and subsequent reads returnvalid data but some intermediate data might bemissing.

User response: Be aware that monitor data might bemissing. Assure that you regularly read monitor dataafter opening the monitor record device.

Severity: Warning

monreader.15a7a1 z/VM *MONITOR system servicedisconnected with rc=<IPUSER SEVERreturn code>

Explanation: The z/VM *MONITOR record devicedriver receives monitor records through an IUCVconnection to the z/VM *MONITOR system service.This connection has been severed and the read functionof the z/VM *MONITOR device driver returns EIO. Alldata received since the last read with 0 size is incorrect.

User response: Disregard all monitor data read sincethe last read with 0 size. Close and reopen the monitorrecord device. For information about the IPUSERSEVER return codes see "z/VM Performance".

Severity: Error

monreader.1a46fe The z/VM *MONITOR recorddevice driver cannot be loaded withoutz/VM

Explanation: The z/VM *MONITOR record devicedriver uses z/VM system services to provide monitordata about z/VM guest operating systems toapplications on Linux. On Linux instances that run inenvironments other than the z/VM hypervisor, thez/VM *MONITOR record device driver does notprovide any useful function and the correspondingmonreader module cannot be loaded.

User response: Load the z/VM *MONITOR recorddevice driver only on Linux instances that run as guestoperating systems of the z/VM hypervisor. If the z/VM*MONITOR record device driver has been compiledinto the kernel, ignore this message.

Severity: Error

monreader.6f04b5 The z/VM *MONITOR recorddevice driver failed to register withIUCV

Explanation: The z/VM *MONITOR record devicedriver receives monitor data through an IUCVconnection and needs to register with the IUCV devicedriver. This registration failed and the z/VM*MONITOR record device driver was not loaded. Apossible cause of this problem is insufficient memory.

User response: Free some memory and try again toload the module. If the z/VM *MONITOR recorddevice driver has been compiled into the kernel, youmight have to configure more memory and rebootLinux. If you do not want to read monitor data, ignorethis message.

Severity: Error

monreader.88c26a Connecting to the z/VM*MONITOR system service failed withrc=<IUCV CONNECT return code>

Explanation: The z/VM *MONITOR record devicedriver receives monitor records through an IUCVconnection to the z/VM *MONITOR system service.This connection could not be established when themonitor record device was opened. If the return code is15, your z/VM guest virtual machine is not authorizedto connect to the *MONITOR system service.

User response: If the return code is 15, ensure that theIUCV *MONITOR statement is included in the z/VMdirectory entry for your z/VM guest virtual machine.For other IUCV CONNECT return codes see the IUCVsection in "CP Programming Services" and the


*MONITOR section in "z/VM Performance".

Severity: Error

monreader.c042b6 Reading monitor data failed withrc=<return code>

Explanation: The z/VM *MONITOR record devicedriver failed to read monitor data because the IUCVREPLY function failed. The read function against themonitor record device returns EIO. All monitor datathat has been read since the last read with 0 size isincorrect.

User response: Disregard all monitor data that hasbeen read since the last read with 0 size. If the devicedriver has been compiled as a separate module, unloadand reload the monreader module. If the device driverhas been compiled into the kernel, reboot Linux. Formore information about possible causes of the error seethe IUCV section in "z/VM CP Programming Services"and the *MONITOR section in "z/VM Performance".

Severity: Error

monreader.ca6466 Disconnecting the z/VM*MONITOR system service failed withrc=<IUCV SEVER return code>

Explanation: The z/VM *MONITOR record devicedriver receives monitor data through an IUCVconnection to the z/VM *MONITOR system service.This connection could not be closed when the monitorrecord device was closed. You might not be able toresume monitoring.

User response: No immediate action is necessary. Ifyou cannot open the monitor record device in thefuture, reboot Linux. For information about the IUCVSEVER return codes see the IUCV section in "CPProgramming Services" and the *MONITOR section in"z/VM Performance".

Severity: Warning

monreader.c042b6 • monreader.ca6466


Chapter 23. monwriter

Messages with a prefix monwriter are issued bythe monitor stream application device driver.Applications can use this device driver to writemonitor data in the form of APPLDATA recordsto the z/VM monitor stream.

monwriter.fcbea9 Writing monitor data failed withrc=<return code>

Explanation: The monitor stream application devicedriver used the z/VM diagnose call DIAG X'DC' tostart writing monitor data. z/VM returned an error andthe monitor data cannot be written. If the return code is5, your z/VM guest virtual machine is not authorizedto write monitor data.

User response: If the return code is 5, ensure thatyour z/VM guest virtual machine's entry in the z/VMdirectory includes the OPTION APPLMON statement.For other return codes see the section aboutDIAGNOSE Code X'DC' in "z/VM CP ProgrammingServices".

Severity: Error



Chapter 24. netiucv

Messages with a prefix netiucv are issued by theNETIUCV device driver. This network devicedriver uses IUCV to connect instances of Linuxon z/VM, or to connect an instance of Linux onz/VM to another z/VM guest such as a TCP/IPservice machine.

netiucv.04ce63 <bus ID of the IUCV device>: The IUCVdevice failed to connect to the peer onz/VM guest <z/VM user ID>

Explanation: The connection cannot be establishedbecause the z/VM guest virtual machine with the peerinterface is not configured for IUCV connections.

User response: Configure the z/VM guest virtualmachine with the peer interface for IUCV connections;then try again to establish the connection.

Severity: Warning

netiucv.297069 <bus ID of the IUCV device>: z/VMguest <remote z/VM user ID> has toomany IUCV connections to connect withthe IUCV device

Explanation: Connecting to the remote z/VM guestvirtual machine failed because the maximum numberof IUCV connections for the remote z/VM guest virtualmachine has been reached.

User response: Close some of the established IUCVconnections on the remote z/VM guest virtual machine;then try again to establish the connection.

Severity: Error

netiucv.55da31 <bus ID of the IUCV device>: The IUCVinterface to <remote z/VM user ID> hasbeen established successfully

Explanation: The IUCV interface to the remote z/VMguest virtual machine has been established and can beactivated with "ifconfig up" or an equivalent command.



netiucv.56149b <bus ID of the IUCV device>:Connecting the IUCV device failed witherror <error code>

Explanation: The connection cannot be establishedbecause of an IUCV CONNECT error.


Severity: Error

netiucv.5be5dc <bus ID of the IUCV device>: The peerinterface of the IUCV device has closedthe connection

Explanation: The peer interface on the remote z/VMguest virtual machine has closed the connection. Do notexpect further packets on this interface. Any packetsyou send to this interface will be dropped.



netiucv.6b758f <bus ID of the IUCV device>: The IUCVdevice has been connected successfullyto <remote z/VM user ID>

Explanation: The connection has been established andthe interface is ready to transmit communicationpackages.



netiucv.863549 <bus ID of the IUCV device>: The IUCVdevice cannot connect to a z/VM guestwith no IUCV authorization

Explanation: Because the remote z/VM guest virtualmachine is not authorized for IUCV connections, theconnection cannot be established.

User response: Add the statements 'IUCV ALLOW'and 'IUCV ANY' to the z/VM directory entry of theremote z/VM guest virtual machine; then try again toestablish the connection. See "z/VM CP Planning andAdministration" for details about the IUCV statements.

Severity: Error

netiucv.bcbc54 <bus ID of the IUCV device>: The IUCVdevice failed to connect to z/VM guest<z/VM user ID>

Explanation: The connection cannot be establishedbecause the z/VM guest virtual machine with the peerinterface is not running.

User response: Ensure that the z/VM guest virtualmachine with the peer interface is running; then tryagain to establish the connection.

Severity: Warning


netiucv.c1b7ef <bus ID of the IUCV device>: The IUCVdevice is connected to <remote z/VM userID> and cannot be removed

Explanation: Removing a connection failed becausethe interface is active with a peer interface on a remotez/VM guest virtual machine.

User response: Deactivate the interface with "ifconfigdown" or an equivalent command; then try again toremove the interface.

Severity: Warning

netiucv.cfb810 <bus ID of the IUCV device>:Connecting the IUCV device wouldexceed the maximum number of IUCVconnections

Explanation: The connection cannot be establishedbecause the maximum number of IUCV connectionshas been reached on the local z/VM guest virtualmachine.

User response: Close some of the established IUCVconnections on the local z/VM guest virtual machine;then try again to establish the connection.

Severity: Error

netiucv.e9590c <bus ID of the IUCV device>: The peerz/VM guest <remote z/VM user ID> hasclosed the connection

Explanation: The peer interface is no longer available.

User response: Either deactivate and remove theinterface, or wait for the peer z/VM guest tore-establish the interface.


netiucv.c1b7ef • netiucv.e9590c


Chapter 25. os_info

Messages with a prefix os_info are issued byLinux in kdump mode.

os_info.2fdede entry <entry ID>: <entry state>(addr=0x<entry address> size=<entry size>)

Explanation: Linux is running in kdump mode andreports information defined by the previously runningproduction kernel. Possible values for "entry state" are:- copied: The entry has been found, verified, andcopied - not available: The entry has not been defined -checksum failed: The entry has been found, but it is notvalid

User response: If kdump fails, contact your serviceorganization and include this message in the errorreport.


os_info.d3cf4c crashkernel: addr=0x<address>size=<size>

Explanation: Linux is running in kdump mode andreports the address and size of the memory area thatwas reserved for kdump by the previously runningproduction kernel.





Chapter 26. perf

Messages with a prefix perf are issued by kernelfunctions that support the z/ArchitectureCPU-measurement facility.

perf.ee05c5 CPU[<cpu number>] CPUM_CF:ver=<first version number>.<second versionnumber> A=<counter set authorization>E=<counter set enable controls> C=<counterset activation controls>

Explanation: This message displays information aboutthe CPU-measurement counter facility (CPUM_CF) on aparticular CPU. For details, see "TheLoad-Program-Parameter and the CPU-MeasurementFacilities", SA23-2260.





Chapter 27. qeth

Messages with a prefix qeth are issued by theqeth device driver. The qeth device driversupports a multitude of network connections, forexample, connections through Open SystemsAdapters (OSA), HiperSockets, guest LANs, andvirtual switches.

qeth.03aa42 <bus ID of the qeth device>: Interface<interface name> is down because theadjacent port is no longer in reflectiverelay mode

Explanation: The ISOLATION_FORWARD policy isactive for the QDIO data connection isolation of theqeth device. This policy requires a network adapter inVirtual Ethernet Port Aggregator (VEPA) mode with anadjacent switch port in reflective relay mode. Thereflective relay mode on the adjacent switch port wasdisabled. The qeth device was set offline and theinterface was deactivated to prevent any unintendednetwork traffic.

User response: Enable the reflective relay mode againon the adjacent port or use the 'isolation' sysfs attributeof the qeth device to set a different policy for the QDIOdata connection isolation. You can then resumeoperations by setting the qeth device back online andactivating the interface.

Severity: Error

qeth.1d3c1d <bus ID of the qeth device>: Registering IPaddress <IP address> failed

Explanation: An IP address could not be registeredwith the network adapter.

User response: Check if another operating systeminstance has already registered the IP address with thesame network adapter or at the same logical IP subnet.

Severity: Warning

qeth.1e4c70 <bus ID of the qeth device>: The device isnot authorized to run as a HiperSocketsnetwork traffic analyzer

Explanation: The sysfs 'sniffer' attribute of theHiperSockets device has the value '1'. Thecorresponding HiperSockets interface is switched intopromiscuous mode but the network traffic analyzer(NTA) rules configured at the Support Element (SE) donot allow tracing. Possible reasons are: - Tracing is notauthorized for all HiperSockets channels in themainframe system - Tracing is not authorized for thisHiperSockets channel - LPAR is not authorized toenable an NTA

User response: Configure appropriate HiperSocketsNTA rules at the SE.

Severity: Warning

qeth.21a074 <bus ID of the qeth device>: There is nokernel module to support discipline<discipline>

Explanation: The qeth device driver or a usercommand requested a kernel module for a particularqeth discipline. Either the discipline is not supportedby the qeth device driver or the requested module isnot available to your Linux system.

User response: Check if the requested disciplinemodule has been compiled into the kernel or is presentin /lib/modules/<version>/kernel/drivers/s390/net.

Severity: Error

qeth.2211d4 <bus ID of the qeth device>: The LAN isoffline

Explanation: A start LAN command was sent by theqeth device driver but the physical or virtual adapterhas not started the LAN. The LAN might take a fewseconds to become available.

User response: Check the status of the qeth device, forexample, with the lsqeth command. If the device doesnot become operational within a few seconds, initiate arecovery process, for example, by writing '1' to the'recover' sysfs attribute of the device.

Severity: Warning

qeth.2f18a4 <bus ID of the qeth device>: Startingmulticast support for <network interfacename> failed

Explanation: The qeth device driver could not startmulticast support on the network adapter.

User response: Ungroup and regroup the subchanneltriplet of the device. If this does not resolve theproblem, reboot Linux. If the problem persists, gatherLinux debug data and report the problem to yoursupport organization.

Severity: Warning

qeth.3acf0c <bus ID of the qeth device>: The qethdevice driver failed to recover an erroron the device

Explanation: The qeth device driver performed anautomatic recovery operation to recover an error on aqeth device. The recovery operation failed.


User response: Try the following actions in the givenorder: i) Check the status of the qeth device, forexample, with the lsqeth command. ii) Initiate arecovery process by writing '1' to the 'recover' sysfsattribute of the device. iii) Ungroup and regroup thesubchannel triplet of the device. vi) Reboot Linux. v) Ifthe problem persists, gather Linux debug data andreport the problem to your support organization.

Severity: Warning

qeth.3d0305 <bus ID of the qeth device>: The adapter isused exclusively by another host

Explanation: The qeth adapter is exclusively used byanother host.

User response: Use another qeth adapter or configurethis one not exclusively to a particular host.

Severity: Error

qeth.48d0da <bus ID of the qeth device>: The networkadapter failed to generate a unique ID

Explanation: In IBM mainframe environments,network interfaces are not identified by a specific MACaddress. Therefore, the network adapters provide thenetwork interfaces with unique IDs to be used in theirIPv6 link local addresses. Without such a unique ID,duplicate addresses might be assigned in other LPARs.

User response: Install the latest firmware on theadapter hardware. Manually, configure an IPv6 linklocal address for this device.

Severity: Warning

qeth.4a588d <bus ID of the qeth device>: CompletionQueue support disabled

Explanation: The HiperSockets device is disabled forcompletion queueing. This device cannot or no longerbe used to set up AF_IUCV communication in anLPAR.



qeth.4da7f2 Initializing the qeth device driver failed

Explanation: The base module of the qeth devicedriver could not be initialized.

User response: See errno.h to determine the reason forthe error. i) Reboot Linux. ii) If the problem persists,gather Linux debug data and report the problem toyour support organization.

Severity: Error

qeth.53237e <bus ID of the qeth device>: A connectioncould not be established because of anOLM limit

Explanation: z/OS® has activated Optimized LatencyMode (OLM) for a connection through an OSAExpress3 adapter. This reduces the maximum numberof concurrent connections per physical port for sharedadapters. The new connection would exceed themaximum. Linux cannot establish further connectionsusing this adapter.

User response: If possible, deactivate an existingconnection that uses this adapter and try again toestablish the new connection. If you cannot free anexisting connection, use a different adapter for the newconnection.

Severity: Error

qeth.5cb8a3 <bus ID of the qeth device>: The qethdevice is not configured for the OSIlayer required by z/VM

Explanation: A qeth device that connects to a virtualnetwork on z/VM must be configured for the sameOpen Systems Interconnection (OSI) layer as the virtualnetwork. An ETHERNET guest LAN or VSWITCH usesthe data link layer (layer 2) while an IP guest LAN orVSWITCH uses the network layer (layer 3).

User response: If you are connecting to anETHERNET guest LAN or VSWITCH, set the layer2sysfs attribute of the qeth device to 1. If you areconnecting to an IP guest LAN or VSWITCH, set thelayer2 sysfs attribute of the qeth device to 0.

Severity: Error

qeth.5d5e5c There is no IPv6 support for the layer 3discipline

Explanation: If you want to use IPv6 with the layer 3discipline, you need a Linux kernel with IPv6 support.Because your Linux kernel has not been compiled withIPv6 support, you cannot use IPv6 with the layer 3discipline, even if your adapter supports IPv6.

User response: Use a Linux kernel that has beencomplied to include IPv6 support if you want to useIPv6 with layer 3 qeth devices.

Severity: Warning

qeth.5ff844 <bus ID of the qeth device>: CompletionQueue support enabled

Explanation: The HiperSockets device is enabled forcompletion queueing. This is part of the process to setup AF_IUCV communication in an LPAR.



qeth.3d0305 • qeth.5ff844


qeth.666544 <bus ID of the qeth device>: MAC address<MAC-address> already exists

Explanation: Setting the MAC address for the qethdevice fails, because this MAC address is alreadydefined on the OSA CHPID.

User response: Use a different MAC address for thisqeth device.

Severity: Warning

qeth.72880f <bus ID of the qeth device>: AHiperSockets network traffic analyzer isalready active in the HiperSockets LAN

Explanation: The sysfs 'sniffer' attribute of theHiperSockets device has the value '1'. The HiperSocketsinterface is switched into promiscuous mode butanother HiperSockets device on the same HiperSocketschannel is already running as a network trafficanalyzer. A HiperSockets channel can only have oneactive network traffic analyzer.

User response: Do not configure multipleHiperSockets devices in the same HiperSockets channelas tracing devices.

Severity: Warning

qeth.760272 <bus ID of the qeth device>: The reflectiverelay mode cannot be enabled at theadjacent switch port

Explanation: The 'isolation' sysfs attribute of the qethdevice could not be set to 'forward'. This setting selectsthe ISOLATION_FORWARD policy for the QDIO dataconnection isolation. The ISOLATION_FORWARDpolicy requires a network adapter in Virtual EthernetPort Aggregator (VEPA) mode with an adjacent switchport in reflective relay mode. The qeth device driverfailed to enable the required reflective relay mode onthe adjacent switch port although the switch portsupports this mode.

User response: Enable reflective relay mode on theswitch for the adjacent port and try again.

Severity: Error

qeth.77cf86 <bus ID of the qeth device>: Enablingbroadcast filtering for <network interfacename> failed

Explanation: The qeth device driver could not enablebroadcast filtering on the network adapter.


Severity: Warning

qeth.7ade71 <bus ID of the qeth device>: StartingVLAN support for <network interfacename> failed

Explanation: The qeth device driver could not startVLAN support on the network adapter.

User response: None if you do not require VLANsupport. If you need VLAN support, ungroup andregroup the subchannel triplet of the device. If thisdoes not resolve the problem, reboot Linux. If theproblem persists, gather Linux debug data and reportthe problem to your support organization.

Severity: Warning

qeth.86d925 <bus ID of the qeth device>: Turning offreflective relay mode at the adjacentswitch failed

Explanation: The policy for the QDIO data connectionisolation was changed successfully, andcommunications are now handled according to the newpolicy. The ISOLATION_FORWARD policy is no longerused, but the qeth device driver could not turn off thereflective relay mode on the adjacent switch port.

User response: Check the adjacent switch for errorsand correct the problem.

Severity: Warning

qeth.883aa0 <bus ID of the qeth device>: Starting HWchecksumming for <network interfacename> failed, using SW checksumming

Explanation: The network adapter supports hardwarechecksumming for incoming IP packages but the qethdevice driver could not start hardware checksummingon the adapter. The qeth device driver continues to usesoftware checksumming for incoming IP packages.

User response: None if you do not require hardwarechecksumming for incoming network traffic. If youwant to enable hardware checksumming, ungroup andregroup the subchannel triplet of the device. If thisdoes not resolve the problem, reboot Linux. If theproblem persists, gather Linux debug data and reportthe problem to your support organization.

Severity: Warning

qeth.8a7bb9 <bus ID of the qeth device>: Starting IPfragmentation support for <networkinterface name> failed

Explanation: The qeth device driver could not start IPfragmentation support on the network adapter.


qeth.666544 • qeth.8a7bb9

Chapter 27. qeth 83

Severity: Warning

qeth.90d7eb <bus ID of the qeth device>: MAC address<MAC-address> is not authorized

Explanation: This qeth device is a virtual networkinterface card (NIC), to which z/VM has alreadyassigned a MAC address. z/VM MAC addressverification does not allow you to change thispredefined address.

User response: None; use the MAC address that hasbeen assigned by z/VM.

Severity: Warning

qeth.9b3034 <bus ID of the qeth device>: Setting thedevice online failed because ofinsufficient authorization

Explanation: The qeth device is configured with OSXCHPIDs. An OSX CHPID cannot be activated unlessthe LPAR is explicitly authorized to access it. For z/VMguest operating systems, the z/VM user ID must beexplicitly authorized in addition to the LPAR. Yougrant these authorizations through the Service Element.

User response: At the Service Element, authorize theLPAR and, if applicable, the z/VM user ID for usingthe OSX CHPIDs with which the qeth device has beenconfigured. Then try again to set the device online.

Severity: Error

qeth.9e9f31 <bus ID of the qeth device>: Setting upbroadcast echo filtering for <networkinterface name> failed

Explanation: The qeth device driver could not set upbroadcast echo filtering on the network adapter.


Severity: Warning

qeth.a4a7ee <bus ID of the qeth device>: The link for<network interface name> on CHPID0x<CHPID> has been restored

Explanation: A failed network link has beenre-established. A device recovery is in progress.



qeth.a853bd <bus ID of the qeth device>: Reading theadapter MAC address failed

Explanation: The qeth device driver could not readthe MAC address from the network adapter.


Severity: Warning

qeth.aa2df0 <bus ID of the qeth device>: TheHiperSockets network traffic analyzer isdeactivated

Explanation: The sysfs 'sniffer' attribute of theHiperSockets device has the value '1'. Promiscuousmode has been switched off for the correspondingHiperSockets interface As a result, the HiperSocketsnetwork traffic analyzer is stopped on the device.



qeth.aa55b2 <bus ID of the qeth device>: The adapterhardware is of an unknown type

Explanation: The qeth device driver does notrecognize the adapter hardware. The cause of thisproblem could be a hardware error or a Linux levelthat does not support your adapter hardware.

User response: i) Investigate if your adapter hardwareis supported by your Linux level. Consider usinghardware that is supported by your Linux level orupgrading to a Linux level that supports yourhardware. ii) Install the latest firmware on your adapterhardware. iii) If the problem persists and is not causedby a version mismatch, contact IBM support.

Severity: Error

qeth.c0a93c <bus ID of the qeth device>: Enabling HWchecksumming for <network interfacename> failed, using SW checksumming

Explanation: The network adapter supports hardwarechecksumming for incoming IP packages but the qethdevice driver could not enable hardwarechecksumming on the adapter. The qeth device drivercontinues to use software checksumming for incomingIP packages.

User response: None if you do not require hardwarechecksumming for incoming network traffic. If youwant to enable hardware checksumming, ungroup andregroup the subchannel triplet of the device. If thisdoes not resolve the problem, reboot Linux. If theproblem persists, gather Linux debug data and reportthe problem to your support organization.

qeth.90d7eb • qeth.c0a93c


Severity: Warning

qeth.c13293 <bus ID of the qeth device>: The adjacentswitch port does not support reflectiverelay mode

Explanation: The 'isolation' sysfs attribute of the qethdevice could not be set to 'forward'. This setting selectsthe ISOLATION_FORWARD policy for the QDIO dataconnection isolation. The ISOLATION_FORWARDpolicy requires a network adapter in Virtual EthernetPort Aggregator (VEPA) mode with an adjacent switchport in reflective relay mode.

User response: Use a switch port that supportsreflective relay mode if you want to use theISOLATION_FORWARD policy for the qeth device.

Severity: Error

qeth.c4e1a6 <bus ID of the qeth device>: TheHiperSockets network traffic analyzer isactivated

Explanation: The sysfs 'sniffer' attribute of theHiperSockets device has the value '1'. Thecorresponding HiperSockets interface has beenswitched into promiscuous mode. As a result, theHiperSockets network traffic analyzer is started on thedevice.



qeth.c98a58 <bus ID of the qeth device>: Enabling HWTX checksumming for <network interfacename> failed, using SW TXchecksumming

Explanation: The network adapter supports hardwarechecksumming for outgoing IP packages but the qethdevice driver could not enable hardware TXchecksumming on the adapter. The qeth device drivercontinues to use software checksumming for outgoingIP packages.

User response: None if you do not require hardwarechecksumming for outgoing network traffic. If youwant to enable hardware checksumming, ungroup andregroup the subchannel triplet of the device. If thisdoes not resolve the problem, reboot Linux. If theproblem persists, gather Linux debug data and reportthe problem to your support organization.

Severity: Warning

qeth.cc86d9 <bus ID of the qeth device>: ActivatingIPv6 support for <network interface name>failed

Explanation: The qeth device driver could not activateIPv6 support on the network adapter.

User response: None if you do not require IPv6communication. If you need IPv6 support, ungroup andregroup the subchannel triplet of the device. If thisdoes not resolve the problem, reboot Linux. If theproblem persists, gather Linux debug data and reportthe problem to your support organization.

Severity: Error

qeth.d41e42 <bus ID of the qeth device>: CompletionQueueing supported

Explanation: The HiperSockets device supportscompletion queueing. This is required to set upAF_IUCV communication in an LPAR.



qeth.d5b6b3 <bus ID of the qeth device>: Startingoutbound TCP segmentation offload for<network interface name> failed

Explanation: The network adapter supports TCPsegmentation offload, but the qeth device driver couldnot start this support on the adapter.

User response: None if you do not require TCPsegmentation offload. If you want to enable TCPsegmentation offload, ungroup and regroup thesubchannel triplet of the device. If this does not resolvethe problem, reboot Linux. If the problem persists,gather Linux debug data and report the problem toyour support organization.

Severity: Warning

qeth.e73874 <bus ID of the qeth device>: Starting ARPprocessing support for <network interfacename> failed

Explanation: The qeth device driver could not startARP support on the network adapter.


Severity: Warning

qeth.eb4e01 <bus ID of the qeth device>: Failed tocreate completion queue

Explanation: The HiperSockets device could not beconfigured with a completion queue. A completionqueue is required to operate AF_IUCV communicationin an LPAR.

User response: i) Investigate if you have the latestfirmware level in place. ii) If the problem persists and

qeth.c13293 • qeth.eb4e01

Chapter 27. qeth 85

is not caused by a version mismatch, contact IBMsupport.

Severity: Error

qeth.ef9329 <bus ID of the qeth device>: A hardwareoperation timed out on the device

Explanation: A hardware operation timed out on theqeth device.

User response: Check the status of the qeth device, forexample, with the lsqeth command. If the device is notoperational, initiate a recovery process, for example, bywriting '1' to the 'recover' sysfs attribute of the device.

Severity: Warning

qeth.f56315 <bus ID of the qeth device>: The link forinterface <network interface name> onCHPID 0x<CHPID> failed

Explanation: A network link failed. A possible reasonfor this error is that a physical network cable has beendisconnected.

User response: Ensure that the network cable on theadapter hardware is connected properly. If theconnection is to a guest LAN, ensure that the device isstill coupled to the guest LAN.

Severity: Warning

qeth.f6c89f <bus ID of the qeth device>: Enabling thepassthrough mode for <network interfacename> failed

Explanation: The qeth device driver could not enablethe passthrough mode on the network adapter. Thepassthrough mode is required for all network trafficother than IPv4. In particular, the passthrough mode isrequired for IPv6 traffic.

User response: None if all you want to support isIPv4 communication. If you want to support IPv6 orother network traffic apart from IPv4, ungroup andregroup the subchannel triplet of the device. If thisdoes not resolve the problem, reboot Linux. If theproblem persists, gather Linux debug data and reportthe problem to your support organization.

Severity: Warning

qeth.f823af <bus ID of the qeth device>: QDIOreported an error, rc=<return code>

Explanation: The QDIO subsystem reported an error.

User response: Check for related QDIO errors. Checkthe status of the qeth device, for example, with thelsqeth command. If the device is not operational,initiate a recovery process, for example, by writing '1'to the 'recover' sysfs attribute of the device.

Severity: Warning

qeth.faf3f3 <bus ID of the qeth device>: Startingsource MAC-address support for<network interface name> failed

Explanation: The qeth device driver could not enablesource MAC-address on the network adapter.


Severity: Warning

qeth.fce5bf <bus ID of the qeth device>: Setting upbroadcast filtering for <network interfacename> failed

Explanation: The qeth device driver could not set upbroadcast filtering on the network adapter.


Severity: Warning

qeth.fd0b7c <bus ID of the qeth device>: A recoveryprocess has been started for the device

Explanation: A recovery process was started either bythe qeth device driver or through a user command.


Severity: Warning

qeth.ef9329 • qeth.fd0b7c


Chapter 28. s390dbf

Messages with a prefix s390dbf are issued by theS/390 debug feature.

s390dbf.2d934d Root becomes the owner of alls390dbf files in sysfs

Explanation: The S/390 debug feature you are usingonly supports uid/gid = 0.


Severity: Warning

s390dbf.8e20d2 Flushing debug data failed because<debug area number> is not a valid area

Explanation: Flushing a debug area by using the'flush' sysfs attribute failed. Valid values are the minussign (-) for flushing all areas, or the number of therespective area for flushing a single area.

User response: Write a valid area number or theminus sign (-) to the 'flush' sysfs attribute.


s390dbf.a1b9ad Registering view <feature name>/<viewname> would exceed the maximumnumber of views <maximum>

Explanation: The maximum number of allowed debugfeature views has been reached. The view has not beenregistered. The system keeps running but the new viewwill not be available in sysfs. This is a program error.

User response: Report this problem to your supportpartner.

Severity: Error

s390dbf.ac1eb1 Registering debug feature <featurename> failed

Explanation: The initialization of an S/390 debugfeature failed. A likely cause of this problem is memoryconstraints. The system keeps running, but the debugdata for this feature will not be available in sysfs.

User response: Consider assigning more memory toyour LPAR or z/VM guest virtual machine.

Severity: Error

s390dbf.d8734b Allocating memory for <number ofpages> pages failed

Explanation: Setting the debug feature size by usingthe 'page' sysfs attribute failed. Linux did not have

enough memory for expanding the debug feature to therequested size.

User response: Use a smaller number of pages for thedebug feature or allocate more memory to your LPARor z/VM guest virtual machine.


s390dbf.ee54db <level> is not a valid level for adebug feature

Explanation: Setting a new level for a debug featureby using the 'level' sysfs attribute failed. Valid levelsare the minus sign (-) and the integers in the range 0 to6. The minus sign switches off the feature. Thenumbers switch the feature on, where higher numbersproduce more debug output.

User response: Write a valid value to the 'level' sysfsattribute.

Severity: Warning



Chapter 29. sclp_cmd

Messages with a prefix sclp_cmd are issued in thecontext of SCLP commands.

sclp_cmd.c01fec Memory hotplug state changed,suspend refused.

Explanation: Suspend is refused after a memoryhotplug operation was performed.

User response: The system needs to be restarted andno memory hotplug operation must be performed inorder to allow suspend.

Severity: Error



Chapter 30. sclp_config

Messages with a prefix sclp_config are issued bySCLP configuration management events.

sclp_config.12c7a1 CPU capability may have changed

Explanation: The capability of the CPUs in theconfiguration may have been upgraded ordowngraded. This message may also appear if thecapability of the CPUs in the configuration did notchange. For details see the STORE SYSTEMINFORMATION description in the "Principles ofOperation."

User response: The user can examine /proc/sysinfofor CPU capability values.




Chapter 31. scm_block

Messages with a prefix scm_block are issued bythe storage-class memory (SCM) device driver.

scm_block.1ab3e5 An I/O operation to SCM failedwith rc=<return code>

Explanation: An error occurred during I/O to storageclass memory (SCM). The operation was repeated, butthe maximum number of retries was exceeded beforethe request could be fulfilled.


Severity: Error

scm_block.5ab56e <start address of the SCM increment>:The capabilities of the SCM incrementchanged

Explanation: A configuration change is in progress forthe storage class memory (SCM) increment.

User response: Verify that the capability of the SCMincrement is as intended; for example, with lsscm.


scm_block.81e66f <start address of the SCM increment>:Write access to the SCM increment isrestored

Explanation: Write access to the storage class memory(SCM) increment was restored after a temporarysuspension during a concurrent firmware upgrade.



scm_block.93981a <start address of the SCM increment>:Write access to the SCM increment issuspended

Explanation: A concurrent firmware upgrade is inprogress. For the duration of the upgrade, write accessto the storage class memory (SCM) increment has beensuspended.





Chapter 32. setup

Messages with a prefix “setup ” are issued whenLinux starts.

setup.0471f6 crashkernel reservation failed: <reasonstring>

Explanation: The memory reservation for the kdump"crashkernel" parameter was not successful. The Linuxkernel was either not able to find a free memory areaor an invalid area has been defined. The reason stringdescribes the cause of the failure in more detail.

User response: Increase the memory footprint of yourvirtual machine or adjust the values for the"crashkernel" kernel parameter. Then boot your Linuxsystem again.


setup.0713cd Address spaces switched, mvcos notavailable

Explanation: The kernel parameter 'switch_amode' hasbeen specified. The kernel will use the primary addressspace for user space processes and the home addressspace for the kernel. The mvcos instruction is notavailable and the kernel will use the slower page tablewalk method to copy between the user and kerneladdress space.



setup.0961dd Linux is running as a z/VM guestoperating system in 31-bit mode

Explanation: The 31-bit Linux kernel detected that it isrunning as a guest operating system of the z/VMhypervisor.



setup.0cb929 Address spaces switched, mvcosavailable

Explanation: The kernel parameter 'switch_amode' hasbeen specified. The kernel will use the primary addressspace for user space processes and the home addressspace for the kernel. The mvcos instruction is used tocopy between the user and kernel address space.



setup.1a06a7 Linux is running as a z/VM guestoperating system in 64-bit mode

Explanation: The 64-bit Linux kernel detected that it isrunning as a guest operating system of the z/VMhypervisor.



setup.262f23 The hardware system has IEEEcompatible floating point units

Explanation: The Linux kernel detected that it isrunning on a hardware system with CPUs that haveIEEE compatible floating point units.



setup.6bac7a Linux is running natively in 64-bit mode

Explanation: The 64-bit Linux kernel detected that it isrunning on an IBM mainframe, either as the soleoperating system in an LPAR or as the sole operatingsystem on the entire mainframe. The Linux kernel isnot running as a guest operating system of the z/VMhypervisor.



setup.904d83 initrd extends beyond end of memory(0x<start address of the initial RAM disk> >0x<memory end address>) disabling initrd

Explanation: The load address and the size of theinitial RAM disk result in an end address of the initialRAM disk that is beyond the end of the systemmemory.

User response: Lower the load address of the initialRAM disk, reduce the size of the initial RAM disk, orincrease the size of the system memory to make theinitial RAM disk fit into the memory.

Severity: Error

setup.9d71f8 The hardware system has no IEEEcompatible floating point units

Explanation: The Linux kernel detected that it isrunning on a hardware system with CPUs that do nothave IEEE compatible floating point units.




setup.d5d221 Saving the Linux kernel NSS failedwith rc=<return code>

Explanation: The Linux kernel could not save thenamed saved system (NSS) with the z/VM CPSAVESYS command. The return code represents thenumeric portion of the CP SAVESYS error message.

User response: For return code 1, the z/VM guestvirtual machine is not authorized to save named savedsystems. Ensure that the z/VM guest virtual machine isauthorized to issue the CP SAVESYS command(typically privilege class E). For other return codes, seethe help and message documentation for the CPSAVESYS command.

Severity: Error

setup.dae2e8 Reserving <amount of reserved memory> ofmemory at <storage location of reservedmemory> for crashkernel (System RAM:<amount of system RAM>)

Explanation: The memory reservation for the kdump"crashkernel" parameter was successful and a kdumpkernel can now be loaded with the kexec tool.



setup.db58c7 Linux is running natively in 31-bit mode

Explanation: The 31-bit Linux kernel detected that it isrunning on an IBM mainframe, either as the soleoperating system in an LPAR or as the sole operatingsystem on the entire mainframe. The Linux kernel isnot running as a guest operating system of the z/VMhypervisor.



setup.df70d5 Defining the Linux kernel NSS failedwith rc=<return code>

Explanation: The Linux kernel could not define thenamed saved system (NSS) with the z/VM CP DEFSYScommand. The return code represents the numericportion of the CP DEFSYS error message.

User response: For return code 1, the z/VM guestvirtual machine is not authorized to define namedsaved systems. Ensure that the z/VM guest virtualmachine is authorized to issue the CP DEFSYScommand (typically privilege class E). For other returncodes, see the help and message documentation for theCP DEFSYS command.

Severity: Error

setup.f47455 Moving initrd (0x<old start address of theinitial RAM disk> -> 0x<new start addressof the initial RAM disk>, size: <size of theinitial RAM disk>)

Explanation: The location of the initial RAM diskconflicted with the boot memory bitmap. To resolve theconflict the initial RAM disk has been moved to a newlocation.



setup.d5d221 • setup.f47455


Chapter 33. tape

Messages with a prefix “tape ” are issued by thechannel-attached tape device driver.

tape.8ce1c3 <bus ID of the tape device>: The tapecartridge has been successfullyunloaded

Explanation: The tape cartridge has been unloadedfrom the tape unit. Insert a tape cartridge beforeaccessing the tape device.



tape.aaef3e <bus ID of the tape device>: A tape unitwas detached while in use

Explanation: A tape unit has been detached from theI/O configuration while a tape was being accessed.This typically results in I/O error messages andpotentially in damaged data on the tape.

User response: Check the output of the applicationthat accesses the tape device. If this problem occurredduring a write-type operation, consider repeating theoperation after bringing the tape device back online.

Severity: Warning

tape.bedee0 Tape device <bus ID of the tape device> isbusy, refusing to suspend

Explanation: A request to suspend a tape device beingcurrently in use is rejected.

User response: Terminate applications performingtape operations and then try to suspend the systemagain.

Severity: Error

tape.d10f9d A cartridge is loaded in tape device <busID of the tape device>, refusing to suspend

Explanation: A request to suspend a tape devicecurrently loaded with a cartridge is rejected.

User response: Unload the tape device. Then try tosuspend the system again.

Severity: Error

tape.fbea0c <bus ID of the tape device>: A tapecartridge has been mounted

Explanation: A tape cartridge has been inserted intothe tape unit. The tape in the tape unit is ready to beaccessed.





Chapter 34. tape_34xx

Messages with a prefix tape_34xx are issued bythe channel-attached tape device driver and relateto an IBM 3480 or IBM 3490 magnetic tapesubsystem.

tape_34xx.01b705 <bus ID of the tape device>: The tapeunit is not ready

Explanation: The tape unit is online but not ready.

User response: Turn the ready switch on the tape unitto the ready position and try the operation again.

Severity: Warning

tape_34xx.0a2df0 <bus ID of the tape device>: The tapeinformation states an incorrect length

Explanation: The tape is shorter than stated at thebeginning of the tape data. A possible reason for thisproblem is that the tape might have been physicallytruncated. Data written to the tape might be incompleteor damaged.

User response: If this problem occurred during awrite-type operation, consider repeating the operationwith a different tape cartridge.

Severity: Warning

tape_34xx.0dcb6e <bus ID of the tape device>: A parityerror occurred on the tape bus

Explanation: A data parity check error occurred onthe bus. Data that was read or written while the erroroccurred is not valid.

User response: Reposition the tape and repeat theread-type or write-type operation.

Severity: Warning

tape_34xx.1438e6 <bus ID of the tape device>: A channelinterface error cannot be recovered

Explanation: An error has occurred on the channelinterface. This error cannot be recovered by the controlunit error recovery process.

User response: See the documentation of the controlunit.

Severity: Warning

tape_34xx.150bb7 <bus ID of the tape device>: The tapeunit does not support tape format 3480-2XF

Explanation: The tape unit does not support tapes

recorded in the 3480-2 XF format.

User response: If you do not need the data recordedon the current tape, rewind the tape and overwrite itwith a supported format. If you need the data on thecurrent tape, use a tape unit that supports the tapeformat.

Severity: Warning

tape_34xx.15d49e <bus ID of the tape device>: Themaximum block size for buffered modeis exceeded

Explanation: The block to be written is larger thanallowed for the buffered mode.

User response: Use a smaller block size.

Severity: Warning

tape_34xx.257c56 <bus ID of the tape device>: A pathequipment check occurred for the tapedevice

Explanation: A path equipment check has occurred.This check indicates problems with the connectionbetween the mainframe system and the tape controlunit.

User response: Ensure that the cable connectionsbetween the mainframe system and the control unit aresecurely in place and not damaged.

Severity: Warning

tape_34xx.2caadc <bus ID of the tape device>: I/O errorrecovery failed on the tape control unit

Explanation: An I/O error occurred that cannot berecovered by the automatic error recovery process ofthe tape control unit. The application that operates thetape unit will receive a return value of -EIO whichindicates an I/O error. The data on the tape might bedamaged.

User response: If this problem occurred during awrite-type operation, consider repositioning the tapeand repeating the operation.

Severity: Warning

tape_34xx.33278e <bus ID of the tape device>: A writeerror on the tape cannot be recovered

Explanation: A write error has occurred that could notbe recovered by the automatic error recovery process.

User response: Use a different tape cartridge.


Severity: Warning

tape_34xx.3be0ed <bus ID of the tape device>: Readingthe tape beyond the end of the recordedarea failed

Explanation: A read-type operation failed because itextended beyond the end of the recorded area on thetape medium.


Severity: Warning

tape_34xx.3f2d36 <bus ID of the tape device>: The tapeunit does not support format 3480 XF

Explanation: The tape unit does not support tapesrecorded in the 3480 XF format.

User response: If you do not need the data recordedon the current tape, rewind the tape and overwrite itwith a supported format. If you need the data on thecurrent tape, use a tape unit that supports the tapeformat.

Severity: Warning

tape_34xx.3f38f7 <bus ID of the tape device>: A dataoverrun occurred between the controlunit and tape unit

Explanation: A data overrun error has occurred on theconnection between the control unit and the tape unit.If this problem occurred during a write-type operation,the integrity of the data on the tape might becompromised.

User response: Use a faster connection. If this problemoccurred during a write-type operation, considerrepositioning the tape and repeating the operation.

Severity: Warning

tape_34xx.442701 <bus ID of the tape device>: The tapeunit does not support the tape length

Explanation: The length of the tape in the cartridge isincompatible with the tape unit.

User response: Either use a different tape unit or usea tape with a supported length.

Severity: Warning

tape_34xx.553e40 <bus ID of the tape device>: Writingthe ID-mark failed

Explanation: The ID-mark at the beginning of tapecould not be written. The tape medium might bewrite-protected.

User response: Try a different tape cartridge. Ensurethat the write-protection on the cartridge is switchedoff.

Severity: Warning

tape_34xx.633cc6 <bus ID of the tape device>: The tapeunit requires a firmware update

Explanation: The tape unit requires firmware patchesfrom the tape control unit but the required patches arenot available on the control unit.

User response: Make the require patches available onthe control unit then reposition the tape and retry theoperation. For details about obtaining and installingfirmware updates see the control unit documentation.

Severity: Warning

tape_34xx.64dd87 <bus ID of the tape device>: The tapemedium has been rewound or unloadedmanually

Explanation: The tape unit rewind button, unloadbutton, or both have been used to rewind or unload thetape cartridge. A tape cartridge other than the intendedcartridge might have been inserted or the tape mediummight not be at the expected position.

User response: Verify that the correct tape cartridgehas been inserted and that the tape medium is at therequired position before continuing to work with thetape.

Severity: Warning

tape_34xx.696dc8 <bus ID of the tape device>: The tapemedium is write-protected

Explanation: A write-type operation failed because thetape medium is write-protected.

User response: Eject the tape cartridge, switch off thewrite protection on the cartridge, insert the cartridge,and try the operation again.

Severity: Warning

tape_34xx.69f60e <bus ID of the tape device>: The tapeunit does not support the current tapelength

Explanation: The length of the tape in the cartridge isincompatible with the tape unit.

User response: Either use a different tape unit or usea tape with a supported length.

Severity: Warning

tape_34xx.6bcece <bus ID of the tape device>: The tapeunit is already assigned

Explanation: The tape unit is already assigned toanother channel path.

User response: Free the tape unit from the operating

tape_34xx.3be0ed • tape_34xx.6bcece


system instance to which it is currently assigned thentry again.

Severity: Warning

tape_34xx.7f9ae4 <bus ID of the tape device>: A channelprotocol error occurred

Explanation: An error was detected in the channelprotocol.

User response: Reposition the tape and try theoperation again.

Severity: Warning

tape_34xx.85efa7 <bus ID of the tape device>: The blockID sequence on the tape is incorrect

Explanation: The control unit has detected anincorrect block ID sequence on the tape. This problemtypically indicates that the data on the tape isdamaged.

User response: If this problem occurred during awrite-type operation reposition the tape and repeat theoperation.

Severity: Warning

tape_34xx.956e53 <bus ID of the tape device>: The tapedoes not have the required tape tension

Explanation: The tape does not have the required tapetension.

User response: Rewind and reposition the tape, thenrepeat the operation.

Severity: Warning

tape_34xx.b334e9 <bus ID of the tape device>: The tapeunit is not online

Explanation: The tape unit is not online to the tapedevice driver.

User response: Ensure that the tape unit is operationaland that the cable connections between the control unitand the tape unit are securely in place and notdamaged.

Severity: Warning

tape_34xx.c5ee4a <bus ID of the tape device>: Automaticunloading of the tape cartridge failed

Explanation: The tape unit failed to unload thecartridge.

User response: Unload the cartridge manually byusing the eject button on the tape unit.

Severity: Warning

tape_34xx.c7fc10 <bus ID of the tape device>: The tapeunit does not support the compactionalgorithm

Explanation: The tape unit cannot read the currenttape. The data on the tape has been compressed withan algorithm that is not supported by the tape unit.

User response: Use a tape unit that supports thecompaction algorithm used for the current tape.

Severity: Warning

tape_34xx.ccc5ad <bus ID of the tape device>: The tapeunit failed to load the cartridge

Explanation: An error has occurred while loading thetape cartridge.

User response: Unload the cartridge and load it again.

Severity: Warning

tape_34xx.cfc6c4 <bus ID of the tape device>: Anequipment check has occurred on thetape unit

Explanation: Possible reasons for the check conditionare a unit adapter error, a buffer error on the lowerinterface, an unusable internal path, or an error thathas occurred while loading the cartridge.

User response: Examine the tape unit and thecartridge loader. Consult the tape unit documentationfor details.

Severity: Warning

tape_34xx.d2b071 <bus ID of the tape device>: A readerror occurred that cannot be recovered

Explanation: A read error has occurred that cannot berecovered. The current tape might be damaged.


Severity: Warning

tape_34xx.d56330 <bus ID of the tape device>: The tapecontains an incorrect block ID sequence

Explanation: The control unit has detected anincorrect block ID sequence on the tape. This problemtypically indicates that the data on the tape isdamaged.

User response: If this problem occurred during awrite-type operation reposition the tape and repeat theoperation.

Severity: Warning

tape_34xx.7f9ae4 • tape_34xx.d56330

Chapter 34. tape_34xx 101

tape_34xx.d608a6 <bus ID of the tape device>: Thecontrol unit has fenced access to thetape volume

Explanation: The control unit fences further access tothe current tape volume. The data integrity on the tapevolume might have been compromised.

User response: Rewind and unload the tape cartridge.

Severity: Warning

tape_34xx.e473c9 <bus ID of the tape device>: The tapesubsystem is running in degraded mode

Explanation: The tape subsystem is not operating atits maximum performance.

User response: Contact your service representative forthe tape unit and report this problem.

Severity: Warning

tape_34xx.e96040 <bus ID of the tape device>: The tapeunit cannot process the tape format

Explanation: Either the tape unit is not able to readthe format ID mark, or the specified format is notsupported by the tape unit.

User response: If you do not need the data recordedon the current tape, use a different tape or write a newformat ID mark at the beginning of the tape. Be awarethat writing a new ID mark leads to a loss of all datathat has been recorded on the tape. If you need thedata on the current tape, use a tape unit that supportsthe tape format.

Severity: Warning

tape_34xx.f06a05 <bus ID of the tape device>: Anunexpected condition <number> occurredin tape error recovery

Explanation: The control unit has reported an errorcondition that is not recognized by the error recoveryprocess of the tape device driver.

User response: Report this problem and the conditionnumber from the message to your supportorganization.

Severity: Error

tape_34xx.d608a6 • tape_34xx.f06a05


Chapter 35. tape_3590

Messages with a prefix tape_3590 are issued bythe channel-attached tape device driver and relateto an IBM 3590 or IBM 3592 magnetic tapesubsystem.

tape_3590.07e630 <bus ID of the tape device>: DEVSIMSEV=<SEV>, DEVTYPE=3590/<model>,MC=<message code>, ES=<exception>/<required service action>,REF=0x<refcode1>-0x<refcode2>-0x<refcode3>

Explanation: This is an operating system independentdevice subsystem information message issued by thetape unit. The information in the message is intendedfor the IBM customer engineer.

User response: See the documentation for the tapeunit for further information.

Severity: Warning

tape_3590.18dc29 <bus ID of the tape device>: The tapemedium must be loaded into a differenttape unit

Explanation: The tape device has indicated an errorcondition that requires loading the tape cartridge into adifferent tape unit to recover.

User response: Unload the cartridge and use adifferent tape unit to retry the operation.

Severity: Warning

tape_3590.3c5600 <bus ID of the tape device>: I/Osubsystem information: exception<exception>, service <required serviceaction>

Explanation: This is an operating system independentI/O subsystem information message that was issued bythe tape unit. The information in the message isintended for the IBM customer engineer.


Severity: Warning

tape_3590.3f6a17 <bus ID of the tape device>: IOSIMSEV=<SEV>, DEVTYPE=3590/<model>,MC=<message code>, ES=<exception>/<required service action>,REF=0x<refcode1>-0x<refcode2>-0x<refcode3>

Explanation: This is an operating system independent

I/O subsystem information message that was issued bythe tape unit. The information in the message isintended for the IBM customer engineer.


Severity: Warning

tape_3590.497827 <bus ID of the tape device>: The tapeunit failed to obtain the encryption keyfrom EKM

Explanation: The tape unit was unable to retrieve theencryption key required to decode the data on the tapefrom the enterprise key manager (EKM).

User response: See the EKM and tape unitdocumentation for information about how to enable thetape unit to retrieve the encryption key.

Severity: Error

tape_3590.4b2253 <bus ID of the tape device>: Devicesubsystem information: exception<exception>, service <required serviceaction>

Explanation: This is an operating system independentdevice subsystem information message that was issuedby the tape unit. The information in the message isintended for the IBM customer engineer.


Severity: Warning

tape_3590.575a6b <bus ID of the tape device>: The tapeunit has issued sense message <sensemessage code>

Explanation: The tape unit has issued an operatingsystem independent sense message.


Severity: Warning

tape_3590.601044 <bus ID of the tape device>: The tapeunit has issued an unknown sensemessage code 0x<code>

Explanation: The tape device driver has received anunknown sense message from the tape unit.



Severity: Warning

tape_3590.7ad0ac <bus ID of the tape device>: MIMSEV=<SEV>, MC=<message code>,ES=<exception>/<required service action>,RC=<refcode>-<mid>-<fid>

Explanation: This is an operating system independentinformation message that was issued by the tape unit.The information in the message is intended for the IBMcustomer engineer.

User response: See to the documentation for the tapeunit for further information.

Severity: Warning

tape_3590.991401 <bus ID of the tape device>: Tapemedia information: exception<exception>, service <service>

Explanation: This is an operating system independenttape medium information message that was issued bythe tape unit. The information in the message isintended for the IBM customer engineer.


Severity: Warning

tape_3590.fca498 <bus ID of the tape device>: Adifferent host has privileged access tothe tape unit

Explanation: You cannot access the tape unit becausea different operating system instance has privilegedaccess to the unit.

User response: Unload the current cartridge to solvethis problem.

Severity: Warning

tape_3590.ff1db8 <bus ID of the tape device>: The tapeunit has issued an unknown sensemessage code <code>

Explanation: The tape device has issued a sensemessage, that is unknown to the device driver.

User response: Use the message code printed ashexadecimal value and see the documentation for thetape unit for further information.

Severity: Warning

tape_3590.7ad0ac • tape_3590.ff1db8


Chapter 36. time

Messages with a prefix “time ” are issued by theSystem z specific time functions.

time.93fc64 The real or virtual hardware systemdoes not provide an STP interface

Explanation: The 'stp=' parameter has been passed onthe kernel parameter line for a Linux instance that doesnot have access to the server time protocol (STP)facility.

User response: To avoid this warning remove the'stp=' kernel parameter.

Severity: Warning

time.c4bd65 The real or virtual hardware systemdoes not provide an ETR interface

Explanation: The 'etr=' parameter has been passed onthe kernel parameter line for a Linux instance that doesnot have access to the external time reference (ETR)facility.

User response: To avoid this warning remove the'etr=' kernel parameter.

Severity: Warning

time.eb7580 The ETR interface has adjusted theclock by <number of microseconds>microseconds

Explanation: The external time reference (ETR)interface has synchronized the system clock with theexternal reference and set it to a new value. The timedifference between the old and new clock value hasbeen passed to the network time protocol (NTP) as asingle shot adjustment.


Severity: Notice



Chapter 37. vmlogrdr

Messages with a prefix vmlogrdr are issued bythe z/VM recording device driver. With thez/VM recording device driver, an instance ofLinux on z/VM can read from the z/VM CPrecording services.

vmlogrdr.c1d147 vmlogrdr: device <device name> isbusy. Refuse to suspend.

Explanation: Suspending vmlogrdr devices that are inuses is not supported. A request to suspend such adevice is refused.

User response: Close all applications that use any ofthe vmlogrdr devices and then try to suspend thesystem again.

Severity: Error



Chapter 38. vmur

Messages with a prefix vmur are issued by thez/VM virtual unit record device driver. Thisdevice driver provides Linux with access toz/VM virtual unit record devices like punch cardreaders, card punches, and line printers.

vmur.386675 Unit record device <bus ID of the unitrecord device> is busy, <z/VM virtual unitrecord device driver> refusing to suspend.

Explanation: Linux cannot be suspended while a unitrecord device is in use.

User response: Stop all applications that work onz/VM spool file queues, for example, the vmur tool.Then try again to suspend Linux.

Severity: Error

vmur.53bf56 The <z/VM virtual unit record devicedriver> cannot be loaded without z/VM

Explanation: The z/VM virtual unit record devicedriver provides Linux with access to z/VM virtual unitrecord devices like punch card readers, card punches,and line printers. On Linux instances that run inenvironments other than the z/VM hypervisor, thedevice driver does not provide any useful function andthe corresponding vmur module cannot be loaded.

User response: Load the vmur module only on Linuxinstances that run as guest operating systems of thez/VM hypervisor. If the z/VM virtual unit recorddevice has been compiled into the kernel, ignore thismessage.

Severity: Error

vmur.ff8847 Kernel function alloc_chrdev_regionfailed with error code <error codeaccording to errno definitions>

Explanation: The z/VM virtual unit record devicedriver (vmur) needs to register a range of characterdevice minor numbers from 0x0000 to 0xffff. Thisregistration failed, probably because of memoryconstraints.

User response: Free some memory and reload thevmur module. If the z/VM virtual unit record devicedriver has been compiled into the kernel reboot Linux.Consider assigning more memory to your LPAR orz/VM guest virtual machine.

Severity: Error



Chapter 39. vmwatchdog

Messages with a prefix vmwatchdog are issuedby the watchdog device driver. With thewatchdog device driver, a watchdog applicationon an instance of Linux on z/VM can access thez/VM watchdog timer.

vmwatchdog.8f03fb The system cannot be suspendedwhile the watchdog is running

Explanation: The watchdog must not time out duringhibernation. The watchdog device driver prevents thesystem from being suspended while the watchdogtimer is running.

User response: If you want to suspend the system,stop the watchdog, for example, by entering thecommand: 'echo V > /dev/vmwatchdog'. Alternatively,stop the program that uses the watchdog or reconfigurethe program to not use the watchdog.

Severity: Error

vmwatchdog.bfeb9c The system cannot besuspended while the watchdog is in use

Explanation: A program is currently using thevmwatchdog device node. The watchdog device driverprevents the system from being suspended while thewatchdog device is in use.

User response: If you want to suspend the system,find out which program uses the watchdog device.Stop the program or reconfigure it to not use thewatchdog.

Severity: Error



Chapter 40. xpram

Messages with a prefix xpram are issued by theXPRAM device driver. This block device driverenables Linux on System z to access expandedstorage.

xpram.9f7762 Resuming the system failed: <cause ofthe failure>

Explanation: A system cannot be resumed if theexpanded memory setup changes after hibernation.Possible reasons for the failure are: - Expanded memorywas removed after hibernation. - Size of the expandedmemory changed after hibernation. The system isstopped with a kernel panic.

User response: Reboot Linux.

Severity: Error

xpram.ab9aa4 <number of partitions> is not a validnumber of XPRAM devices

Explanation: The number of XPRAM partitionsspecified for the 'devs' module parameter or with the'xpram.parts' kernel parameter must be an integer inthe range 1 to 32. The XPRAM device driver created amaximum of 32 partitions that are probably notconfigured as intended.

User response: If the XPRAM device driver has beencompiled as a separate module, unload the module andload it again with a correct value for the 'devs' moduleparameter. If the XPRAM device driver has beencompiled into the kernel, correct the 'xpram.parts'parameter in the kernel command line and restartLinux.

Severity: Error

xpram.f004d1 Not enough expanded memoryavailable

Explanation: The amount of expanded memoryrequired to set up your XPRAM partitions depends onthe 'sizes' parameter specified for the xpram module oron the specifications for the 'xpram.parts' parameter ifthe XPRAM device driver has been compiled into thekernel. Your current specification exceed the amount ofavailable expanded memory. Your XPRAM partitionsare probably not configured as intended.

User response: If the XPRAM device driver has beencompiled as a separate module, unload the xprammodule and load it again with an appropriate value forthe 'sizes' module parameter. If the XPRAM devicedriver has been compiled into the kernel, adjust the'xpram.parts' parameter in the kernel command line

and restart Linux. If you need more than the availableexpanded memory, increase the expanded memoryallocation for your virtual hardware or LPAR.

Severity: Error

xpram.f6ae78 No expanded memory available

Explanation: The XPRAM device driver has beenloaded in a Linux instance that runs in an LPAR orvirtual hardware without expanded memory. NoXPRAM partitions are created.

User response: Allocate expanded memory for yourLPAR or virtual hardware or do not load the xprammodule. You can ignore this message, if you do notwant to create XPRAM partitions.

Severity: Error



Chapter 41. zdump

Messages with a prefix zdump are issued by thezfcpdump functions.

zdump.54a0dd The 32-bit dump tool cannot be usedfor a 64-bit system

Explanation: The dump process ends without creatinga system dump.

User response: Use a 64-bit dump tool to obtain asystem dump for 64-bit Linux instance.

Severity: Alert

zdump.d05784 The 64-bit dump tool cannot be usedfor a 32-bit system

Explanation: The dump process ends without creatinga system dump.

User response: Use a 32-bit dump tool to obtain asystem dump for 32-bit Linux instance.

Severity: Alert



Chapter 42. zfcp

Messages with a prefix zfcp are issued by theSCSI-over-Fibre Channel device driver (zfcpdevice driver) for the QDIO-based System zSCSI-over-Fibre Channel adapter. The zfcp devicedriver supports Fibre Channel-attached SCSIdevices on Linux on System z.

zfcp.000866 <bus ID of the zfcp device>: The FCPadapter cannot support more NPIV ports

Explanation: N_Port ID Virtualization (NPIV) portsconsume physical resources on the FCP adapter. TheFCP adapter resources are exhausted. The connection isnot operational.

User response: Analyze the number of available NPIVports and which operating system instances use them.If necessary, reconfigure your setup to move someNPIV ports to an FCP adapter with free resources.

Severity: Warning

zfcp.01a8f2 <bus ID of the zfcp device>: All NPIVports on the FCP adapter have beenassigned

Explanation: The number of N_Port ID Virtualization(NPIV) ports that can be assigned on an FCP adapter islimited. Once assigned, NPIV ports are not releasedautomatically but have to be released explicitly throughthe support element (SE).

User response: Identify NPIV ports that have beenassigned but are no longer in use and release themfrom the SE.

Severity: Warning

zfcp.020115 <bus ID of the zfcp device>: Registeringport 0x<WWPN> failed

Explanation: The Linux kernel could not allocateenough memory to register the remote port with theindicated WWPN with the SCSI stack. The remote portis not available.

User response: Free some memory and trigger therescan for ports.

Severity: Error

zfcp.058803 <bus ID of the zfcp device>: FCP adaptermaximum QTCB size (<maximumsupported size> bytes) is too small

Explanation: The queue transfer control block (QTCB)size requested by the zfcp device driver is notsupported by the FCP adapter hardware.

User response: Update the firmware on your FCPadapter hardware to the latest available level andupdate the Linux kernel to the latest supported level. Ifthe problem persists, contact your support organization.

Severity: Error

zfcp.0cf3fa <bus ID of the zfcp device>: Creating anERP thread for the FCP device failed.

Explanation: The zfcp device driver could not set uperror recovery procedure (ERP) processing for the FCPdevice. The FCP device is not available for use inLinux.

User response: Free some memory and try again toload the zfcp device driver. If the zfcp device driverhas been compiled into the kernel, reboot Linux.Consider assigning more memory to your LPAR orz/VM guest virtual machine. If the problem persists,contact your support organization.

Severity: Error

zfcp.10efb5 <bus ID of the zfcp device>: Opening WKAport 0x<destination ID of the WKA port>failed

Explanation: The FCP adapter rejected a request toopen the specified well-known address (WKA) port. Noretry is possible.

User response: Verify the setup and check if themaximum number of remote ports used through thisadapter is below the maximum allowed. If the problempersists, gather Linux debug data, collect the FCPadapter hardware logs, and report the problem to yoursupport organization.

Severity: Warning

zfcp.128ff1 <bus ID of the zfcp device>: The WWPNassignment file on the FCP adapter hasbeen damaged

Explanation: This is an FCP adapter hardwareproblem.

User response: Report this problem with FCPhardware logs to IBM support.

Severity: Warning

zfcp.19bff2 <bus ID of the zfcp device>: Incorrect CDBlength <value in length field>, LUN0x<LUN> on port 0x<WWPN> closed

Explanation: The control-data-block (CDB) length fieldin a SCSI request is not valid or too large for the FCP


adapter. The zfcp device driver closed down the SCSIdevice at the indicated LUN.

User response: Gather Linux debug data and reportthis problem to your support organization.

Severity: Error

zfcp.219537 <bus ID of the zfcp device>: The fibrechannel fabric does not support NPIV

Explanation: The FCP adapter requires N_Port IDVirtualization (NPIV) from the adjacent fibre channelnode. Either the FCP adapter is connected to a fibrechannel switch that does not support NPIV or the FCPadapter tries to use NPIV in a point-to-point setup. Theconnection is not operational.

User response: Verify that NPIV is correctly used forthis connection. Check the FCP adapter configurationand the fibre channel switch configuration. If necessary,update the fibre channel switch firmware.

Severity: Warning

zfcp.29fa1a <bus ID of the zfcp device>: The adjacentfibre channel node does not supportFCP

Explanation: The fibre channel switch or storagesystem that is connected to the FCP channel does notsupport the fibre channel protocol (FCP). The zfcpdevice driver stopped using the FCP device.

User response: Check the adjacent fibre channel node.

Severity: Warning

zfcp.2a747e <bus ID of the zfcp device>: No handle isavailable for LUN 0x<LUN> on port0x<WWPN>

Explanation: The FCP adapter can only open a limitednumber of SCSI devices. This limit has been reachedand the SCSI device at the indicated LUN cannot beopened.

User response: For FCP subchannels running innon-NPIV mode, check all SCSI devices openedthrough the FCP adapter and close some of them. ForFCP subchannels running in NPIV mode, verify theSAN zoning and host connections on the storagesystems. Ensure that the zoning and host connectionsonly allow access to the required LUNs. As aworkaround, disable the automatic LUN scanning bysetting the zfcp.allow_lun_scan kernel parameter or theallow_lun_scan module parameter to 0.

Severity: Warning

zfcp.2c93b9 <bus ID of the zfcp device>: The FCPadapter only supports older controlblock versions

Explanation: The protocol supported by the FCPadapter is not compatible with the zfcp device driver.

User response: Install the latest firmware on your FCPadapter.

Severity: Error

zfcp.306272 <bus ID of the zfcp device>: The FCPadapter reported a problem that cannotbe recovered

Explanation: The FCP adapter has a problem thatcannot be recovered by the zfcp device driver. The zfcpdevice driver stopped using the FCP device.

User response: Gather Linux debug data, collect theFCP adapter hardware logs, and report this problem toyour support organization.

Severity: Error

zfcp.307c0c <bus ID of the zfcp device>: FCP devicenot operational because of anunsupported FC class

Explanation: The FCP adapter hardware does notsupport the fibre channel service class requested by thezfcp device driver. This problem indicates a programerror in the zfcp device driver.


Severity: Error

zfcp.308f45 <bus ID of the zfcp device>: The modetable on the FCP adapter has beendamaged

Explanation: This is an FCP adapter hardwareproblem.

User response: Report this problem with FCPhardware logs to IBM support.

Severity: Warning

zfcp.3dff9c <bus ID of the zfcp device>: Setting up theQDIO connection to the FCP adapterfailed

Explanation: The zfcp device driver failed to establisha QDIO connection with the FCP adapter.

User response: Set the FCP adapter offline or detach itfrom the Linux system, free some memory and set theFCP adapter online again or attach it again. If thisproblem persists, gather Linux debug data, collect the

zfcp.219537 • zfcp.3dff9c


FCP adapter hardware logs, and report the problem toyour support organization.

Severity: Error

zfcp.4a463f <bus ID of the zfcp device>: ERP failed forremote port 0x<WWPN>

Explanation: An error occurred on a remote port. Theerror recovery procedure (ERP) could not resolve theerror. The port is not available.

User response: Verify that the WWPN is correct andcheck the fibre channel fabric for errors related to theWWPN.

Severity: Error

zfcp.4c0e02 <bus ID of the zfcp device>: The FCPadapter does not recognize thecommand 0x<command>

Explanation: A command code that was sent from thezfcp device driver to the FCP adapter is not valid. Thezfcp device driver stopped using the FCP device.


Severity: Error

zfcp.566303 <bus ID of the zfcp device>: The CHPIDfor the FCP device is offline

Explanation: The CHPID for an FCP device has beenset offline, either logically in Linux or on the hardware.

User response: Find out which CHPID corresponds tothe FCP device, for example, with the lscss command.Check if the CHPID has been set logically offline insysfs. Write 'on' to the CHPID's status attribute to set itonline. If the CHPID is online in sysfs, find out if it hasbeen varied offline through a hardware managementinterface, for example the service element (SE).

Severity: Warning

zfcp.56747f <bus ID of the zfcp device>: The adjacentswitch cannot support more NPIV ports

Explanation: N_Port ID Virtualization (NPIV) portsconsume physical resources. The resources of the fibrechannel switch that is connected to the FCP adapter areexhausted. The connection is not operational.

User response: Analyze the number of available NPIVports on the adjacent fibre channel switch and howthey are used. If necessary, reconfigure your fibrechannel fabric to accommodate the required NPIVports.

Severity: Warning

zfcp.574d43 <bus ID of the zfcp device>: ERP cannotrecover an error on the FCP device

Explanation: An error occurred on an FCP device. Theerror recovery procedure (ERP) could not resolve theerror. The FCP device driver cannot use the FCP device.

User response: Check for previous error messages forthe same FCP device to find the cause of the problem.

Severity: Error

zfcp.646ca0 <bus ID of the zfcp device>: QTCB version0x<requested version> not supported byFCP adapter (0x<lowest supported version>to 0x<highest supported version>)

Explanation: See message text. The queue transfercontrol block (QTCB) version requested by the zfcpdevice driver is not supported by the FCP adapterhardware.

User response: If the requested version is higher thanthe highest version supported by the hardware, installmore recent firmware on the FCP adapter. If therequested version is lower then the lowest versionsupported by the hardware, upgrade to a Linux levelwith a more recent zfcp device driver.

Severity: Error

zfcp.657cf6 <bus ID of the zfcp device>: Setting updata structures for the FCP adapterfailed

Explanation: The zfcp device driver could not allocatedata structures for an FCP adapter. A possible reasonfor this problem is memory constraints.

User response: Set the FCP adapter offline or detach itfrom the Linux system, free some memory and set theFCP adapter online again or attach it again. If thisproblem persists, gather Linux debug data, collect theFCP adapter hardware logs, and report the problem toyour support organization.

Severity: Error

zfcp.6dbb23 <bus ID of the zfcp device>: Incorrectdirection <value in direction field>, LUN0x<LUN> on port 0x<WWPN> closed

Explanation: The direction field in a SCSI requestcontains an incorrect value. The zfcp device driverclosed down the SCSI device at the indicated LUN.

User response: Gather Linux debug data and reportthis problem to your support organization.

Severity: Error

zfcp.4a463f • zfcp.6dbb23

Chapter 42. zfcp 119

zfcp.7059a3 <bus ID of the zfcp device>: 0x<statusinformation> is not a valid transferprotocol status

Explanation: The transfer protocol status informationreported by the FCP adapter is not a valid status forthe zfcp device driver. The zfcp device driver stoppedusing the FCP device.


Severity: Error

zfcp.747e7d <bus ID of the zfcp device>: LUN 0x<LUN>on port 0x<remote port WWPN> isalready in use by CSS<channel subsystemID>, MIF Image ID <MIF Image ID of theLPAR>

Explanation: The SCSI device at the indicated LUN isalready in use by another system. Only one system at atime can use the SCSI device.

User response: Ensure that the other system stopsusing the device before trying to use it.

Severity: Warning

zfcp.772dc6 <bus ID of the zfcp device>: Unknown orunsupported arbitrated loop fibrechannel topology detected

Explanation: The FCP device is connected to a fibrechannel arbitrated loop or the FCP adapter reported anunknown fibre channel topology. The zfcp devicedriver supports point-to-point connections andswitched fibre channel fabrics but not arbitrated looptopologies. The FCP device cannot be used.

User response: Check the fibre channel setup andensure that only supported topologies are connected tothe FCP adapter.

Severity: Error

zfcp.787564 <bus ID of the zfcp device>: A port openedwith WWPN 0x<expected WWPN>returned data that identifies it asWWPN 0x<reported WWPN>

Explanation: A remote port was opened successfully,but it reported an unexpected WWPN in the returnedport login (PLOGI) data. This condition might havebeen caused by a change applied to the SANconfiguration while the port was being opened.

User response: If this condition is only temporary andaccess to the remote port is possible, no action isrequired. If the condition persists, identify the storagesystem with the specified WWPN and contact thesupport organization of the storage system.

Severity: Warning

zfcp.7d0b42 <bus ID of the zfcp device>: The FCPdevice has been detached

Explanation: An FCP device is no longer available toLinux.

User response: Ensure that the FCP adapter isoperational and attached to the LPAR or z/VM virtualmachine.

Severity: Warning

zfcp.7d6999 <bus ID of the zfcp device>: There is nolight signal from the local fibre channelcable

Explanation: There is no signal on the fibre channelcable that connects the FCP adapter to the fibre channelfabric.

User response: Ensure that the cable is in place andconnected properly to the FCP adapter and to theadjacent fibre channel switch or storage system.

Severity: Warning

zfcp.7f96f9 <bus ID of the zfcp device>: The nameserver reported <number of words inresidual data> words residual data

Explanation: The fibre channel name server sent toomuch information about remote ports. The zfcp devicedriver did not receive sufficient information to attachall available remote ports in the SAN.

User response: Verify that you are running the latestfirmware level on the FCP adapter. Check your SANsetup and consider reducing the number of portsvisible to the FCP adapter by using more restrictivezoning in the SAN.

Severity: Warning

zfcp.82bb71 <bus ID of the zfcp device>: The FCPdevice did not respond within thespecified time

Explanation: The common I/O layer waited for aresponse from the FCP adapter but no response wasreceived within the specified time limit. This mightindicate a hardware problem.

User response: Consult your hardware administrator.If this problem persists, gather Linux debug data,collect the FCP adapter hardware logs, and report theproblem to your support organization.

Severity: Warning

zfcp.7059a3 • zfcp.82bb71


zfcp.87c4d0 <bus ID of the zfcp device>: The errorthreshold for checksum statistics hasbeen exceeded

Explanation: The FCP adapter has reported a largenumber of bit errors. This might indicate a problemwith the physical components of the fibre channelfabric. Details about the errors have been written to theHBA trace for the FCP adapter.

User response: Check for problems in the fibrechannel fabric and ensure that all cables are properlyplugged.

Severity: Warning

zfcp.8bdb34 <bus ID of the zfcp device>: ERP failed forLUN 0x<LUN> on port 0x<WWPN>

Explanation: An error occurred on the SCSI device atthe specified LUN. The error recovery procedure (ERP)could not resolve the error. The SCSI device is notavailable.

User response: Verify that the LUN is correct. Checkthe fibre channel fabric for errors related to thespecified WWPN and LUN, the storage server, andLinux.

Severity: Error

zfcp.9b70c0 <bus ID of the zfcp device>: Not enoughFCP adapter resources to open remoteport 0x<WWPN>

Explanation: Each port that is opened consumesphysical resources of the FCP adapter to which it isattached. These resources are exhausted and thespecified port cannot be opened.

User response: Reduce the total number of remoteports that are attached to the FCP adapter.

Severity: Warning

zfcp.9d2a6b <bus ID of the zfcp device>: There is awrap plug instead of a fibre channelcable

Explanation: The FCP adapter is not physicallyconnected to the fibre channel fabric.

User response: Remove the wrap plug from the FCPadapter and connect the adapter with the fibre channelfabric.

Severity: Warning

zfcp.a9953d <bus ID of the zfcp device>: The FCPdevice is suspended because of afirmware update

Explanation: The FCP device is not available while afirmware update is in progress. This problem is

temporary. The FCP device will resume operationswhen the firmware update is completed.

User response: Wait 10 seconds and try the operationagain.

Severity: Warning

zfcp.ac341f <bus ID of the zfcp device>: The local linkhas been restored

Explanation: A problem with the connection betweenthe FCP adapter and the adjacent node on the fibrechannel fabric has been resolved. The FCP adapter isnow available again.



zfcp.ad5387 <bus ID of the zfcp device>: Registeringthe FCP device with the SCSI stackfailed

Explanation: The FCP adapter could not be registeredwith the Linux SCSI stack. A possible reason for thisproblem is memory constraints.

User response: Set the FCP adapter offline or detach itfrom the Linux system, free some memory and set theFCP adapter online again or attach it again. If thisproblem persists, gather Linux debug data, collect theFCP adapter hardware logs, and report the problem toyour support organization.

Severity: Error

zfcp.afba9a <bus ID of the zfcp device>: The linkbetween the FCP adapter and the FCfabric is down

Explanation: The FCP adapter is not usable. Specificerror information is not available.

User response: Check the cabling and the fibrechannel fabric configuration. If this problem persists,gather Linux debug data, collect the FCP adapterhardware logs, and report the problem to your supportorganization.

Severity: Warning

zfcp.b2d959 The zfcp device driver could not registerwith the common I/O layer

Explanation: The device driver initialization failed. Apossible cause of this problem is memory constraints.

User response: Free some memory and try again toload the zfcp device driver. If the zfcp device driverhas been compiled into the kernel, reboot Linux.Consider assigning more memory to your LPAR orz/VM guest virtual machine. If the problem persists,contact your support organization.

zfcp.87c4d0 • zfcp.b2d959

Chapter 42. zfcp 121

Severity: Error

zfcp.b2ef0a <bus ID of the zfcp device>: The FCPdevice is operational again

Explanation: An FCP device has been unavailablebecause it had been detached from the Linux system orbecause the corresponding CHPID was offline. The FCPdevice is now available again and the zfcp devicedriver resumes all operations to the FCP device.



zfcp.c2c546 <bus ID of the zfcp device>: The FCPadapter could not log in to the fibrechannel fabric

Explanation: The fibre channel switch rejected thelogin request from the FCP adapter.

User response: Check the fibre channel fabric orswitch logs for possible errors.

Severity: Warning

zfcp.cf1c58 <bus ID of the zfcp device>: The QTCBtype is not supported by the FCPadapter

Explanation: The queue transfer control block (QTCB)type requested by the zfcp device driver is notsupported by the FCP adapter hardware.

User response: Install the latest firmware on your FCPadapter hardware. If this does not resolve the problem,upgrade to a Linux level with a more recent zfcpdevice driver. If the problem persists, contact yoursupport organization.

Severity: Error

zfcp.cfb51a <device specification> is not a valid SCSIdevice

Explanation: The specification for an initial SCSIdevice provided with the 'zfcp.device' kernel parameteror with the 'device' module parameter is syntacticallyincorrect. The specified SCSI device could not beattached to the Linux system.

User response: Correct the value for the 'zfcp.device'or 'device' parameter and reboot Linux. See "DeviceDrivers, Features, and Commands" for informationabout the syntax.

Severity: Error

zfcp.d4aea8 <bus ID of the zfcp device>: 0x<request ID>is an ambiguous request identifier

Explanation: The FCP adapter reported that itreceived the same request ID twice. This is an error.The zfcp device driver stopped using the FCP device.


Severity: Error

zfcp.dda2e3 <bus ID of the zfcp device>: The FCPdevice detected a WWPN that isduplicate or not valid

Explanation: This condition indicates an error in theFCP adapter hardware or in the z/VM hypervisor.

User response: Gather Linux debug data, collect theFCP adapter hardware logs, and report this problem toIBM support.

Severity: Warning

zfcp.e78dec <bus ID of the zfcp device>: A QDIOproblem occurred

Explanation: QDIO reported a problem to the zfcpdevice driver. The zfcp device driver tries to recoverthis problem.

User response: Check for related error messages. Ifthis problem occurs frequently, gather Linux debugdata and contact your support organization.

Severity: Warning

zfcp.f16820 <bus ID of the zfcp device>: The FCPadapter only supports newer controlblock versions

Explanation: The protocol supported by the FCPadapter is not compatible with the zfcp device driver.

User response: Upgrade your Linux kernel to a levelthat includes a zfcp device driver with support for thecontrol block version required by your FCP adapter.

Severity: Error

zfcp.b2ef0a • zfcp.f16820


Chapter 43. zpci

Messages with a prefix zpci are issued by thekernel module that provides PCIe support.

zpci.1bc6a2 <device name of the function>: Event0x<PCI event code> reconfigured PCIfunction 0x<function ID>

Explanation: The availability of a PCI function haschanged. Possible reasons for the change include PCIconfiguration actions on the Hardware ManagementConsole or hypervisor. For shared PCI functions, thefunction might also have been reserved or released byanother system. If the device name of a function isshown as 'n/a', the device registration with the PCIdevice driver has not completed. The function IDidentifies the function to the I/O configuration(IOCDS). The PCI event code can be useful diagnosticinformation for your support organization.



zpci.9b6a12 <device name of the function>: Event0x<PCI event code> reports an error forPCI function 0x<function ID>

Explanation: A PCI function entered an error statefrom which it cannot recover automatically.

User response: Trigger a recovery action by writing '1'to the 'recovery' sysfs attribute of the PCI function. Insysfs, PCI functions are represented as/sys/bus/pci/devices/<name>, where <name> is thedevice name of the function. If the problem persists,contact your support organization.

Severity: Error



Accessibility

Accessibility features help users who have a disability, such as restricted mobilityor limited vision, to use information technology products successfully.

Documentation accessibility

The Linux on System z publications are in Adobe Portable Document Format(PDF) and should be compliant with accessibility standards. If you experiencedifficulties when you use the PDF file and want to request a Web-based format forthis publication, use the Readers' Comments form in the back of this publication,send an email to [email protected], or write to:

IBM Deutschland Research & Development GmbHInformation DevelopmentDepartment 3282Schoenaicher Strasse 22071032 BoeblingenGermany

In the request, be sure to include the publication number and title.

When you send information to IBM, you grant IBM a nonexclusive right to use ordistribute the information in any way it believes appropriate without incurring anyobligation to you.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information aboutthe commitment that IBM has to accessibility atwww.ibm.com/able


http://www.ibm.com/able


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.


This information is for planning purposes only. The information herein is subject tochange before the products described become available.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" atwww.ibm.com/legal/copytrade.shtml

Adobe is either a registered trademark or trademark of Adobe SystemsIncorporated in the United States, and/or other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.


http://www.ibm.com/legal/copytrade.shtml

Readers’ Comments — We'd Like to Hear from You

Linux on System zKernel Messageson SUSE Linux Enterprise Server 12

Publication No. SC34-2747-00

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:v Send your comments to the address on the reverse side of this form.v Send your comments via email to: [email protected]

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouSC34-2747-00

SC34-2747-00

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

PLACE

POSTAGE

STAMP

HERE

IBM Deutschland Research & Development GmbHInformation DevelopmentDepartment 3282Schoenaicher Strasse 22071032 BoeblingenGermany

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

SC34-2747-00

Date post:	20-Aug-2020
Category:	Documents
Upload:	others
View:	8 times
Download:	0 times

Kernel Messages - SUSE Linux Enterprise Server 12 · System z® specific Linux kernel modules on...

Documents