kernel messages - may, 2009linux on system z kernel messages may, 2009...

Linux on System z

Kernel MessagesMay, 2009Linux Kernel 2.6 - Development stream

SC34-2599-00

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 97.

First Edition (May 2009)

This edition applies to Linux on System z Development stream, and to all subsequent releases and modificationsuntil otherwise indicated in new editions.

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

Contents

About this document . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1. Message numbers and man pages . . . . . . . . . . . . . 1Building a kernel with message documentation support . . . . . . . . . . 1Generating the message man pages . . . . . . . . . . . . . . . . . 1Displaying a message man page. . . . . . . . . . . . . . . . . . . 1

Chapter 2. aes_s390 . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 3. af_iucv . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 4. ap. . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 5. appldata . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 6. cio . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 7. claw . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 8. cpcmd . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 9. cpu. . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 10. ctcm . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 11. dasd . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 12. dcssblk . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 13. extmem . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 14. hvc_iucv . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 15. hypfs . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 16. iucv . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 17. lcs . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 18. monreader . . . . . . . . . . . . . . . . . . . . . 59

Chapter 19. monwriter. . . . . . . . . . . . . . . . . . . . . . 61

Chapter 20. netiucv . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 21. qeth . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 22. s390dbf . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 23. setup . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 24. tape . . . . . . . . . . . . . . . . . . . . . . . . 73

© Copyright IBM Corp. 2009 iii

Chapter 25. time . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 26. vmcp . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 27. vmur. . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 28. xpram . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 29. zdump . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 30. zfcp . . . . . . . . . . . . . . . . . . . . . . . . 89

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 98

iv Kernel Messages - May, 2009

About this document

This message reference document contains the messages that IBM® System z®

specific kernel modules issue on the console and write to the syslog.

You can configure Linux® to issue these messages with message numbers. In thisdocument the messages are grouped by the issuing module. The modules arelisted in alphabetical order and the messages for each module are listed indescending order by message number.

This document reflects the Development stream with the May, 2009 software drop.

You can find the latest version of this document on developerWorks® atibm.com/developerworks/linux/linux390/documentation_dev.html.

© Copyright IBM Corp. 2009 v

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

vi Kernel Messages - May, 2009

Chapter 1. Message numbers and man pages

If you build your Linux kernel with message number support, you can also createman pages that users can display to obtain message details.

Building a kernel with message documentation supportTo include message documentation support, include “Kernel message numbers”(CONFIG_KMSG_IDS) in the kernel configuration menu. You can find this itemunder “Base setup”.

Generating the message man pagesYou can generate the message man pages from the root of the Linux source tree.

Generate the man pages by entering:

# make D=2

Results

After running this command, you will find a directory man in the root of your Linuxsource tree. This directory contains a man page for each System z specific kernelmessage that is issued with a message number.

Displaying a message man pageIf your distribution provides message man pages or you have generated man pagesfor your distribution, you can display message details.

Before you begin

Ensure that the message man pages are available under man/man9 where the pathto man is included in the MANPATH environment variable. Enter echo $MANPATH todisplay the eligible man directories.

If your Linux kernel has been compiled with the “CONFIG_KMSG_IDS” option,System z specific kernel messages have a message identifier. For example, thefollowing message has the message identifier xpram.ab9aa4:

xpram.ab9aa4: 50 is not a valid number of XPRAM devices

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

# man

Example

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

# man xpram.ab9aa4

© Copyright IBM Corp. 2009 1

The corresponding man page looks like this:

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

Messagexpram.ab9aa4: 50 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)

2 Kernel Messages - May, 2009

Chapter 2. aes_s390

This section contains messages that are issued bythe kernel module that provides support for theSystem z hardware accelerated implementation ofthe AES cipher algorithms (FIPS-197).

aes_s390.cb83bb AES hardware acceleration isonly available 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 onlyprovides hardware acceleration for the 128-bit keymode. The aes_s390 module will use the lessperformant software fallback algorithm for the 192-bitand 256-bit key modes.

User response: None.

Severity: Informational

aes_s390.dc0a3b Allocating AES fallback algorithm failed

