Kernel Messages - SUSE Linux Enterprise Server 12 SP2 · 2016. 11. 4. · specific Linux kernel...

Linux on z Systems and LinuxONE

Kernel Messageson SUSE Linux Enterprise Server 12 SP2

SC34-2747-02

IBM

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

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

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

Contents

About this publication . . . . . . . . vOther publications that apply to SUSE LinuxEnterprise Server 12 SP2 on IBM z Systems . . . . v

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

Chapter 2. Viewing messages with theIBM Doc Buddy app . . . . . . . . . 3

Chapter 3. Summary of prefixes . . . . 5

Chapter 4. aes_s390 . . . . . . . . . 11

Chapter 5. af_iucv . . . . . . . . . . 13

Chapter 6. ap . . . . . . . . . . . . 15

Chapter 7. appldata . . . . . . . . . 17

Chapter 8. cio . . . . . . . . . . . . 19

Chapter 9. cpcmd . . . . . . . . . . 21

Chapter 10. cpu . . . . . . . . . . . 23

Chapter 11. cpum_cf . . . . . . . . . 25

Chapter 12. cpum_sf . . . . . . . . . 27

Chapter 13. ctcm . . . . . . . . . . 29

Chapter 14. dasd-eckd . . . . . . . . 31

Chapter 15. dasd-fba. . . . . . . . . 47

Chapter 16. dasd . . . . . . . . . . 49

Chapter 17. dcssblk . . . . . . . . . 55

Chapter 18. diag288_wdt . . . . . . . 57

Chapter 19. extmem . . . . . . . . . 59

Chapter 20. hmcdrv . . . . . . . . . 63

Chapter 21. hvc_iucv . . . . . . . . 65

Chapter 22. hypfs . . . . . . . . . . 67

Chapter 23. iucv. . . . . . . . . . . 69

Chapter 24. lcs . . . . . . . . . . . 71

Chapter 25. monreader . . . . . . . . 73

Chapter 26. monwriter . . . . . . . . 75

Chapter 27. netiucv . . . . . . . . . 77

Chapter 28. numa . . . . . . . . . . 79

Chapter 29. numa_emu. . . . . . . . 81

Chapter 30. os_info . . . . . . . . . 83

Chapter 31. perf . . . . . . . . . . . 85

Chapter 32. prng . . . . . . . . . . 87

Chapter 33. qeth . . . . . . . . . . 89

Chapter 34. s390dbf . . . . . . . . . 97

Chapter 35. sclp_cmd . . . . . . . . 99

Chapter 36. sclp_config . . . . . . . 101

Chapter 37. scm_block . . . . . . . 103

Chapter 38. setup . . . . . . . . . 105

Chapter 39. tape . . . . . . . . . . 107

Chapter 40. tape_34xx . . . . . . . 109

Chapter 41. tape_3590. . . . . . . . 113

Chapter 42. time . . . . . . . . . . 115

Chapter 43. vmlogrdr . . . . . . . . 117

Chapter 44. vmur . . . . . . . . . . 119

Chapter 45. xpram . . . . . . . . . 121

Chapter 46. zcrypt . . . . . . . . . 123

Chapter 47. zdump . . . . . . . . . 125

© Copyright IBM Corp. 2009, 2016 iii

Chapter 48. zfcp . . . . . . . . . . 127

Chapter 49. zpci . . . . . . . . . . 133

Accessibility . . . . . . . . . . . . 135

Notices . . . . . . . . . . . . . . 137Trademarks . . . . . . . . . . . . . . 138

iv Kernel Messages - SUSE Linux Enterprise Server 12 SP2

About this publication

This message reference document contains the messages that are issued by IBM® zSystems™ specific Linux kernel modules on SUSE Linux Enterprise Server 12 SP2.

On SUSE Linux Enterprise Server 12 SP2, 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 SP2. For messagenumbers that are not included in this publication, see the kernel messagesreference at www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.l0kmsg.doc/l0km_plugin_top.html.

You can find the newest version of this publication on IBM Knowledge Center atwww.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_suse.html

Other publications that apply to SUSE Linux Enterprise Server 12 SP2on IBM z Systems

Go to IBM Knowledge Center or to developerWorks® for Linux on IBM z Systemspublications about SUSE Linux Enterprise Server 12 SP2.

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

SC34-2745v Device Drivers, Features, and Commands on SUSE Linux Enterprise Server 12 SP2 as

