Activity log for bug #1845323

Date Who What changed Old value New value Message
2019-09-25 13:00:42 Dimitri John Ledkov bug added bug
2019-09-25 13:03:02 Dimitri John Ledkov attachment added dasd-log.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845323/+attachment/5291135/+files/dasd-log.txt
2019-09-25 13:04:42 Frank Heimes tags s390x
2019-09-25 13:30:08 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2019-09-25 13:30:10 Ubuntu Kernel Bot tags s390x eoan s390x
2019-09-26 07:35:54 Frank Heimes linux (Ubuntu): status Incomplete New
2019-09-26 08:00:09 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2019-09-26 09:37:53 Frank Heimes linux (Ubuntu): status Incomplete Confirmed
2019-09-26 11:05:30 Dimitri John Ledkov summary Trying to online dasd drive results in invalid input/output from the kernel Trying to online dasd drive results in invalid input/output from the kernel on z/VM
2019-09-26 11:05:45 Dimitri John Ledkov tags eoan s390x bot-stop-nagging eoan s390x
2019-09-26 11:05:55 Dimitri John Ledkov linux (Ubuntu): assignee Canonical Kernel (canonical-kernel)
2019-09-26 17:21:18 Frank Heimes description 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/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error 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/module.c:1137 module_put.part.0+0xe2/0xe8 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_put.part.0+0xe2/0xe8) 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] ([<000000002b2c336e>] module_put.part.0+0xde/0xe8) Sep 25 12:06:39 kernel: [ 137.473994] [<000003ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.473998] [<000003ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474001] [<000003ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474006] [<000000002b84db48>] ccw_device_set_online+0x110/0x528 Sep 25 12:06:39 kernel: [ 137.474008] [<000000002b84dfb0>] online_store_recog_and_online+0x50/0x130 Sep 25 12:06:39 kernel: [ 137.474009] [<000000002b84f042>] online_store+0x1b2/0x2e0 Sep 25 12:06:39 kernel: [ 137.474013] [<000000002b50b7a0>] kernfs_fop_write+0xd8/0x1f8 Sep 25 12:06:39 kernel: [ 137.474017] [<000000002b4585f8>] vfs_write+0xb0/0x1b8 Sep 25 12:06:39 kernel: [ 137.474018] [<000000002b459eb8>] ksys_write+0x68/0xf8 Sep 25 12:06:39 kernel: [ 137.474023] [<000000002ba4c4b8>] system_call+0xdc/0x2c8 Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-Event-Address: Sep 25 12:06:39 kernel: [ 137.474025] [<000000002b2c336e>] module_put.part.0+0xde/0xe8 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 SRU Justification: ================== [Impact] * Trying to online dasd drive results in invalid input/output from the kernel on z/VM [Fix] * ? TODO - hopefully patch attached ? [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/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error 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/module.c:1137 module_put.part.0+0xe2/0xe8 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_put.part.0+0xe2/0xe8) 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] ([<000000002b2c336e>] module_put.part.0+0xde/0xe8) Sep 25 12:06:39 kernel: [ 137.473994] [<000003ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.473998] [<000003ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474001] [<000003ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474006] [<000000002b84db48>] ccw_device_set_online+0x110/0x528 Sep 25 12:06:39 kernel: [ 137.474008] [<000000002b84dfb0>] online_store_recog_and_online+0x50/0x130 Sep 25 12:06:39 kernel: [ 137.474009] [<000000002b84f042>] online_store+0x1b2/0x2e0 Sep 25 12:06:39 kernel: [ 137.474013] [<000000002b50b7a0>] kernfs_fop_write+0xd8/0x1f8 Sep 25 12:06:39 kernel: [ 137.474017] [<000000002b4585f8>] vfs_write+0xb0/0x1b8 Sep 25 12:06:39 kernel: [ 137.474018] [<000000002b459eb8>] ksys_write+0x68/0xf8 Sep 25 12:06:39 kernel: [ 137.474023] [<000000002ba4c4b8>] system_call+0xdc/0x2c8 Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-Event-Address: Sep 25 12:06:39 kernel: [ 137.474025] [<000000002b2c336e>] module_put.part.0+0xde/0xe8 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
2019-09-27 07:54:21 Frank Heimes bug task added ubuntu-z-systems
2019-09-27 07:54:27 Frank Heimes ubuntu-z-systems: status New Confirmed
2019-09-27 07:55:16 Frank Heimes ubuntu-z-systems: importance Undecided Critical
2019-09-27 13:15:18 Christian Borntraeger attachment added testpatch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845323/+attachment/5291775/+files/0001-s390-dasd-Fix-error-handling-during-online-processin.patch
2019-09-27 13:41:06 Dimitri John Ledkov description SRU Justification: ================== [Impact] * Trying to online dasd drive results in invalid input/output from the kernel on z/VM [Fix] * ? TODO - hopefully patch attached ? [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/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error 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/module.c:1137 module_put.part.0+0xe2/0xe8 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_put.part.0+0xe2/0xe8) 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] ([<000000002b2c336e>] module_put.part.0+0xde/0xe8) Sep 25 12:06:39 kernel: [ 137.473994] [<000003ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.473998] [<000003ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474001] [<000003ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474006] [<000000002b84db48>] ccw_device_set_online+0x110/0x528 Sep 25 12:06:39 kernel: [ 137.474008] [<000000002b84dfb0>] online_store_recog_and_online+0x50/0x130 Sep 25 12:06:39 kernel: [ 137.474009] [<000000002b84f042>] online_store+0x1b2/0x2e0 Sep 25 12:06:39 kernel: [ 137.474013] [<000000002b50b7a0>] kernfs_fop_write+0xd8/0x1f8 Sep 25 12:06:39 kernel: [ 137.474017] [<000000002b4585f8>] vfs_write+0xb0/0x1b8 Sep 25 12:06:39 kernel: [ 137.474018] [<000000002b459eb8>] ksys_write+0x68/0xf8 Sep 25 12:06:39 kernel: [ 137.474023] [<000000002ba4c4b8>] system_call+0xdc/0x2c8 Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-Event-Address: Sep 25 12:06:39 kernel: [ 137.474025] [<000000002b2c336e>] module_put.part.0+0xde/0xe8 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 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/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error 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/module.c:1137 module_put.part.0+0xe2/0xe8 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_put.part.0+0xe2/0xe8) 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] ([<000000002b2c336e>] module_put.part.0+0xde/0xe8) Sep 25 12:06:39 kernel: [ 137.473994] [<000003ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.473998] [<000003ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474001] [<000003ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474006] [<000000002b84db48>] ccw_device_set_online+0x110/0x528 Sep 25 12:06:39 kernel: [ 137.474008] [<000000002b84dfb0>] online_store_recog_and_online+0x50/0x130 Sep 25 12:06:39 kernel: [ 137.474009] [<000000002b84f042>] online_store+0x1b2/0x2e0 Sep 25 12:06:39 kernel: [ 137.474013] [<000000002b50b7a0>] kernfs_fop_write+0xd8/0x1f8 Sep 25 12:06:39 kernel: [ 137.474017] [<000000002b4585f8>] vfs_write+0xb0/0x1b8 Sep 25 12:06:39 kernel: [ 137.474018] [<000000002b459eb8>] ksys_write+0x68/0xf8 Sep 25 12:06:39 kernel: [ 137.474023] [<000000002ba4c4b8>] system_call+0xdc/0x2c8 Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-Event-Address: Sep 25 12:06:39 kernel: [ 137.474025] [<000000002b2c336e>] module_put.part.0+0xde/0xe8 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
2019-09-27 15:47:41 Dimitri John Ledkov linux (Ubuntu): importance Undecided High
2019-09-27 16:32:03 Frank Heimes linux (Ubuntu): status Confirmed In Progress
2019-09-27 16:32:08 Frank Heimes ubuntu-z-systems: status Confirmed In Progress
2019-10-01 12:43:34 Francis Ginther tags bot-stop-nagging eoan s390x bot-stop-nagging eoan id-5d8d330bb2bfed880c80c1da s390x
2019-10-01 15:45:35 Stefan Haberland attachment added 0001-s390-dasd-Fix-error-handling-during-online-processin.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845323/+attachment/5293211/+files/0001-s390-dasd-Fix-error-handling-during-online-processin.patch
2019-10-07 07:18:19 Frank Heimes linux (Ubuntu): status In Progress Fix Committed
2019-10-07 07:18:27 Frank Heimes ubuntu-z-systems: status In Progress Fix Committed
2019-10-07 08:34:06 Frank Heimes attachment added verification of eoan proposed kernel.txt https://bugs.launchpad.net/ubuntu-z-systems/+bug/1845323/+attachment/5295059/+files/verification%20of%20eoan%20proposed%20kernel.txt
2019-10-10 07:11:11 Launchpad Janitor linux (Ubuntu): status Fix Committed Fix Released
2019-10-10 07:11:11 Launchpad Janitor cve linked 2019-15098
2019-10-10 07:11:11 Launchpad Janitor cve linked 2019-17052
2019-10-10 07:11:11 Launchpad Janitor cve linked 2019-17053
2019-10-10 07:11:11 Launchpad Janitor cve linked 2019-17054
2019-10-10 07:11:11 Launchpad Janitor cve linked 2019-17055
2019-10-10 07:11:11 Launchpad Janitor cve linked 2019-17056
2019-10-10 07:26:58 Frank Heimes ubuntu-z-systems: status Fix Committed Fix Released