Explanation: The advanced encryption standard(AES) algorithm includes three modes with 128-bit,192-bit, and 256-bit keys. Your hardware system onlyprovides hardware acceleration for the 128-bit mode.The aes_s390 module failed to allocate a softwarefallback for the AES modes that are not supported bythe hardware. A possible reason for this problem is thatthe aes_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


Chapter 3. af_iucv

This section contains messages that are issued bythe kernel module that supports the AF_IUCVaddress family for communication and addressingwith z/VM® IUCV.

af_iucv.5c08c7 Application onz/VM guest 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 machine onwhich the application runs is high enough.

Severity: Error

af_iucv.cc24c0 The af_iucv module cannot beloaded without z/VM

Explanation: The AF_IUCV protocol connects socketapplications running in Linux kernels on different z/VMvirtual machines, or it connects a Linux application toanother sockets application running in a z/VM virtualmachine. On Linux instances that run in environmentsother than the z/VM hypervisor, the AF_IUCV protocoldoes not provide any useful function and thecorresponding af_iucv module cannot be loaded.

User response: Load the af_iucv module only onLinux instances that run as guest operating systems ofthe z/VM hypervisor. If the module has been compiledinto the kernel, ignore this message.

Severity: Error


Chapter 4. ap

This section contains messages that are issued bythe kernel module that supports specialprocessors for cryptographic operations.

ap.3677f7 The hardware system does not supportAP instructions

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

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

Severity: Warning

ap.7564a4 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 devicedriver with a correct module parameter. If the devicedriver has been compiled into the kernel, correct thevalue in the kernel parameter line and reboot Linux.

Severity: Warning

ap.fce52f Registering adapter interrupts for AP 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) AnAP adapter firmware update to a firmware level thatsupports 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, reboot Linux.

Severity: Error


Chapter 5. appldata

This section contains messages that are issued bythe kernel modules that gather kernel performancedata and statistics and export this data to z/VM bymeans of APPLDATA monitor records.

appldata.0ae163 Stopping the data collection for failed with rc=

Explanation: The specified data collection moduleused the z/VM diagnose call DIAG 0xDC to stop writingdata. z/VM returned an error and the data collectioncontinues.

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

Severity: Error

appldata.81e326 Maximum OS record size exceeds the maximum recordsize

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 supported bythe 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 your Linuxinstance to support less than 110 CPUs.

Severity: Error

appldata.887845 Stopping a faulty OS datacollection failed with rc=

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 collected withthe 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/VMCP Programming Services″.

Severity: Error

appldata.ccf8e3 Starting a new OS data collectionfailed with rc=

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/VMCP Programming Services″.

Severity: Error

appldata.f26e28 Starting the data collection for failed with rc=

Explanation: The specified data collection moduleused the z/VM diagnose call DIAG 0xDC to start writingdata. z/VM returned an error and the data collectioncould not start. If the return code is 5, your z/VM guestvirtual machine is not authorized to write data 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 6. cio

This section contains messages that are issued bythe kernel module that provides basic I/Ofunctions for channel-attached devices.

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.2943d5 Processing forchannel path .

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


Severity: Notice

cio.2b995e 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 inthe kernel 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.5b32ec 0.. to 0.. 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 the

kernel parameter line to have the range of devicesexcluded when you next reboot Linux. You can write thecorrect range specification to /proc/cio_ignore to add therange of devices to the list of devices to be excluded.This does not immediately make the devices in therange inaccessible but any of these devices are ignoredif they disappear and later reappear.

Severity: Warning

cio.8665f1 The CSS device driver initializationfailed with errno=

Explanation: The channel subsystem bus could notbe established.

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

Severity: Alert

