VM devices rdr, pun and prt are not activated after restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Medium
|
Canonical Foundations Team | ||
s390-tools |
Fix Released
|
Unknown
|
|||
s390-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Cannot configure race-free generic-ccw devices to be onlined on boot.
[Test Case]
# on a z/VM
$ sudo chzdev -d 0.0.000c 0.0.000d 0.0.000e
$ sudo chzdev -e 0.0.000c 0.0.000d 0.0.000e
$ sudo update-initramfs -u
$ sudo reboot
$ lszdev
Expectations is for generic-ccw c-d-e devices to be "yes yes" meaning online and persistent online.
Previously after a reboot they would be "no yes" meaning offline yet persistent configured online.
[Regression Potential]
* generic-ccw rules need to be `upgraded` / `regenerated` which is not done in maintainer scripts in this upload for now.
[Other Info]
* fix contributed upstream at
https:/
* original bug report
Linux s390x as VM guest can use the VM-specific reader (0.0.000c), puncher (0.0.000d) and printer devices (0.0.000e).
They can be enabled as usual with chzdev like:
lszdev | grep '000c\|000d\|000e'
generic-ccw 0.0.000c no no
generic-ccw 0.0.000d no no
generic-ccw 0.0.000e no no
sudo chzdev -e 000c 000d 000e
Generic CCW device 0.0.000c configured
Generic CCW device 0.0.000d configured
Generic CCW device 0.0.000e configured
lszdev | grep '000c\|000d\|000e'
generic-ccw 0.0.000c yes yes vmrdr-0.0.000c
generic-ccw 0.0.000d yes yes vmpun-0.0.000d
generic-ccw 0.0.000e yes yes vmprt-0.0.000e
Aa a result of that activation udev rules are generated:
ls -la /etc/udev/
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-
-rw-r--r-- 1 root root 238 Sep 25 10:15 41-generic-
cat /etc/udev/
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000c", GOTO="cfg_
00c"
GOTO="end_
LABEL="
ATTR{[ccw/
LABEL="
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000d", GOTO="cfg_
00d"
GOTO="end_
LABEL="
ATTR{[ccw/
LABEL="
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000e", GOTO="cfg_
00e"
GOTO="end_
LABEL="
ATTR{[ccw/
LABEL="
Once this is done it's expected that this configuration is persistent and that these three devices are automatically activated after a reboot, which is not the case:
lszdev | grep '000c\|000d\|000e'
generic-ccw 0.0.000c no yes
generic-ccw 0.0.000d no yes
generic-ccw 0.0.000e no yes
A 'sudo udevadm trigger' doesn't help to activate them again.
Another 'sudo chzdev -e 000c 000d 000e' helps, but again for the current session only.
[
The cio_ignore list is empty, hence this can't be the reason:
cio_ignore -l
Ignored devices:
=================
$
]
Changed in ubuntu-z-systems: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
tags: | added: id-5baa55c367a0cd020990ac52 |
tags: | added: id-5baa4a4ce2d7537ba20fd8c5 |
description: | updated |
description: | updated |
Changed in ubuntu-z-systems: | |
status: | Triaged → Fix Released |
Changed in s390-tools (Ubuntu Xenial): | |
status: | New → Fix Committed |
status: | Fix Committed → In Progress |
Changed in s390-tools (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in s390-tools: | |
status: | Unknown → Fix Released |
This bug was fixed in the package s390-tools - 2.6.0-0ubuntu7
---------------
s390-tools (2.6.0-0ubuntu7) cosmic; urgency=medium
* zdev: Trigger generic_ccw devices on any kernel module loads. LP:
#1794308
-- Dimitri John Ledkov <email address hidden> Tue, 16 Oct 2018 10:23:35 +0100