[Kernel-packages] [Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
This patch fixes a segfault seen when attaching to a process on Solaris. The steps leading to the segfault are: http://www.compilatori.com/tech/xiaomi/ - procfs_target::attach calls do_attach, at this point the inferior's process slot in the target stack is empty. - do_attach adds a thread with `add http://www.acpirateradio.co.uk/tech/forest-fires/ _thread (_procfs_target, ptid)` - in add_thread_silent, the passed target (_procfs_target) is passed to find_inferior_ptid http://www.logoarts.co.uk/tech/drone-cameras/ - find_inferior_ptid returns nullptr, as there is no inferior with this ptid that has _procfs_target as its process target http://www.slipstone.co.uk/tech/express-van/ - the nullptr `inf` is passed to find_thread_ptid, which dereferences it, causing a segfault - back in procfs_target::attach, after do_attach, we push the http://embermanchester.uk/technology/telegram/ the_procfs_target on the inferior's target stack, although we never reach this because the segfault happens before. http://connstr.net/tech/mars-surface/ To fix this, I think we need to do the same as is done in inf_ptrace_target::attach: push the target early and unpush it in case the attach fails (and keep it if the attach succeeds). http://joerg.li/tech/cars-comparison/ Implement it by moving target_unpush_up to target.h, so it can be re-used here. Make procfs_target::attach use it. Note that just like is mentioned http://www.jopspeech.com/tech/xiaomi-headset/ in inf_ptrace_target::attach, we should push the target before calling target_pid_to_str, so that calling target_pid_to_str ends up in procfs_target::pid_to_str. http://www.wearelondonmade.com/tech/driving-assistant/ Tested by trying to attach on a process on gcc211 on the gcc compile farm. https://waytowhatsnext.com/health/vaccination-rates/ gdb/ChangeLog: This patch fixes a segfault seen when attaching to a process on Solaris. The steps leading to the segfault are: http://www.iu-bloomington.com/health/amoled-display/ - procfs_target::attach calls do_attach, at this point the inferior's process slot in the target stack is empty. https://komiya-dental.com/health/telegram-account/ - do_attach adds a thread with `add_thread (_procfs_target, ptid)` - in add_thread_silent, the passed target (_procfs_target) is passed to find_inferior_ptid http://www-look-4.com/services/usb-type-a/ - find_inferior_ptid returns nullptr, as there is no inferior with this ptid that has _procfs_target as its process target - the nullptr `inf` is passed to find_thread_ptid, which dereferences it, causing a segfault https://www.webb-dev.co.uk/property/house-sales-in-2020/ - back in procfs_target::attach, after do_attach, we push the the_procfs_target on the inferior's target stack, although we never reach this because the segfault happens before. To fix this, I think we need to do the same as is done in inf_ptrace_target::attach: push the target early and unpush it in case the attach fails (and keep it if the attach succeeds). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876011 Title: Kernel Panic when dasd-fba device is selected for install Status in curtin: Fix Released Status in subiquity: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Stating a zVM install (either subiquity or d-i) and selecting dasd-fba devices leads to a kernel panic. Details from the installer shell before the panic: root@ubuntu-server:/# uname -a Linux ubuntu-server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux root@ubuntu-server:/# cat /proc/cmdline ip=10.245.208.13::10.245.208.1:255.255.255.0:s5lp1-gen03:enc600:none:10.245.208.1 url=ftp://10.13.0.2:21/ubuntu-live-server-20.04/focal-live-server-s390x.iso http_proxy=http://91.189.89.11:3128 --- quiet root@ubuntu-server:/# root@ubuntu-server:/# lsmod Module Size Used by dm_multipath 40960 0 scsi_dh_rdac 20480 0 scsi_dh_emc16384 0 scsi_dh_alua 24576 0 vmur 20480 0 vfio_ccw 36864 0 vfio_mdev 16384 0 mdev 28672 2 vfio_ccw,vfio_mdev vfio_iommu_type1 32768 0 vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1 sch_fq_codel 20480 1 drm 499712 0 drm_panel_orientation_quirks16384 1 drm i2c_core 77824 1 drm ip_tables 32768 0 x_tables 45056 1 ip_tables overlay 135168 1 nls_utf8
[Kernel-packages] [Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
This bug is fixed with
https://github.com/CanonicalLtd/subiquity/releases/tag/21.01.1
for Ubuntu releases H, G and F.
** Changed in: subiquity
Status: In Progress => Fix Released
** Changed in: curtin
Status: Incomplete => Fix Released
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876011
Title:
Kernel Panic when dasd-fba device is selected for install
Status in curtin:
Fix Released
Status in subiquity:
Fix Released
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Stating a zVM install (either subiquity or d-i) and selecting dasd-fba
devices leads to a kernel panic.
Details from the installer shell before the panic:
root@ubuntu-server:/# uname -a
Linux ubuntu-server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC
2020 s390x s390x s390x GNU/Linux
root@ubuntu-server:/# cat /proc/cmdline
ip=10.245.208.13::10.245.208.1:255.255.255.0:s5lp1-gen03:enc600:none:10.245.208.1
url=ftp://10.13.0.2:21/ubuntu-live-server-20.04/focal-live-server-s390x.iso
http_proxy=http://91.189.89.11:3128 --- quiet
root@ubuntu-server:/#
root@ubuntu-server:/# lsmod
Module Size Used by
dm_multipath 40960 0
scsi_dh_rdac 20480 0
scsi_dh_emc16384 0
scsi_dh_alua 24576 0
vmur 20480 0
vfio_ccw 36864 0
vfio_mdev 16384 0
mdev 28672 2 vfio_ccw,vfio_mdev
vfio_iommu_type1 32768 0
vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1
sch_fq_codel 20480 1
drm 499712 0
drm_panel_orientation_quirks16384 1 drm
i2c_core 77824 1 drm
ip_tables 32768 0
x_tables 45056 1 ip_tables
overlay 135168 1
nls_utf8 16384 1
isofs 49152 1
qeth_l245056 1
lcs53248 0
zfcp 126976 0
scsi_transport_fc 69632 1 zfcp
raid10 65536 0
raid456 180224 0
async_raid6_recov 20480 1 raid456
async_memcpy 20480 1 raid456
async_pq 20480 1 raid456
async_xor 20480 2 async_pq,raid456
async_tx 20480 5
async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor16384 1 async_xor
raid6_pq 102400 3 async_pq,raid456,async_raid6_recov
libcrc32c 16384 1 raid456
raid1 53248 0
raid0 28672 0
linear 20480 0
pkey 32768 0
crc32_vx_s390 16384 1
ghash_s390 16384 0
prng 20480 4
aes_s390 28672 0
des_s390 20480 0
libdes 28672 1 des_s390
sha512_s39016384 0
sha256_s39016384 0
sha1_s390 16384 0
sha_common 16384 3 sha512_s390,sha256_s390,sha1_s390
qeth 135168 1 qeth_l2
dasd_fba_mod 24576 0
dasd_eckd_mod 131072 0
qdio 61440 3 qeth,zfcp,qeth_l2
ccwgroup 20480 3 qeth,lcs,qeth_l2
dasd_mod 143360 2 dasd_eckd_mod,dasd_fba_mod
zcrypt_cex420480 0
zcrypt106496 2 pkey,zcrypt_cex4
root@ubuntu-server:/# dmesg | tail
[ 34.458754] audit: type=1400 audit(1588204779.286:14): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="snap.subiquity.subiquity-service" pid=1789 comm="apparmor_parser"
[ 190.647685] ctcm.151d85: CTCM driver initialized
[ 190.663097] dasd-fba.f36f2f: 0.0.0101: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 190.664748] dasda: dasda1
[ 193.364797] dasd-fba.f36f2f: 0.0.0102: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 193.366573] dasdb:(nonl) dasdb1
[ 195.743686] dasd-fba.f36f2f: 0.0.0103: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 195.745327] dasdc:(nonl) dasdc1
[ 198.408631] dasd-fba.f36f2f: 0.0.0104: New FBA DASD 9336/10 (CU 6310/80)
with 16384 MB and 512 B/blk
[ 198.411231] dasdd:(nonl) dasdd1
Dropped to shell after partition confirmation to run tail on syslog
root@ubuntu-server:/# tail -f /var/log/syslog
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: Shutdown Plan:
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 6, 'device':
'/sys/class/block/dm-0', 'dev_type': 'lvm'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 4, 'device':
'/sys/class/block/dasda/dasda1', 'dev_type': 'partition'}
Apr 30 00:10:08 ubuntu-server
[Kernel-packages] [Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876011
Title:
Kernel Panic when dasd-fba device is selected for install
Status in curtin:
Incomplete
Status in subiquity:
In Progress
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Bug description:
Stating a zVM install (either subiquity or d-i) and selecting dasd-fba
devices leads to a kernel panic.
Details from the installer shell before the panic:
root@ubuntu-server:/# uname -a
Linux ubuntu-server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC
2020 s390x s390x s390x GNU/Linux
root@ubuntu-server:/# cat /proc/cmdline
ip=10.245.208.13::10.245.208.1:255.255.255.0:s5lp1-gen03:enc600:none:10.245.208.1
url=ftp://10.13.0.2:21/ubuntu-live-server-20.04/focal-live-server-s390x.iso
http_proxy=http://91.189.89.11:3128 --- quiet
root@ubuntu-server:/#
root@ubuntu-server:/# lsmod
Module Size Used by
dm_multipath 40960 0
scsi_dh_rdac 20480 0
scsi_dh_emc16384 0
scsi_dh_alua 24576 0
vmur 20480 0
vfio_ccw 36864 0
vfio_mdev 16384 0
mdev 28672 2 vfio_ccw,vfio_mdev
vfio_iommu_type1 32768 0
vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1
sch_fq_codel 20480 1
drm 499712 0
drm_panel_orientation_quirks16384 1 drm
i2c_core 77824 1 drm
ip_tables 32768 0
x_tables 45056 1 ip_tables
overlay 135168 1
nls_utf8 16384 1
isofs 49152 1
qeth_l245056 1
lcs53248 0
zfcp 126976 0
scsi_transport_fc 69632 1 zfcp
raid10 65536 0
raid456 180224 0
async_raid6_recov 20480 1 raid456
async_memcpy 20480 1 raid456
async_pq 20480 1 raid456
async_xor 20480 2 async_pq,raid456
async_tx 20480 5
async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor16384 1 async_xor
raid6_pq 102400 3 async_pq,raid456,async_raid6_recov
libcrc32c 16384 1 raid456
raid1 53248 0
raid0 28672 0
linear 20480 0
pkey 32768 0
crc32_vx_s390 16384 1
ghash_s390 16384 0
prng 20480 4
aes_s390 28672 0
des_s390 20480 0
libdes 28672 1 des_s390
sha512_s39016384 0
sha256_s39016384 0
sha1_s390 16384 0
sha_common 16384 3 sha512_s390,sha256_s390,sha1_s390
qeth 135168 1 qeth_l2
dasd_fba_mod 24576 0
dasd_eckd_mod 131072 0
qdio 61440 3 qeth,zfcp,qeth_l2
ccwgroup 20480 3 qeth,lcs,qeth_l2
dasd_mod 143360 2 dasd_eckd_mod,dasd_fba_mod
zcrypt_cex420480 0
zcrypt106496 2 pkey,zcrypt_cex4
root@ubuntu-server:/# dmesg | tail
[ 34.458754] audit: type=1400 audit(1588204779.286:14): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="snap.subiquity.subiquity-service" pid=1789 comm="apparmor_parser"
[ 190.647685] ctcm.151d85: CTCM driver initialized
[ 190.663097] dasd-fba.f36f2f: 0.0.0101: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 190.664748] dasda: dasda1
[ 193.364797] dasd-fba.f36f2f: 0.0.0102: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 193.366573] dasdb:(nonl) dasdb1
[ 195.743686] dasd-fba.f36f2f: 0.0.0103: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 195.745327] dasdc:(nonl) dasdc1
[ 198.408631] dasd-fba.f36f2f: 0.0.0104: New FBA DASD 9336/10 (CU 6310/80)
with 16384 MB and 512 B/blk
[ 198.411231] dasdd:(nonl) dasdd1
Dropped to shell after partition confirmation to run tail on syslog
root@ubuntu-server:/# tail -f /var/log/syslog
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: Shutdown Plan:
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 6, 'device':
'/sys/class/block/dm-0', 'dev_type': 'lvm'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 4, 'device':
'/sys/class/block/dasda/dasda1', 'dev_type': 'partition'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 2, 'device':
'/sys/class/block/dasda', 'dev_type': 'disk'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: shutdown running on
holder type: 'lvm' syspath: '/sys/class/block/dm-0'
Apr 30 00:10:08 ubuntu-server
[Kernel-packages] [Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
** Changed in: subiquity
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876011
Title:
Kernel Panic when dasd-fba device is selected for install
Status in curtin:
Incomplete
Status in subiquity:
In Progress
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Fix Released
Bug description:
Stating a zVM install (either subiquity or d-i) and selecting dasd-fba
devices leads to a kernel panic.
Details from the installer shell before the panic:
root@ubuntu-server:/# uname -a
Linux ubuntu-server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC
2020 s390x s390x s390x GNU/Linux
root@ubuntu-server:/# cat /proc/cmdline
ip=10.245.208.13::10.245.208.1:255.255.255.0:s5lp1-gen03:enc600:none:10.245.208.1
url=ftp://10.13.0.2:21/ubuntu-live-server-20.04/focal-live-server-s390x.iso
http_proxy=http://91.189.89.11:3128 --- quiet
root@ubuntu-server:/#
root@ubuntu-server:/# lsmod
Module Size Used by
dm_multipath 40960 0
scsi_dh_rdac 20480 0
scsi_dh_emc16384 0
scsi_dh_alua 24576 0
vmur 20480 0
vfio_ccw 36864 0
vfio_mdev 16384 0
mdev 28672 2 vfio_ccw,vfio_mdev
vfio_iommu_type1 32768 0
vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1
sch_fq_codel 20480 1
drm 499712 0
drm_panel_orientation_quirks16384 1 drm
i2c_core 77824 1 drm
ip_tables 32768 0
x_tables 45056 1 ip_tables
overlay 135168 1
nls_utf8 16384 1
isofs 49152 1
qeth_l245056 1
lcs53248 0
zfcp 126976 0
scsi_transport_fc 69632 1 zfcp
raid10 65536 0
raid456 180224 0
async_raid6_recov 20480 1 raid456
async_memcpy 20480 1 raid456
async_pq 20480 1 raid456
async_xor 20480 2 async_pq,raid456
async_tx 20480 5
async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor16384 1 async_xor
raid6_pq 102400 3 async_pq,raid456,async_raid6_recov
libcrc32c 16384 1 raid456
raid1 53248 0
raid0 28672 0
linear 20480 0
pkey 32768 0
crc32_vx_s390 16384 1
ghash_s390 16384 0
prng 20480 4
aes_s390 28672 0
des_s390 20480 0
libdes 28672 1 des_s390
sha512_s39016384 0
sha256_s39016384 0
sha1_s390 16384 0
sha_common 16384 3 sha512_s390,sha256_s390,sha1_s390
qeth 135168 1 qeth_l2
dasd_fba_mod 24576 0
dasd_eckd_mod 131072 0
qdio 61440 3 qeth,zfcp,qeth_l2
ccwgroup 20480 3 qeth,lcs,qeth_l2
dasd_mod 143360 2 dasd_eckd_mod,dasd_fba_mod
zcrypt_cex420480 0
zcrypt106496 2 pkey,zcrypt_cex4
root@ubuntu-server:/# dmesg | tail
[ 34.458754] audit: type=1400 audit(1588204779.286:14): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="snap.subiquity.subiquity-service" pid=1789 comm="apparmor_parser"
[ 190.647685] ctcm.151d85: CTCM driver initialized
[ 190.663097] dasd-fba.f36f2f: 0.0.0101: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 190.664748] dasda: dasda1
[ 193.364797] dasd-fba.f36f2f: 0.0.0102: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 193.366573] dasdb:(nonl) dasdb1
[ 195.743686] dasd-fba.f36f2f: 0.0.0103: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 195.745327] dasdc:(nonl) dasdc1
[ 198.408631] dasd-fba.f36f2f: 0.0.0104: New FBA DASD 9336/10 (CU 6310/80)
with 16384 MB and 512 B/blk
[ 198.411231] dasdd:(nonl) dasdd1
Dropped to shell after partition confirmation to run tail on syslog
root@ubuntu-server:/# tail -f /var/log/syslog
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: Shutdown Plan:
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 6, 'device':
'/sys/class/block/dm-0', 'dev_type': 'lvm'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 4, 'device':
'/sys/class/block/dasda/dasda1', 'dev_type': 'partition'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 2, 'device':
'/sys/class/block/dasda', 'dev_type': 'disk'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: shutdown running on
holder type: 'lvm' syspath: '/sys/class/block/dm-0'
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: Running
[Kernel-packages] [Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
Checking the focal git tree this is included in the Ubuntu kernels:
Ubuntu-5.4.0-55.61
Ubuntu-5.4.0-56.62
Ubuntu-5.4.0-57.63
And Ubuntu-5.4.0-56 just migrated to updates:
linux-generic | 5.4.0.56.59 | focal-updates | s390x
hence I'm updating this (focal) to Fix Released.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876011
Title:
Kernel Panic when dasd-fba device is selected for install
Status in curtin:
Incomplete
Status in subiquity:
New
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Fix Released
Bug description:
Stating a zVM install (either subiquity or d-i) and selecting dasd-fba
devices leads to a kernel panic.
Details from the installer shell before the panic:
root@ubuntu-server:/# uname -a
Linux ubuntu-server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC
2020 s390x s390x s390x GNU/Linux
root@ubuntu-server:/# cat /proc/cmdline
ip=10.245.208.13::10.245.208.1:255.255.255.0:s5lp1-gen03:enc600:none:10.245.208.1
url=ftp://10.13.0.2:21/ubuntu-live-server-20.04/focal-live-server-s390x.iso
http_proxy=http://91.189.89.11:3128 --- quiet
root@ubuntu-server:/#
root@ubuntu-server:/# lsmod
Module Size Used by
dm_multipath 40960 0
scsi_dh_rdac 20480 0
scsi_dh_emc16384 0
scsi_dh_alua 24576 0
vmur 20480 0
vfio_ccw 36864 0
vfio_mdev 16384 0
mdev 28672 2 vfio_ccw,vfio_mdev
vfio_iommu_type1 32768 0
vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1
sch_fq_codel 20480 1
drm 499712 0
drm_panel_orientation_quirks16384 1 drm
i2c_core 77824 1 drm
ip_tables 32768 0
x_tables 45056 1 ip_tables
overlay 135168 1
nls_utf8 16384 1
isofs 49152 1
qeth_l245056 1
lcs53248 0
zfcp 126976 0
scsi_transport_fc 69632 1 zfcp
raid10 65536 0
raid456 180224 0
async_raid6_recov 20480 1 raid456
async_memcpy 20480 1 raid456
async_pq 20480 1 raid456
async_xor 20480 2 async_pq,raid456
async_tx 20480 5
async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor16384 1 async_xor
raid6_pq 102400 3 async_pq,raid456,async_raid6_recov
libcrc32c 16384 1 raid456
raid1 53248 0
raid0 28672 0
linear 20480 0
pkey 32768 0
crc32_vx_s390 16384 1
ghash_s390 16384 0
prng 20480 4
aes_s390 28672 0
des_s390 20480 0
libdes 28672 1 des_s390
sha512_s39016384 0
sha256_s39016384 0
sha1_s390 16384 0
sha_common 16384 3 sha512_s390,sha256_s390,sha1_s390
qeth 135168 1 qeth_l2
dasd_fba_mod 24576 0
dasd_eckd_mod 131072 0
qdio 61440 3 qeth,zfcp,qeth_l2
ccwgroup 20480 3 qeth,lcs,qeth_l2
dasd_mod 143360 2 dasd_eckd_mod,dasd_fba_mod
zcrypt_cex420480 0
zcrypt106496 2 pkey,zcrypt_cex4
root@ubuntu-server:/# dmesg | tail
[ 34.458754] audit: type=1400 audit(1588204779.286:14): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="snap.subiquity.subiquity-service" pid=1789 comm="apparmor_parser"
[ 190.647685] ctcm.151d85: CTCM driver initialized
[ 190.663097] dasd-fba.f36f2f: 0.0.0101: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 190.664748] dasda: dasda1
[ 193.364797] dasd-fba.f36f2f: 0.0.0102: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 193.366573] dasdb:(nonl) dasdb1
[ 195.743686] dasd-fba.f36f2f: 0.0.0103: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[ 195.745327] dasdc:(nonl) dasdc1
[ 198.408631] dasd-fba.f36f2f: 0.0.0104: New FBA DASD 9336/10 (CU 6310/80)
with 16384 MB and 512 B/blk
[ 198.411231] dasdd:(nonl) dasdd1
Dropped to shell after partition confirmation to run tail on syslog
root@ubuntu-server:/# tail -f /var/log/syslog
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: Shutdown Plan:
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 6, 'device':
'/sys/class/block/dm-0', 'dev_type': 'lvm'}
Apr 30 00:10:08 ubuntu-server curtin_log.2234[2946]: {'level': 4, 'device':
