[Group.of.nepali.translators] [Bug 1794308] Re: VM devices rdr, pun and prt are not activated after restart

2018-10-30 Thread Launchpad Bug Tracker 
This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.8

---
s390-tools (1.34.0-0ubuntu8.8) xenial; urgency=medium

  * zdev: Adjust zdev modprobe path to be compatible with split-usr
systems. (LP: #1777600)
  * zdev: Trigger generic_ccw devices on any kernel module loads. (LP:
#1794308)

 -- Dimitri John Ledkov   Mon, 22 Oct 2018 12:51:12
+0100

** Changed in: s390-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released
Status in s390-tools source package in Bionic:
  Fix Released

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.000cno   no
  generic-ccw  0.0.000dno   no
  generic-ccw  0.0.000eno   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.000cyes  yes   vmrdr-0.0.000c
  generic-ccw  0.0.000dyes  yes   vmpun-0.0.000d
  generic-ccw  0.0.000eyes  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.000cno  yes
  generic-ccw  0.0.000dno  yes
  generic-ccw  0.0.000eno  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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1794308] Re: VM devices rdr, pun and prt are not activated after restart

2018-10-30 Thread Launchpad Bug Tracker 
This bug was fixed in the package s390-tools - 2.3.0-0ubuntu3.1

---
s390-tools (2.3.0-0ubuntu3.1) bionic; urgency=medium

  * zdev: Adjust zdev modprobe path to be compatible with split-usr
systems. (LP: #1777600)
  * zdev: Trigger generic_ccw devices on any kernel module loads. (LP:
#1794308)

 -- Dimitri John Ledkov   Mon, 22 Oct 2018 12:37:39
+0100

** Changed in: s390-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Committed
Status in s390-tools source package in Bionic:
  Fix Released

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.000cno   no
  generic-ccw  0.0.000dno   no
  generic-ccw  0.0.000eno   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.000cyes  yes   vmrdr-0.0.000c
  generic-ccw  0.0.000dyes  yes   vmpun-0.0.000d
  generic-ccw  0.0.000eyes  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.000cno  yes
  generic-ccw  0.0.000dno  yes
  generic-ccw  0.0.000eno  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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1794308] Re: VM devices rdr, pun and prt are not activated after restart

2018-10-22 Thread Dimitri John Ledkov 
** Also affects: s390-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: s390-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  New
Status in s390-tools source package in Bionic:
  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.000cno   no
  generic-ccw  0.0.000dno   no
  generic-ccw  0.0.000eno   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.000cyes  yes   vmrdr-0.0.000c
  generic-ccw  0.0.000dyes  yes   vmpun-0.0.000d
  generic-ccw  0.0.000eyes  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.000cno  yes
  generic-ccw  0.0.000dno  yes
  generic-ccw  0.0.000eno  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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp