| 2018-09-25 14:43:31 |
Frank Heimes |
bug |
|
|
added bug |
| 2018-09-25 14:43:39 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2018-09-25 14:43:46 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
Medium |
|
| 2018-09-25 14:49:19 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Canonical Foundations Team (canonical-foundations) |
|
| 2018-09-26 12:23:41 |
Francis Ginther |
tags |
|
id-5baa55c367a0cd020990ac52 |
|
| 2018-09-26 12:35:46 |
Francis Ginther |
tags |
id-5baa55c367a0cd020990ac52 |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 |
|
| 2018-09-26 15:59:15 |
Dimitri John Ledkov |
bug task added |
|
s390-tools (Ubuntu) |
|
| 2018-09-26 16:00:07 |
Dimitri John Ledkov |
bug watch added |
|
https://github.com/ibm-s390-tools/s390-tools/issues/37 |
|
| 2018-09-26 16:00:07 |
Dimitri John Ledkov |
bug task added |
|
s390-tools |
|
| 2018-10-16 11:23:22 |
Dimitri John Ledkov |
description |
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:
=================
$
] |
[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 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:
=================
$
] |
|
| 2018-10-16 11:26:01 |
Dimitri John Ledkov |
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]
* 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:
=================
$
] |
[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:
=================
$
] |
|
| 2018-10-16 12:52:16 |
Launchpad Janitor |
s390-tools (Ubuntu): status |
New |
Fix Released |
|
| 2018-10-16 13:40:00 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
Fix Released |
|
| 2018-10-22 11:41:54 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-10-22 11:41:54 |
Dimitri John Ledkov |
bug task added |
|
s390-tools (Ubuntu Xenial) |
|
| 2018-10-22 11:41:54 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-10-22 11:41:54 |
Dimitri John Ledkov |
bug task added |
|
s390-tools (Ubuntu Bionic) |
|
| 2018-10-22 11:42:25 |
Dimitri John Ledkov |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-10-22 11:55:52 |
Dimitri John Ledkov |
s390-tools (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2018-10-22 11:55:55 |
Dimitri John Ledkov |
s390-tools (Ubuntu Xenial): status |
Fix Committed |
In Progress |
|
| 2018-10-22 11:55:59 |
Dimitri John Ledkov |
s390-tools (Ubuntu Bionic): status |
New |
In Progress |
|
| 2018-10-23 13:29:44 |
Brian Murray |
s390-tools (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2018-10-23 13:29:47 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2018-10-23 13:29:49 |
Brian Murray |
tags |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-needed verification-needed-xenial |
|
| 2018-10-23 13:31:36 |
Brian Murray |
s390-tools (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-10-23 13:31:42 |
Brian Murray |
tags |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-needed verification-needed-xenial |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-needed verification-needed-bionic verification-needed-xenial |
|
| 2018-10-23 17:05:30 |
Frank Heimes |
attachment added |
|
verification_on_xenial.txt https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794308/+attachment/5204594/+files/verification_on_xenial.txt |
|
| 2018-10-23 17:05:49 |
Frank Heimes |
tags |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-needed verification-needed-bionic verification-needed-xenial |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-done-xenial verification-needed verification-needed-bionic |
|
| 2018-10-23 17:06:34 |
Frank Heimes |
attachment added |
|
verification_on_bionic.txt https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794308/+attachment/5204595/+files/verification_on_bionic.txt |
|
| 2018-10-23 17:07:02 |
Frank Heimes |
attachment added |
|
verification_on_xenial.txt https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794308/+attachment/5204596/+files/verification_on_xenial.txt |
|
| 2018-10-23 17:07:17 |
Frank Heimes |
tags |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-done-xenial verification-needed verification-needed-bionic |
id-5baa4a4ce2d7537ba20fd8c5 id-5baa55c367a0cd020990ac52 verification-done verification-done-bionic verification-done-xenial |
|
| 2018-10-30 15:55:31 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-10-30 15:57:59 |
Launchpad Janitor |
s390-tools (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-10-30 16:05:27 |
Launchpad Janitor |
s390-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-11-08 13:03:28 |
Bug Watch Updater |
s390-tools: status |
Unknown |
Fix Released |
|