a KVM Guest, SC34-2756v Using the Dump Tools on SUSE Linux Enterprise Server 12 SP1, SC34-2746

For each of the following publications, you can find the version that most closelyreflects SUSE Linux Enterprise Server 12 SP2:v How to use FC-attached SCSI devices with Linux on z Systems, 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 z Systems 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, 2016 v

http://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.l0kmsg.doc/l0km_plugin_top.htmlhttp://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.l0kmsg.doc/l0km_plugin_top.htmlhttp://www.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_suse.htmlhttp://www.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_suse.htmlhttp://www.ibm.com/developerworks/linux/linux390/documentation_suse.html

vi Kernel Messages - SUSE Linux Enterprise Server 12 SP2

Chapter 1. Displaying a message man page

This document lists z Systems specific kernel messages with message identifiers.SUSE Linux Enterprise Server 12 SP2 provides an RPM with a man page for eachof these 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-s390x.rpm andshipped on DVD1.

Procedure

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

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

[email protected]: 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, 2016 1

2 Kernel Messages - SUSE Linux Enterprise Server 12 SP2

Chapter 2. Viewing messages with the IBM Doc Buddy app

You can view documentation for z Systems specific Linux kernel messages throughan app for mobile devices.

IBM Doc Buddy is helpful in environments from where the messagedocumentation on the Internet is not directly accessible.

Before you begin

You can obtain IBM Doc Buddy from Apple App Store or from Google Play. Formore information about IBM Doc Buddy, go tohttp://ibmdocbuddy.mybluemix.net.

Procedure

Perform the following steps to set up IBM Doc Buddy on your mobile device:1. In your app repository, search for “IBM Doc Buddy”, then download, install,

and start the app.

2. Enter the setup mode by tapping the

symbol at the top left corner in theapp window.

3. Select Components.4. Search for “Linux on z Systems” and download the messages component.5. Close the setup mode.

Results

You can now enter IDs for messages of interest in the main search field anddisplay the message documentation on your mobile device.


https://geo.itunes.apple.com/us/app/ibm-doc-buddy/id1121244571?mt=8https://play.google.com/store/apps/details?id=com.ibm.systems.supportassistant&utm_source=global_co&utm_medium=prtnr&utm_content=Mar2515&utm_campaign=PartBadge&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1http://ibmdocbuddy.mybluemix.net

Chapter 3. 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 thez Systems 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.

cpcmd

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

cpu

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

cpum_cf

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

cpum_sf

Messages with a prefix cpum_sf are issued by kernel functions that support thez/Architecture CPU-measurement sampling 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 z Systems.

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.

diag288_wdt

Messages with a prefix diag288_wdt are issued by the diag288_wdt kernel module.

extmem

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

hmcdrv

Messages with a prefix hmcdrv are issued by the hmcdrv kernel module thatsupports the DVD drive of the HMC or SE.

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, or


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

numa

Messages with a prefix numa are issued by a kernel function that supportsnon-uniform memory access (NUMA).

numa_emu

Messages with a prefix numa_emu are issued by a kernel function that emulatesnon-uniform memory access (NUMA).

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.

prng

Messages with a prefix prng are issued by the pseudo-random number devicedriver.

qeth

Messages with a prefix qeth are issued by the qeth device driver. The qeth devicedriver supports a multitude of network connections, for example, connections

Chapter 3. Summary of prefixes 7

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

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 z Systems 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.


xpram

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

zcrypt

Messages with a prefix zcrypt are issued by the cryptographic device driver.

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 z Systems SCSI-over-Fibre Channeladapter. The zfcp device driver supports Fibre Channel-attached SCSI devices onLinux on z Systems.

zpci

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

Chapter 3. Summary of prefixes 9

Chapter 4. aes_s390

Messages with a prefix aes_s390 are issued by thekernel module that supports the z Systems

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 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 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 5. 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 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 machineon which the application runs is high enough.

Severity: Error


Chapter 6. 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 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 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 7. 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 failed with rc=

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 exceeds the maximum record size

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=

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=

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 failed with rc=

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 8. cio

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

