Trying to online dasd drive results in invalid input/output from the kernel on z/VM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Critical
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Canonical Kernel |
Bug Description
SRU Justification:
==================
[Impact]
* Trying to online dasd drive results in invalid input/output from the kernel on z/VM
[Fix]
* Ignore errors from non-essential metadata reads, which may or may not be implemented by the storage server or z/VM.
[Test Case]
* Ubuntu on z/VM guest installation and selecting at least one DASD device (that's not defined as dedicated).
* Alternatively doing an Ubuntu on z/VM guest installation on zFCP/SCSI disk and manually activating a DASD device post-install with 'chzdev -e <device-number>'.
[Regression Potential]
* The kernel (aka DASD module) currently just fails on activating a (non dedicated) DASD.
* But regressions might be introduced in the DASD stack so that is fails later on LPAR installation, too - but this can easily be tested (and will be).
* The chance that zFCP/SCSI disks are harmed by accident is quite low, since this is a very different stack.
[Other Info]
* This is a regression that was introduced with the thin dasd provisioning feature that landed upstream with kernel 5.2/5.3, so affects Eoan only.
__________
Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed
Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file /sys/bus/
Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active configuration only
Sep 25 12:06:39 main-menu[421]: WARNING **: Configuring 's390-dasd' failed with error code 1
Sep 25 12:06:39 main-menu[421]: WARNING **: Menu item 's390-dasd' failed.
Sep 25 12:06:39 kernel: [ 137.472853] dasd-eckd.401b68: 0.0.0200: A channel path to the device has become operational
Sep 25 12:06:39 kernel: [ 137.473914] dasd-eckd.6b7759: 0.0.0200: Reading the volume storage information failed with rc=-5
Sep 25 12:06:39 kernel: [ 137.473917] dasd.3e7d29: 0.0.0200 Setting the DASD online with discipline ECKD failed with rc=-5
Sep 25 12:06:39 kernel: [ 137.473918] ------------[ cut here ]------------
Sep 25 12:06:39 kernel: [ 137.473943] WARNING: CPU: 0 PID: 4638 at kernel/
Sep 25 12:06:39 kernel: [ 137.473944] Modules linked in: lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod qeth_l2 pkey crc32_vx_s390 qeth qdio zcrypt_cex4 ccwgroup zcrypt
Sep 25 12:06:39 kernel: [ 137.473953] CPU: 0 PID: 4638 Comm: chzdev Not tainted 5.3.0-10-generic #11-Ubuntu
Sep 25 12:06:39 kernel: [ 137.473954] Hardware name: IBM 2964 N63 400 (z/VM 6.4.0)
Sep 25 12:06:39 kernel: [ 137.473955] Krnl PSW : 0704c00180000000 000000002b2c3372 (module_
Sep 25 12:06:39 kernel: [ 137.473958] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Sep 25 12:06:39 kernel: [ 137.473959] Krnl GPRS: 0000000000000004 0000000000000006 0000000000000024 0000000000000007
Sep 25 12:06:39 kernel: [ 137.473960] 0000000000000007 000000007f2ce800 fffffffffffffffb 000003ff80151578
Sep 25 12:06:39 kernel: [ 137.473961] 00000000fffffffb 000003ff80074df8 000003ff80151900 0000000078105800
Sep 25 12:06:39 kernel: [ 137.473962] 000000007e17e600 0000000000000bf8 000000002b2c336e 000003e000c5fb08
Sep 25 12:06:39 kernel: [ 137.473969] Krnl Code: 000000002b2c3362: c0200048859a larl %r2,2bbd3e96
Sep 25 12:06:39 kernel: [ 137.473969] 000000002b2c3368: c0e5fffe16a4 brasl %r14,2b2860b0
Sep 25 12:06:39 kernel: [ 137.473969] #000000002b2c336e: a7f40001 brc 15,2b2c3370
Sep 25 12:06:39 kernel: [ 137.473969] >000000002b2c3372: a7f4ffb1 brc 15,2b2c32d4
Sep 25 12:06:39 kernel: [ 137.473969] 000000002b2c3376: 0707 bcr 0,%r7
Sep 25 12:06:39 kernel: [ 137.473969] 000000002b2c3378: c00400000000 brcl 0,2b2c3378
Sep 25 12:06:39 kernel: [ 137.473969] 000000002b2c337e: ec280006007c cgij %r2,0,8,2b2c338a
Sep 25 12:06:39 kernel: [ 137.473969] 000000002b2c3384: c0f4ffffff86 brcl 15,2b2c3290
Sep 25 12:06:39 kernel: [ 137.473980] Call Trace:
Sep 25 12:06:39 kernel: [ 137.473982] ([<000000002b2c
Sep 25 12:06:39 kernel: [ 137.473994] [<000003ff80074
Sep 25 12:06:39 kernel: [ 137.473998] [<000003ff8007f
Sep 25 12:06:39 kernel: [ 137.474001] [<000003ff8007b
Sep 25 12:06:39 kernel: [ 137.474006] [<000000002b84d
Sep 25 12:06:39 kernel: [ 137.474008] [<000000002b84d
Sep 25 12:06:39 kernel: [ 137.474009] [<000000002b84f
Sep 25 12:06:39 kernel: [ 137.474013] [<000000002b50b
Sep 25 12:06:39 kernel: [ 137.474017] [<000000002b458
Sep 25 12:06:39 kernel: [ 137.474018] [<000000002b459
Sep 25 12:06:39 kernel: [ 137.474023] [<000000002ba4c
Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-
Sep 25 12:06:39 kernel: [ 137.474025] [<000000002b2c3
Sep 25 12:06:39 kernel: [ 137.474026] ---[ end trace 94b382399e0f8876 ]---
Cannot online a dasd drive with $ chzdev -e 0.0.0200
Possibly regression in the new kernel, due to thin provisioning patches to dasd? just a wild guess.
$ uname -a
Linux hwe0006 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:08:10 UTC 2019 s390x GNU/Linux
CVE References
tags: | added: s390x |
Changed in linux (Ubuntu): | |
status: | Incomplete → New |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
summary: |
Trying to online dasd drive results in invalid input/output from the - kernel + kernel on z/VM |
tags: | added: bot-stop-nagging |
Changed in linux (Ubuntu): | |
assignee: | nobody → Canonical Kernel (canonical-kernel) |
description: | updated |
Changed in ubuntu-z-systems: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in ubuntu-z-systems: | |
status: | Confirmed → In Progress |
tags: | added: id-5d8d330bb2bfed880c80c1da |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1845323
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.