[Bug 1794308] Re: VM devices rdr, pun and prt are not activated after restart
Dimitri John Ledkov
launchpad at surgut.co.uk
Tue Oct 16 11:23:22 UTC 2018
** Description changed:
+ [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]
+
+ * 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 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/rules.d/41-generic-ccw-0.0.000{c,d,e}.rules
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-ccw-0.0.000c.rules
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-ccw-0.0.000d.rules
-rw-r--r-- 1 root root 238 Sep 25 10:15 41-generic-ccw-0.0.000e.rules
cat /etc/udev/rules.d/41-generic-ccw-0.0.000{c,d,e}.rules
- # Generated by chzdev
+ # Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000c", GOTO="cfg_generic_ccw_0.0.0
- 00c"
- GOTO="end_generic_ccw_0.0.000c"
-
- LABEL="cfg_generic_ccw_0.0.000c"
- ATTR{[ccw/0.0.000c]online}="1"
-
- LABEL="end_generic_ccw_0.0.000c"
- # Generated by chzdev
+ 00c"
+ GOTO="end_generic_ccw_0.0.000c"
+
+ LABEL="cfg_generic_ccw_0.0.000c"
+ ATTR{[ccw/0.0.000c]online}="1"
+
+ LABEL="end_generic_ccw_0.0.000c"
+ # Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000d", GOTO="cfg_generic_ccw_0.0.0
- 00d"
- GOTO="end_generic_ccw_0.0.000d"
-
- LABEL="cfg_generic_ccw_0.0.000d"
- ATTR{[ccw/0.0.000d]online}="1"
-
- LABEL="end_generic_ccw_0.0.000d"
- # Generated by chzdev
+ 00d"
+ GOTO="end_generic_ccw_0.0.000d"
+
+ LABEL="cfg_generic_ccw_0.0.000d"
+ ATTR{[ccw/0.0.000d]online}="1"
+
+ LABEL="end_generic_ccw_0.0.000d"
+ # Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000e", GOTO="cfg_generic_ccw_0.0.0
- 00e"
- GOTO="end_generic_ccw_0.0.000e"
-
- LABEL="cfg_generic_ccw_0.0.000e"
- ATTR{[ccw/0.0.000e]online}="1"
-
- LABEL="end_generic_ccw_0.0.000e"
+ 00e"
+ GOTO="end_generic_ccw_0.0.000e"
+
+ LABEL="cfg_generic_ccw_0.0.000e"
+ ATTR{[ccw/0.0.000e]online}="1"
+
+ LABEL="end_generic_ccw_0.0.000e"
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:
+ cio_ignore -l
+ Ignored devices:
=================
$
]
** Description changed:
[Impact]
- * Cannot configure race-free generic-ccw devices to be onlined on boot.
+ * 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
+ * generic-ccw rules need to be `upgraded` / `regenerated` which is not
done in maintainer scripts in this upload for now.
[Other Info]
-
- * original bug report
+
+ * fix contributed upstream at
+
+ https://github.com/ibm-s390-tools/s390-tools/pull/45/files
+
+ * 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/rules.d/41-generic-ccw-0.0.000{c,d,e}.rules
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-ccw-0.0.000c.rules
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-ccw-0.0.000d.rules
-rw-r--r-- 1 root root 238 Sep 25 10:15 41-generic-ccw-0.0.000e.rules
cat /etc/udev/rules.d/41-generic-ccw-0.0.000{c,d,e}.rules
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000c", GOTO="cfg_generic_ccw_0.0.0
00c"
GOTO="end_generic_ccw_0.0.000c"
LABEL="cfg_generic_ccw_0.0.000c"
ATTR{[ccw/0.0.000c]online}="1"
LABEL="end_generic_ccw_0.0.000c"
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000d", GOTO="cfg_generic_ccw_0.0.0
00d"
GOTO="end_generic_ccw_0.0.000d"
LABEL="cfg_generic_ccw_0.0.000d"
ATTR{[ccw/0.0.000d]online}="1"
LABEL="end_generic_ccw_0.0.000d"
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000e", GOTO="cfg_generic_ccw_0.0.0
00e"
GOTO="end_generic_ccw_0.0.000e"
LABEL="cfg_generic_ccw_0.0.000e"
ATTR{[ccw/0.0.000e]online}="1"
LABEL="end_generic_ccw_0.0.000e"
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:
=================
$
]
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to s390-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1794308
Title:
VM devices rdr, pun and prt are not activated after restart
Status in s390-tools:
Unknown
Status in Ubuntu on IBM z Systems:
Triaged
Status in s390-tools package in Ubuntu:
New
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://github.com/ibm-s390-tools/s390-tools/pull/45/files
* 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/rules.d/41-generic-ccw-0.0.000{c,d,e}.rules
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-ccw-0.0.000c.rules
-rw-r--r-- 1 root root 238 Sep 21 06:24 41-generic-ccw-0.0.000d.rules
-rw-r--r-- 1 root root 238 Sep 25 10:15 41-generic-ccw-0.0.000e.rules
cat /etc/udev/rules.d/41-generic-ccw-0.0.000{c,d,e}.rules
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000c", GOTO="cfg_generic_ccw_0.0.0
00c"
GOTO="end_generic_ccw_0.0.000c"
LABEL="cfg_generic_ccw_0.0.000c"
ATTR{[ccw/0.0.000c]online}="1"
LABEL="end_generic_ccw_0.0.000c"
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000d", GOTO="cfg_generic_ccw_0.0.0
00d"
GOTO="end_generic_ccw_0.0.000d"
LABEL="cfg_generic_ccw_0.0.000d"
ATTR{[ccw/0.0.000d]online}="1"
LABEL="end_generic_ccw_0.0.000d"
# Generated by chzdev
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.000e", GOTO="cfg_generic_ccw_0.0.0
00e"
GOTO="end_generic_ccw_0.0.000e"
LABEL="cfg_generic_ccw_0.0.000e"
ATTR{[ccw/0.0.000e]online}="1"
LABEL="end_generic_ccw_0.0.000e"
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:
=================
$
]
To manage notifications about this bug go to:
https://bugs.launchpad.net/s390-tools/+bug/1794308/+subscriptions
More information about the foundations-bugs
mailing list