cio.0e0832 : No interrupt wasreceived within (CS=, DS=,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 : 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 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 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 : 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.. was triggered

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


Severity: Notice

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 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.. failed witherrno=

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=

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 : 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 : 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 (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.



cio.d25039 Link stopped: RS=RSID= IC= IUPARAMS= IUNODEID= AUPARAMS= AUNODEID=

Explanation: A hardware error has occurred. A unit atone end of an interface link has detected a failure inthe link or in one of the units attached to the link. As aresult, data transfer across the link has stopped. In themessage text, the node IDs of involved units arerepresented in the following format:TTTTTT/MDL,MMM.PPSSSSSSSSSSSS,XXXX whereTTTTTT refers to the machine type, MDL the modelnumber, MMM the manufacturer, PP the manufacturingplant, SSSSSSSSSSSS the unit sequence number andXXXX the machine type-dependent physical interfacenumber. If no data is available for the unit parametersor node ID field, "n/a" is used instead.

User response: Report the problem to your supportorganization.

Severity: Error

cio.e99758 Link degraded: RS=RSID= IC= IUPARAMS= IUNODEID= AUPARAMS= AUNODEID=

Explanation: A hardware error has occurred. A unit atone end of an interface link has detected a failure inthe link or in one of the units attached to the link. As aresult, data transfer across the link is degraded. In themessage text, the node IDs of involved units arerepresented in the following format:TTTTTT/MDL,MMM.PPSSSSSSSSSSSS,XXXX whereTTTTTT refers to the machine type, MDL the modelnumber, MMM the manufacturer, PP the manufacturingplant, SSSSSSSSSSSS the unit sequence number andXXXX the machine type-dependent physical interfacenumber. If no data is available for the unit parametersor node ID field, "n/a" is used instead.

User response: Report the problem to your supportorganization.

Severity: Warning

cio.7a35c2 • cio.e99758


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 the zSystems

cpu.33a262 configuredCPUs, 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 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 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=

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=

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=

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[] 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=

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

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

cpum_sf.13a98c Switching off the sampling facilityfailed with rc=

Explanation: The CPU-measurement sampling facilitycould not be switched off and continues to run. Fordetails, see LOAD SAMPLING CONTROLS in "TheLoad-Program-Parameter and the CPU-MeasurementFacilities", SA23-2260.

User response: If this problem persists, reboot yourLinux instance.

Severity: Error

cpum_sf.20f026 A sampling buffer entry is incorrect(alert=0x)

Explanation: An incorrect sampling facility bufferentry was detected. The alert code indicates the rootcause, for example, an incorrect entry address or anincorrect sample-data-block-table entry.

User response: End active performance measurementsessions, for example, perf processes. If the problempersists, reboot your Linux instance.

Severity: Error

cpum_sf.72392d Loading sampling controls failed:op= err=

Explanation: The sampling facility support could notload sampling controls to enable (operation type 1) ordisable (operation type 2) the CPU-measurementsampling facility. For details of the error condition, seeLOAD SAMPLING CONTROLS in "TheLoad-Program-Parameter and the CPU-MeasurementFacilities", SA23-2260.

User response: If the problem persists, reboot yourLinux instance.

Severity: Error

cpum_sf.856c05 Registering for s390dbf failed

Explanation: The device driver failed to register forthe s390 debug feature. You will not receive any debuginformation. A possible cause of this problem ismemory constraints.

User response: Consider assigning more memory toyour Linux instance.

Severity: Error

cpum_sf.96d859 Sampling facility support for perf isnot available: reason=

Explanation: The device driver could not initialize thesampling facility support. Possible reason codes are:0001: The device driver failed to queryCPU-measurement sampling facility information. 0002:The device driver does not support the basic-samplingfunction that is available on the LPAR within which theLinux instance runs. 0003: The device driver could notregister to receive CPU-measurement alerts. A possiblecause of this problem is memory constraints. 0004: Thedevice driver could not register the PerformanceMeasurement Unit (PMU) for the CPU-measurementsampling facility. A possible cause of this problem ismemory constraints.

User response: Consider assigning more memory toyour Linux instance.

Severity: Error

cpum_sf.9aaa3d Sample data was lost

Explanation: Sample data was lost because ofmachine-internal high-priority activities. The samplingfacility is stopped.

User response: End all performance measurementsessions. Discard the measurement data, which arelikely to be flawed. Repeat your measurements. If theproblem persists, contact your hardware administrator.

Severity: Error

cpum_sf.a2e96f The sampling buffer limits havechanged to: min= max= (diag=x)

Explanation: The minimum or maximum size limit forthe sampling facility buffer was changed. The change iseffective immediately.




Chapter 13. 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 z Systems

ctcm.06c639 : 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 : 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 :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 debugdata and report the problem to your supportorganization.

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 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 : 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 : 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 : 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 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 : 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 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 : 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 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 : 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 14. 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 : An I/Ocontrol call used incorrect flags 0x

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

User response: Contact the owner of the formattingtool.

Severity: Warning

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



Severity: Warning

dasd-eckd.02c01a : FORMAT 7 -No response to selection after a pollinterruption



Severity: Warning

dasd-eckd.0471ed : FORMAT 0 -Reserved



Severity: Warning

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



Severity: Warning

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



Severity: Warning

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



Severity: Warning

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

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 : 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 : FORMAT 4- No sync byte in data area



Severity: Warning

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



Severity: Warning

dasd-eckd.094439 : FORMAT 3 -Reserved



Severity: Warning

dasd-eckd.0ad5d2 : FORMAT 4- No sync byte in home address area



Severity: Warning

dasd-eckd.0af728 : FORMAT 6 -Overrun on channel B



Severity: Warning

dasd-eckd.0d6cb0 : 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 : FORMAT 7 -Invalid tag-in for an immediatecommand sequence



Severity: Warning

dasd-eckd.0ec8bb : Readingdevice feature codes failed (rc=) for new path

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 : 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 : 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 : FORMAT 4 -Key area error; offset active



Severity: Warning

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



Severity: Warning

dasd-eckd.1dd1a2 : FORMAT 2- Reserved



Severity: Warning

dasd-eckd.1fd065 : 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 : 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 : FORMAT 4 -No syn byte in count address area;offset active



Severity: Warning

dasd-eckd.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-eckd.27f2cd : 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 : FORMAT D- Reserved



Severity: Warning

dasd-eckd.29f189 : 0xis 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 : New DASD/ (CU /) with cylinders, heads, sectors

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

Chapter 14. dasd-eckd 33

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 : FORMAT 1- Device check-2 error or Set Sector isnot complete



Severity: Warning

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



Severity: Warning

dasd-eckd.308a03 : FORMAT 5 -Reserved



Severity: Warning

dasd-eckd.331a2a : FORMAT 1 -Reserved



Severity: Warning

dasd-eckd.36ac9b : Start track used in formattingexceeds end track

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

User response: Contact the owner of the formattingtool.

Severity: Warning

dasd-eckd.39c600 : FORMAT 8 -Unexpected end operation response code



Severity: Warning

dasd-eckd.3dd39b : FORMAT 7- RCC 1 and RCC 2 sequences notsuccessful



Severity: Warning

dasd-eckd.3ea257 : FORMAT 1 -Device not ready



Severity: Warning

dasd-eckd.400105 : FORMAT 6 -Overrun on channel C



Severity: Warning

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

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



dasd-eckd.4170f2 : 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 : 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 : FORMAT 7- Missing end operation; device transfercomplete



Severity: Warning

dasd-eckd.42a207 : 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 : 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 : 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 storage serverdocumentation.

Severity: Warning

dasd-eckd.45f2d1 : 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 : FORMAT 5 -Data Check in the key area



Severity: Warning

dasd-eckd.47fcac : ERP () refers to



Severity: Error

dasd-eckd.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-eckd.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.

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


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

Severity: Error

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



Severity: Warning

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



Severity: Warning

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



Severity: Error

dasd-eckd.5005eb : FORMAT 8 -Reserved



Severity: Warning

dasd-eckd.538dcc : FORMAT 4 -Reserved



Severity: Warning

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



Severity: Warning

dasd-eckd.5806f8 : FORMAT 8 -DPS checks after a system reset orselective reset



Severity: Warning

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



Severity: Warning

dasd-eckd.58c328 : 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 : 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 : FORMAT 4 -No sync byte in count address area



Severity: Warning

dasd-eckd.5f55a6 Path . is back online afterservice on the storage server

Explanation: A path had been set offline temporarilybecause of a service action on the storage server. Theservice action has completed, and the channel path isavailable again.



dasd-eckd.637cf1 : Readingdevice feature codes failed withrc=

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 : FORMAT 6 -Overrun on channel D



Severity: Warning

dasd-eckd.65917e : 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 : FORMAT 7- Reserved



Severity: Warning

dasd-eckd.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-eckd.6e3fdc : FORMAT 6 -Overrun on channel G



Severity: Warning

dasd-eckd.6eae2d : 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 : FORMAT 1 -Interruption cannot be reset



Severity: Warning

dasd-eckd.5efa1b • dasd-eckd.7109ed


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



Severity: Warning

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



Severity: Warning

dasd-eckd.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-eckd.767039 Service on the storage servercaused path . to go offline

Explanation: A channel path to the DASD has beenset offline because of a service action on the storageserver. The path will be set back online automaticallywhen the service action is completed.


Severity: Warning

dasd-eckd.792e2f : FORMAT 8 -End operation with transfer count notzero



Severity: Warning

dasd-eckd.7b19bf : FORMAT 3 -Allegiance terminated

Explanation: Allegiance terminated because of a ResetAllegiance or an Unconditional Reserve command onanother channel. This is an operating system

independent message that is issued by the storagesystem.


Severity: Warning

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



Severity: Warning

dasd-eckd.7c1681 : 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 : 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 : 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.72eaa3 • dasd-eckd.7f0765


dasd-eckd.81757d : FORMAT 1 -Device Status 1 not as expected



Severity: Warning

dasd-eckd.840169 : FORMAT 6 -Overrun on channel E



Severity: Warning

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



Severity: Warning

dasd-eckd.87ddea : 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 : FORMAT 7 -3990 microcode time out when stoppingselection



Severity: Warning

dasd-eckd.8b4bdf : FORMAT 2- Microcode detected error



Severity: Warning

dasd-eckd.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 trackpinned for this device. This is an operating systemindependent message that is issued by the storagesystem.


Severity: Warning

dasd-eckd.948ccf : FORMAT 4 -Key area error



Severity: Warning

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



Severity: Warning

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



Severity: Warning

dasd-eckd.9a48d5 : FORMAT 4 -No syn byte in data area; offset active



Severity: Warning

dasd-eckd.81757d • dasd-eckd.9a48d5


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



Severity: Warning

dasd-eckd.9e183a : FORMAT 4 -Count area error



Severity: Warning

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



Severity: Warning

dasd-eckd.a0ce75 : FORMAT 4 -No sync byte in key area; offset active



Severity: Warning

dasd-eckd.a28dc6 : The DASDcache mode was set to ( cylinder prestage)

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



dasd-eckd.a3c651 : FORMAT 9 -Device check-2 error



Severity: Warning

dasd-eckd.a4325c : 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 : 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-eckd.a77e4f : FORMAT 1 -Track physical address did not compare



Severity: Warning

dasd-eckd.a9cbd8 : FORMAT 1 -Drive motor switch is off



Severity: Warning

dasd-eckd.aac43a : FORMAT 0 -Device Fenced - device =

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.9bb776 • dasd-eckd.aac43a


dasd-eckd.ac6397 : FORMAT 1 -Index missing



Severity: Warning

dasd-eckd.acd228 : FORMAT 7 -extra RCC required



Severity: Warning

dasd-eckd.adb621 : 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 : FORMAT 4 -Data area error



Severity: Warning

dasd-eckd.b22b7e : 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 : 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 : An erroroccurred in the DASD device driver,reason=

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 : The newlyadded channel path will not be used because it leads to adifferent device

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 : The DASDcannot be reached on any path(lpum=/opm=)

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 : FORMAT 7 -Invalid tag-in for an extended commandsequence



dasd-eckd.ac6397 • dasd-eckd.b98207


Severity: Warning

dasd-eckd.bba496 : FORMAT 9- Track physical address did notcompare while oriented



Severity: Warning

dasd-eckd.bbe891 : 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.


Severity: Warning

dasd-eckd.be85b8 : 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 : 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 : 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 : FORMAT 5 -Data Check in the data area



Severity: Warning

dasd-eckd.c55c2f : Unable toallocate DCTL-CQR

Explanation: This is an internal error.

User response: Contact your support organization.

Severity: Error

dasd-eckd.c67479 : FORMAT 1 -Seek incomplete



Severity: Warning

dasd-eckd.c87cc2 : FORMAT 5 -Data Check in the key area; offset active



Severity: Warning

dasd-eckd.c9cc06 : FORMAT 1 -Device status 1 not valid



dasd-eckd.bba496 • dasd-eckd.c9cc06


Severity: Warning

dasd-eckd.c9f7f5 : FORMAT 7 -Invalid tag-in during selection sequence



Severity: Warning

dasd-eckd.ca8dfc : FORMAT 7 -Permanent path error (DASD controllernot available)



Severity: Warning

dasd-eckd.cf8d3d : FORMAT 5 -Data Check in the count area



Severity: Warning

dasd-eckd.d1a88a : 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 : FORMAT 0 -Channel requested ...

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

Kernel Messages - SUSE Linux Enterprise Server 12 SP2 · 2016. 11. 4. · specific Linux kernel...

Documents

Transcript of Kernel Messages - SUSE Linux Enterprise Server 12 SP2 · 2016. 11. 4. · specific Linux kernel...

SUSE Linux Enterprise Server 11 SP2 for IBM PowerLinux

SUSE Linux Enterprise 10 SP1: Virtualization Technology...SUSE Linux Enterprise 10 SP1: Virtualization Technology Support Upgrade Path: SUSE Linux Enterprise Server 10 to SUSE Linux

SUSE Linux iPrint Server Guide - Equitrac · PDF file• SUSE Linux Enterprise Server (SLES) 11 SP2 with Novell OES11 SP2 including iPrint support (64-bit) You must have the iPrint

PDF Compressor - Cantanhede€¦ · - Ubuntu Linux 12.04 LTS, Ubuntu Linux 13.04 - SUSE Linux Enterprise Server (SLES) 11 SP2, SLES 1 1 SP3 Suporte e garantia tecnológica. A soluçäo

SUSE Linux Toolbox - 1000+ Commands for OpenSUSE and SUSE Linux Enterprise PDF

Docker Guide - SUSE Linux Enterprise Server 12 SP2

SUSE Linux Enterprise Technology Roadmap · SAP RT RT SAP SP4 SP1 SP2 SP1 SAP. ... • Exception: SLED ... SUSE® Linux Enterprise Technology Roadmap - SUSECon 2015 ...

SuSE* Linux Enterprise Server 10 SP1 and 10 SP2 (x86 and ... · SuSE* Linux Enterprise Server 10 SP1 and 10 SP2 - Updating from Single SCM Installation to Dual SCM Installation (cont’d)

for SUSE Linux Enterprise Server 11 SP2 - OraclePillar Axiom Path Manager 3.1 Installation Guide and Release Notes for SUSE Linux Enterprise Server 11 SP2

Security Guide - SUSE Linux Enterprise Desktop 12 SP2

Quickly Configure a HA Cluster with the SUSE Linux ... · 8 Quickly Configure a HA Cluster with the SUSE Linux Enterprise HA Extension 11 SP2 Copying all or part of this manual, or

SUSE Linux Enterprise Server 11 SP2 for UEFI Clients

HP ProLiant server power management on SUSE Linux ... · PDF fileCollaborative Power Control with SLES11 SP2 ... management on SUSE Linux Enterprise Server 11 ... HP ProLiant server

Release Notes - volgafin.volgograd.ruvolgafin.volgograd.ru/information-systems/subsystem/zv… · Web viewRH Linux AS 5.5, 6 и 7. SUSe Linux 10 SP2/11. ... Suse Linux Enterprise

SUSE Linux Enterprise Server: Supported Virtualization ... · PDF fileUpgrade Path: SUSE Linux Enterprise Server 11 SP2 to SUSE Linux Enterprise Server 11 SP3. 1. Upgrade.all virtualizationhost

SUSE Linux Enterprise Server 11 Service Pack 2 ... - New CC Portal · The Target of Evaluation (TOE) is SUSE Linux Enterprise Server 11 Service Pack 2 (SLES11-SP2). SUSE Linux Enterprise

SUSE Linux Enterprise Kernel · 22 SUSE Linux Enterprise 11 SP2 Beta 4 • This was a tough challenge ‒ We were almost done with incorporating all feature changes ‒ We worked

Storage Administration Guide - SUSE Linux Enterprise Server 12 SP2

Dell Wyse SUSE LINUX Enterprise Release 11 SP2/SP3 ... Wyse... · Dell Wyse SUSE LINUX Enterprise Release 11 SP2/SP3 — Administrator’s Guide. Notes, cautions, and warnings ...

UEFI Secure Boot - SUSE Linux Secure Boot Olaf Kirch SUSE, Director SUSE Linux Enterprise [email protected] Udo Seidel Linux Strategy at Amadeus [email protected] Vojtech Pavlik SUSE,