cio.b5d5f6 Channel measurement facilityinitialized using format (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 setautomatically. Mode ’parameter’ means that the formathas been set according to the ’format=’ kernelparameter.




Chapter 7. claw

This section contains messages that are issued bythe Common Link Access to Workstation (CLAW)device driver.

claw.182198 : Settingthe write subchannel online failed witherror code

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 CLAW writesubchannel must be for a 3088 device of type x’61’ andhave an uneven bus ID. The bus ID of the writesubchannel can be found from the symbolic link/sys/bus/ccwgroup/drivers/claw//cdev1where is the bus ID of the CLAWdevice.

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. Assure that avalid number of write buffers has been assigned to thedevice. See ’Device Drivers, Features, and Commands’for details about the read buffers. See the errno manpage for information about the error code.

Severity: Warning

claw.24e119 : Thecommunication peer of disconnected

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a devicestatus word DEV_STAT_UNIT_CHECK and sense code0x41. This indicates that the remote network interface isno longer available.

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 : Settingthe read subchannel online failed witherror code

Explanation: Setting the Common Link Access toWorkstation (CLAW) device online failed with an errorfor the read subchannel. This problem occurs, for

example, if the read subchannel used to create theCLAW group device is not defined as a CLAW readsubchannel in the hardware definitions. The CLAW readsubchannel must be for a 3088 device of type x’61’ andhave 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. Assure that avalid number of read buffers has been assigned to thedevice. See ’Device Drivers, Features, and Commands’for details about the read buffers. See the errno manpage for information about the error code.

Severity: Warning

claw.37e392 : Thestatus of the remote channel adapter isnot valid

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

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

Severity: Error

claw.3a62f0 Registering with the cu3088 devicedriver failed with error code

Explanation: The Common Link Access toWorkstation (CLAW) device driver failed to register withthe cu3088 channel subsystem device driver. TheCLAW device driver requires the cu3088 device driver.

User response: Enter ’lsmod | grep cu3088’ or anequivalent command to check if the cu3088 devicedriver is loaded. If the output does not show the cu3088module, unload the CLAW device driver, load thecu3088 device driver, then reload the CLAW devicedriver. See the errno man page for information aboutthe error code.

Severity: Error

claw.3f4182 : The localread buffer is smaller than the remotewrite buffer

Explanation: You set the buffer size for the localCommon Link Access to Workstation (CLAW) device


implicitly by setting the connection type. For connectiontype ’packed’ the buffer size is 32 KB, for the otherconnection types the buffer size is 4 KB. Theconnection cannot be established because the readbuffer size of the local CLAW device does not match thewrite 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 :Allocating a buffer for incoming datafailed

Explanation: A Common Link Access to Workstation(CLAW) data packet was received but the CLAW devicedriver could not allocate a receive buffer. A possiblecause of this problem is memory constraints. The datapacket 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 : The device isnot a CLAW device

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a channelinterrupt (IRQ) for a subchannel that is not a CLAWread or write 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 havebeen defined correctly to the real or virtual hardware, forexample, in your IOCDS or in your z/VM configuration.

Severity: Warning

claw.5355ea :Deactivating completed with incorrect subchannelstatus (read ,write )

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 the

network 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 : Thecommunication peer of uses an incorrect APIversion

Explanation: The Common Link Access toWorkstation (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 : Creatinga CLAW group device failed with errorcode

Explanation: The Common Link Access toWorkstation (CLAW) device driver failed to create aCLAW group device. A possible cause of this problem ismemory constraints.

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 : Thecommunication peer of rejected theconnection

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

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.4b316e • claw.68529a


claw.6c9677 : Anuninitialized CLAW device received anIRQ, c- d-

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 comes onlineor is taken offline.

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 :Activating the 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 : TheCLAW device for received an unexpected IRQ

Explanation: A Common Link Access to Workstation(CLAW) device received a channel interrupt (IRQ) whilethe CLAW device driver had assigned a status to thedevice 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 : Validating failedbecause of a frame size conflict

Explanation: You set the frame size for the localCommon Link Access to Workstation (CLAW) deviceimplicitly by setting the connection type. For connectiontype ’packed’ the frame size is 32 KB, for the otherconnection 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 set

accordingly. Restart the CLAW device, local or remote,for which you have have made corrections.

Severity: Warning

claw.7466e6 : Thecommunication peer of failed

Explanation: The remote Common Link Access toWorkstation (CLAW) device reported an error conditionthat 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 : Theremote channel adapter is not available

Explanation: During an operation, the Common LinkAccess to Workstation (CLAW) device driver receivederrno ENODEV from the common I/O layer. This meansthat the remote channel adapter was not operational oroffline.

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

Severity: Error

claw.76b4f5 : Theremote channel adapter for has been reset

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a devicestatus word DEV_STAT_UNIT_CHECK and sense code0x40. This indicates that the remote channel adapterhas been reset.

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 : rejected a request toopen multiple connections

Explanation: The Common Link Access toWorkstation (CLAW) device rejected a request by itscommunication peer to open more than one connection.The CLAW device driver only supports a singleconnection for each CLAW device.

User response: Reconfigure the remote CLAW device

claw.6c9677 • claw.7797f9

Chapter 7. claw 15

to only use one connection. Restart the remote CLAWdevice.


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

Explanation: The Common Link Access toWorkstation (CLAW) device driver failed to register withthe S/390 debug feature. No debug traces will beavailable for CLAW.

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 debug feature,then reload the CLAW device driver. See the errno manpage for information about the error code.

Severity: Error

claw.7f27d6 : Theremote channel adapter for is faulty

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a devicestatus word DEV_STAT_UNIT_CHECK and sense code0x30. This indicates that the remote channel adapter isfaulty.

User response: Check and restart the remote channeladapter and activate the remote interface. If the problempersists, perform device diagnosis for the remotechannel adapter and examine the subchannel trace forfurther diagnostic information. For information about thesense code see /Documentation/s390/cds.txt in theLinux source tree. Search for ’SNS0’ to locate theinformation.

Severity: Warning

claw.81d266 : TheCLAW device received an unexpectedIRQ, c- d-

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

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.823401 :Creating the /proc files for a newCLAW device failed

Explanation: For each Common Link Access toWorkstation (CLAW) device the CLAW device drivermaintains files in the proc file system. The CLAW devicedriver failed to create a new CLAW device because itcould not create these /proc files for the new device.You cannot create CLAW devices for Linux kernels thatdo not include a proc file system.

User response: Ensure that your Linux kernelprovides a proc file system. Reboot Linux. If your kernelprovides a proc file system and the problem persists,contact your support organization.

Severity: Error

claw.858a92 : Thecommunication peer of rejected a connectionrequest

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

User response: Examine the settings of your localand remote CLAW device. Correct the erroneous settingand restart the CLAW device, local or remote, for whichyou have made corrections.

Severity: Warning

claw.887cf5 : Validating failedbecause of a version conflict

Explanation: The Common Link Access toWorkstation (CLAW) network interface cannot beactivated because the remote CLAW device does notsupport CLAW version 2. The CLAW device driverrequires CLAW version 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 : Adaptername for does not match the remote hostname

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. The

claw.7c1758 • claw.89e5ba


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.9bd9c2 : rejected a connectionrequest because it is already active

Explanation: The Common Link Access toWorkstation (CLAW) device rejected a connectionrequest by its communication peer because theconnection is already active. The CLAW device driveronly supports a single connection for each CLAWdevice. This might be a runtime problem.

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


claw.a84a95 : 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. For connectiontype ’packed’ the buffer size is 32 KB, for the otherconnection types the buffer size is 4 KB. Theconnection cannot be established because the writebuffer size of the local CLAW device does not match theread 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 : Validating failedbecause of a host or adapter namemismatch

Explanation: The Common Link Access toWorkstation (CLAW) network interface cannot beactivated because there is a mismatch between a hostname and the corresponding adapter name. The localhost name must match the remote adapter name andthe local adapter name must match the remote hostname.

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

Severity: Warning

claw.abecae : A datastreaming timeout occurred for

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a devicestatus word DEV_STAT_UNIT_CHECK and sense code0x24. This indicates a data streaming timeout. Theremote channel adapter 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 : Settingsfor validated(version=, remotedevice=, rc=, adaptername=, 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 : Thecommunication peer of sent a faulty frame oflength

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 not resolvethe error, gather logs and traces from the remote CLAWdevice to obtain further diagnostic data.

Severity: Warning

claw.9bd9c2 • claw.b322ac

Chapter 7. claw 17

claw.b40a6a : Thecommunication peer of rejected a connectionrequest because 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. not be started.

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 : Thecommunication peer of sent an unknowncommand 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 connection remainsoperational.

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

Severity: Warning

claw.c06c67 : A readdata parity error occurred for

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a devicestatus word DEV_STAT_UNIT_CHECK and sense code0x10. This indicates a read data parity error. Theremote channel adapter 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 about thesense code see /Documentation/s390/cds.txt in theLinux source tree. Search for ’SNS0’ to locate theinformation.

Severity: Warning

claw.ce65ab : Hostname for does not match the remoteadapter name

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 : rejected a connectionrequest because of a type mismatch

Explanation: The Common Link Access toWorkstation (CLAW) device rejected a request by itscommunication peer to open a connection. A connectioncan only be opened if the same connection type hasbeen set for both the local and the remote CLAWdevice.

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 : A datatransfer parity error occurred for

Explanation: The Common Link Access toWorkstation (CLAW) device driver received a devicestatus word DEV_STAT_UNIT_CHECK and sense code0x20. This indicates a data parity error. The remotechannel adapter or the channel might be faulty.

User response: Ensure that all cables are securelyplugged. 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 : Activating failed becauseof an incorrect link ID=

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 a time(link ID=1) for each network interface.

claw.b40a6a • claw.f10136


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

Severity: Warning

claw.f26e3d : Thecommon device layer returned errorcode

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 relatedmessages. Restart the remote channel adapter. If theproblem persists, examine the subchannel trace forfurther diagnostic information.

Severity: Error

claw.f26e3d

Chapter 7. claw 19

Chapter 8. cpcmd

This section contains messages that are issued bythe cpcmd 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 control program(CP). If a program that uses the cpcmd function doesnot allocate a contiguous response buffer below 2 GBguest real storage, cpcmd creates a bounce buffer to beused as the response buffer. Because of low memory ormemory fragmentation, cpcmd could not create thebounce buffer.

User response: Look for related page allocationfailure messages and at the stack trace to find outwhich program or operation failed. Free some memoryand retry the failed operation. Consider allocating morememory to your z/VM guest virtual machine.

Severity: Warning


Chapter 9. cpu

This section contains messages that are issued bythe System z specific CPU management functions.

cpu.17772b Processor started, address ,identification

Explanation: The kernel detected a CPU with thegiven characteristics.



cpu.33a262 configured CPUs, standby CPUs

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 Mag1 to Mag6 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.2which specifies the maximum possible nesting that canbe configured through dynamic changes. For details seethe SYSIB 15.1.2 information in the ″Principles ofOperation.″



cpu.e2917c CPU exceeds themaximum 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 not includeall CPU information.

Severity: Warning

cpu.f76a91 Processor stopped

Explanation: A logical CPU has been set offline.




Chapter 10. ctcm

This section contains messages that are issued bythe Channel-to-Channel (CTC) device driver. CTCconnections are high-speed point-to-pointconnections between two operating systeminstances on System z.

ctcm.06c639 : Theadapter received 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 CTCMdevice, for example, with ifconfig. Check if theconnection to the remote device still works. If the CTCMdevice is not operational, set it offline and back online. Ifthis does 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 : 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 CTCMdevice, 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 :Initialization failed with RX/TX inithandshake error

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 debug dataand report the problem to your support organization.

Severity: Warning

ctcm.4b5292 : 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 not operational,set it offline and back online. If this does not resolve theproblem, perform a manual recovery. See ″DeviceDrivers, Features, and Commands″ for details abouthow to recover a CTCM device. If this problem persists,gather Linux debug data and report the problem to yoursupport organization.

Severity: Warning

ctcm.58aa19 : The remote operatingsystem is not available

Explanation: The operating system instance with thecommunication peer has disconnected. Possiblereasons are that the operating system instance hasbeen rebooted or shut down.

User response: Ensure that the peer operatingsystem instance is running and that the peer interface isoperational.

Severity: Notice

ctcm.8079b5 : Anadapter hardware 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 : 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 : The communicationpeer is 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 : 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

Explanation: A hardware operation ended with anerror.

User response: Check the status of the CTCMdevice, 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 problem persists,gather Linux debug data, collect the hardware logs, andreport the problem to your support organization.

Severity: Error

ctcm.defd4f : The XIDused in the MPC protocol is not valid,rc =

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 : Thenetwork backlog for isexceeded, package dropped

Explanation: There is more network traffic than canbe handled by the device. The device is closed andsome data has not been transmitted. The device mightbe recovered automatically.

User response: Investigate and resolve thecongestion. If necessary, set the device online to makeit operational.

Severity: Warning

ctcm.fde68a : The specified targetdevice is 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 11. dasd

This section contains messages that are issued bythe DASD device driver.

dasd.00f842 : An I/O controlcall used incorrect flags 0x

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

User response: Contact the owner of the formattingtool.

Severity: Warning

dasd.01a684 : FORMAT 4 - Nosync 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.01f692 : FORMAT 9 -Reserved



Severity: Warning

dasd.02c01a : FORMAT 7 - Noresponse to selection after a pollinterruption



Severity: Warning

dasd.04422e Registering the device driver withmajor number 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 driver andunload this device driver. Then try again to load theDASD device driver.

Severity: Warning

dasd.0471ed : FORMAT 0 -Reserved



Severity: Warning

dasd.04ae78 : FORMAT 7 -Missing end operation; device transferincomplete



Severity: Warning

dasd.05b6e3 : FORMAT 8 -End operation with transfer count zero



Severity: Warning

dasd.05c8ba : FORMAT 6 -Overrun on channel F



Severity: Warning

dasd.06e412 : FORMAT 0 -Status Not As Required: reason

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


Severity: Warning

dasd.07541e : 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.08b7b8 : FORMAT 4 - Nosync byte in data area



Severity: Warning

dasd.08d1ee : FORMAT 9 -Head address did not compare



Severity: Warning

dasd.094439 : FORMAT 3 -Reserved



Severity: Warning

dasd.0ad5d2 : FORMAT 4 - Nosync byte in home address area



Severity: Warning

dasd.0ae5e4 Discipline 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.0af728 : FORMAT 6 -Overrun on channel B



Severity: Warning

dasd.0d6cb0 : FORMAT F -Subsystem Processing Error

Explanation: A firmware logic error has beendetected. This is an operating system independentmessage that is issued by the storage system.


Severity: Warning

dasd.0e881a : FORMAT 7 -Invalid tag-in for an immediatecommand sequence



Severity: Warning

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

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

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

Severity: Warning

dasd.126bfe : 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.08b7b8 • dasd.126bfe


dasd.1577ff : FORMAT F -Caching terminated

Explanation: The storage system was unable toinitiate caching or had to suspend caching for a 3990control unit. If this problem is caused by a failurecondition, an additional message will provide moreinformation about the failure. This is an operatingsystem independent message that is issued by thestorage system.

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

Severity: Warning

dasd.190a3f : The DASDcannot be formatted with 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.1ac0f4 : Flushing theDASD request queue failed for 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.1bdba7 : Start tracknumber used informatting is too big

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

User response: Contact the owner of the formattingtool.

Severity: Warning

dasd.1c04cd : FORMAT 4 -Key area error; offset active



Severity: Warning

dasd.1c9171 : DIAGinitialization failed with rc=

Explanation: Initializing the DASD with the DIAGdiscipline failed. Possible reasons for this problem arethat the device is read-only, has a device type otherthan FBA or ECKD, or has a block size other than oneof the supported sizes: 512 byte, 1024 byte, 2048 byte,or 4096 byte.

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 cannot resolvethe error, note the error code and contact your supportorganization.

Severity: Warning

dasd.1cfbb8 : FORMAT 1 -Offset active cannot be reset



Severity: Warning

dasd.1dd1a2 : FORMAT 2 -Reserved



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/VM notby Linux.

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


dasd.20b59b : 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.

User response: For more information see the

dasd.1577ff • dasd.20b59b

Chapter 11. dasd 29

documentation of your storage system.

Severity: Warning

dasd.22e514 : FORMAT 4 - Nosyn byte in count address area; offsetactive



Severity: Warning

dasd.2529f2 : 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.2567a1 : 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.2741d8 : DIAG ERPfailed with rc=

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 forrelated I/O errors, and report this problem to yoursupport organization.

Severity: Warning

dasd.292792 : FORMAT D -Reserved




Severity: Warning

dasd.29f189 : 0x isnot a known command

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

User response: Contact your support organization.

Severity: Error

dasd.2dd933 : FORMAT 1 -Device check-2 error or Set Sector isnot complete



Severity: Warning

dasd.2ebc2e : FORMAT 5 -Data Check in the count area; offsetactive



Severity: Warning

dasd.2f6a90 The probeonly mode has beenactivated

Explanation: The probeonly mode of the DASDdevice driver has been activated. In this mode thedevice driver rejects any ’open’ syscalls with EPERM.



dasd.308a03 : FORMAT 5 -Reserved



Severity: Warning

dasd.331a2a : FORMAT 1 -Reserved


dasd.22e514 • dasd.331a2a



Severity: Warning

dasd.34a404 : cqr timed out (), retries remaining

Explanation: One 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 to yoursupport organization.

Severity: Error

dasd.39c600 : FORMAT 8 -Unexpected end operation responsecode



Severity: Warning

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.3dd39b : FORMAT 7 -RCC 1 and RCC 2 sequences notsuccessful



Severity: Warning

dasd.3e7d29 Setting theDASD online with discipline failed with rc=

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

User response: Look for previous error messages. If

you cannot resolve the error, note the return code andcontact your support organization.

Severity: Warning

dasd.3ea257 : FORMAT 1 -Device not ready



Severity: Warning

dasd.400105 : FORMAT 6 -Overrun on channel C



Severity: Warning

dasd.412b53 : DASD with KB/block, KBtotal size, KB/track,

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



dasd.423705 : FORMAT 0 -Channel Returned with Incorrect retryCCW

Explanation: A command portion of the CCW returnedafter a command retry sequence does not match thecommand for which retry was signaled. This is anoperating system independent message that is issuedby the storage system.


Severity: Warning

dasd.423d5b : FORMAT 7 -Missing end operation; device transfercomplete



Severity: Warning

dasd.34a404 • dasd.423d5b

Chapter 11. dasd 31

dasd.42a207 : The specifiedrecord was not found

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

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

Severity: Error

dasd.43830c : 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.459c47 : log SIM - SRC:

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 storageserver documentation.

Severity: Warning

dasd.45f2d1 : The disk layoutof the DASD is not supported

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


Severity: Warning

dasd.46d841 : FORMAT 5 -Data Check in the key area



Severity: Warning

dasd.47fcac : ERP () refers to



Severity: Error

dasd.481dec : 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.487b65 : SIM - SRC:

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

User response: Look up the SRC in the storageserver documentation.

Severity: Error

dasd.4a5b55 : FORMAT 7 -DASD controller not available ondisconnected command chain



Severity: Warning

dasd.4aeb6d : FORMAT 8 -DASD controller failed to set or resetthe long busy latch



Severity: Warning

dasd.42a207 • dasd.4aeb6d


dasd.4cdcde : ERP chain atEND of ERP-ACTION



Severity: Error

dasd.5005eb : FORMAT 8 -Reserved



Severity: Warning

dasd.50a6e5 : Formatting unit failed with rc=

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 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. The ParallelAccess Volume (PAV) support of the DASD devicedriver has been deactivated.



dasd.538dcc : FORMAT 4 -Reserved



Severity: Warning

dasd.55aa2f : FORMAT 1 -Missing device address bit



Severity: Warning

dasd.5806f8 : FORMAT 8 - DPSchecks after a system reset orselective reset



Severity: Warning

dasd.58865b : FORMAT 1 -Cylinder address did not compare



Severity: Warning

dasd.58c328 : FORMAT 0 -Invalid Defective/Alternate TrackPointer

Explanation: A defective track has been accessed.The subsystem 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.4cdcde • dasd.58c328

Chapter 11. dasd 33

dasd.5c0c98 : default ERP hasrun out of retries and failed

Explanation: The error recovery procedure (ERP)tried to 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.5cf324 : 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.5efa1b : FORMAT 4 - Nosync byte in count address area



Severity: Warning

dasd.648dca : FORMAT 6 -Overrun on channel D



Severity: Warning

dasd.65917e : Data recoveredduring retry with PCI fetch mode 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.65b8de : FORMAT 7 -Reserved



Severity: Warning

dasd.680aac : 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.696eb5 is not a supporteddevice option

Explanation: The dasd= parameter includes anunknown option for a DASD or a device range. Optionsare specified in parenthesis and immediately follow adevice or device range.

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

Severity: Warning

dasd.6e3fdc : FORMAT 6 -Overrun on channel G



Severity: Warning

dasd.6eae2d : is offline or notinstalled - INTERVENTION REQUIRED!!

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.For details see the storage system documentation.

Severity: Error

dasd.5c0c98 • dasd.6eae2d


dasd.7109ed : FORMAT 1 -Interruption cannot be reset



Severity: Warning

dasd.72eaa3 : FORMAT 6 -Overrun on channel A



Severity: Warning

dasd.74be4d : FORMAT 8 -DPS cannot be filled



Severity: Warning

dasd.75373e : Cancellingrequest failed withrc=

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.757950 : New FBA DASD/ (CU/)with MB and B/blk




dasd.75ca81 : 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.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 : The DASDcannot be 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.792e2f : FORMAT 8 - Endoperation with transfer count not zero



Severity: Warning

dasd.7b19bf : FORMAT 3 -Allegiance terminated

Explanation: Allegiance terminated because of aReset Allegiance or an Unconditional Reserve commandon another channel. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd.7109ed • dasd.7b19bf

Chapter 11. dasd 35

dasd.7bb394 : FORMAT 7 -Invalid DCC selection response ortimeout



Severity: Warning

dasd.7c1681 : FORMAT 0 -Storage Path Restart

Explanation: An operation for an active channelprogram was queued in a Storage Control when a warmstart was received by the path. This is an operatingsystem independent message that is issued by thestorage system.


Severity: Warning

dasd.7eabfd : 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.7f0765 : Track 0 has norecords 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.81757d : FORMAT 1 -Device Status 1 not as expected



Severity: Warning

dasd.840169 : FORMAT 6 -Overrun on channel E



Severity: Warning

dasd.869e5e : FORMAT 6 -Overrun on channel H



Severity: Warning

dasd.894a4b : FORMAT 7 -3990 microcode time out whenstopping selection



Severity: Warning

dasd.8b4bdf : FORMAT 2 -Microcode detected error



Severity: Warning

dasd.90fb0d : New DASD/ (CU/)with cylinders, heads, sectors




dasd.910d5f : 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 track

dasd.7bb394 • dasd.910d5f


pinned for this device. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd.939f75 The statistics have been reset

Explanation: The DASD statistics data have beenreset.



dasd.948ccf : FORMAT 4 - Keyarea error



Severity: Warning

dasd.966201 The statistics feature has beenswitched on

Explanation: The statistics feature of the DASDdevice driver has been switched on.



dasd.96f088 : FORMAT 7 -RCC 1 sequence not successful



Severity: Warning

dasd.9957b7 : FORMAT 1 -Head address does not compare



Severity: Warning

dasd.9a48d5 : FORMAT 4 - Nosyn byte in data area; offset active



Severity: Warning

dasd.9bb776 : FORMAT 4 -Data area error; offset active



Severity: Warning

dasd.9e183a : FORMAT 4 -Count area error



Severity: Warning

dasd.9f31f9 : FORMAT 7 -RCC initiated by a connection checkalert



Severity: Warning

dasd.a0ce75 : FORMAT 4 - Nosync byte in key area; offset active



Severity: Warning

dasd.a28dc6 : The DASDcache mode was set to ( cylinderprestage)

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


dasd.939f75 • dasd.a28dc6

Chapter 11. dasd 37


dasd.a35e01 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.a3baba : 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 : The DASDcannot be formatted while it is enabled

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

kernel messages - may, 2009linux on system z kernel messages may, 2009...

Documents