group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1799208@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.9

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

  * dump2tar: backport utility
  * dbginfo.sh: backport patch to use dump2tar instead of walking sysfs
  * Addresses dbginfo.sh hanging indefinately whilst walking sysfs. LP:
    #1799208

 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>  Wed, 23 Jan 2019 07:36:29
-0500

** 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/1799208

Title:
  dbginfo.sh does not complete on Ubuntu 16.04(.5)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released

Bug description:
  dbginfo.sh does not complete on Ubuntu 16.04(.5) using s390-tools
  version 1.34.0-0ubuntu8.7

  Execution starts and proceeds until step 4 'sysfs':
  $ sudo dbginfo.sh
  dbginfo.sh: Debug information script version 1.34.0-build-20180502
  Copyright IBM Corp. 2002, 2016

  Hardware platform     = s390x
  Kernel version        = 4.15.0 (4.15.0-33-generic)
  Runtime environment   = LPAR

  1 of 10: Collecting command output

  2 of 10: Collecting z/VM command output skipped - no z/VM environment

  3 of 10: Collecting procfs

  4 of 10: Collecting sysfs

  'dd' process with 100% CPU can be seen:

  # ps aux | grep [d]d\
  root     257158  100  0.0   2120   664 pts/0    R+   06:51  11:18 dd if=/sys/kernel/debug/tracing/trace status=noxfer iflag=nonblock of=/tmp/DBGINFO-2018-10-22-06-49-52-s1lp15-1F8F67//sys/kernel/debug/tracing/trace

  Happens on 16.04.5 with kernel 4.4 or HWE kernel 4.15.
  But works fine on 18.04 (with kernel 4.15) and s390-tools 2.3.0-0ubuntu3.

  ----------

  The regression risk of this fixed dbginfo.sh script and the updated
  s390-tools package is very low for the following reasons:

  - the script is broken today on xenial, hence it cannot really get that worse...
  - the fix was provided by IBM via a newer s390-tools package and was pretested by IBM before it was made available
  - all this is limited to the s390x architecture and also to xenial (newer Ubuntu releases use newer packages)
  - newer s390-tools packages that already incl. the fix are used in newer Ubuntu server releases and are known to work there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799208/+subscriptions