from:"Andrew Cloke"

[Group.of.nepali.translators] [Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd

2021-01-18 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1904585

Title:
  opal-prd: Have a worker process handle page offlining (Fixes
  "PlatServices: dyndealloc memory_error() failed" is getting reported
  in error log (opal-prd))

Status in The Ubuntu-power-systems project:
  Fix Released
Status in skiboot package in Ubuntu:
  Fix Released
Status in skiboot source package in Xenial:
  Fix Released
Status in skiboot source package in Bionic:
  Fix Released
Status in skiboot source package in Focal:
  Fix Released
Status in skiboot source package in Groovy:
  Fix Released
Status in skiboot source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  This impacts the opal-prd userspace command from the skiboot package
  The memory_error() hservice interface expects the memory_error() call to
  just accept the offline request and return without actually offlining the
  memory. Currently we will attempt to offline the marked pages before
  returning to HBRT which can result in an excessively long time spent in the 
memory_error() hservice call which blocks HBRT from processing other
  errors.

  [Test Case]

  Unfortunately due to the specific hardware requirement I wasn't able
  to reproduce this problem and provide a test case for it. However I
  was able to build this package into a ppa and got the IBM team to
  confirm this problem was resolved for groovy focal, bionic, xenial see
  comment #4 and #6

  Another verification test will be done (as part of the SRU process)
  again by the IBM Power team.

  [What could go wrong]

  To avoid long delays (that may blocks HBRT from processing other
  errors) the memory offlining process is now separated in a dedicated
  worker process, that can now be handled in the background.

  If broken this can introduce further issues, like hangs in the worker 
process, not returning, and processes that pile up or in worst case memory 
pages that are not offlined, but reported otherwise.
  The latter one would be a significant memory management problem, that even 
may break the system over time entirely.

  But the code seem to have taken this into account with 'sigaction',
  the return-code/exit-status check and the reaping of the worker
  threads.

  The fix was prepared back in September and was upstream accepted,
  hence it's unlikely that regressions are in and in between it already
  landed in hirsute.

  On top a PPA with a patched skiboot package was created, shared and
  eventually successfully tested by IBM (the initial bug reporter).

  [Original Description]

  https://github.com/open-
  power/skiboot/commit/8cbd0de88d162e387f11569eee1bdecef8fad2e3

  opal-prd: Have a worker process handle page offlining

  The memory_error() hservice interface expects the memory_error() call to
  just accept the offline request and return without actually offlining the
  memory. Currently we will attempt to offline the marked pages before
  returning to HBRT which can result in an excessively long time spent in the
  memory_error() hservice call which blocks HBRT from processing other
  errors. Fix this by adding a worker process which performs the page
  offlining via the sysfs memory error interfaces.

  Reviewed-by: Vasant Hegde - hegdevas...@linux.vnet.ibm.com
  Signed-off-by: Oliver O'Halloran - ooh...@gmail.com

  Thanks in advance for your support.

  Machine Type = Power8 and Power9 OPAL systems

  ---Steps to Reproduce---
  * Inject memory error (UE)
  * Verify that opal-prd doesn't return asynchronously to the platform after 
requesting the memory offlining operation

  Userspace tool common name: opal-prd

  We need this fix for 16.04.x and 18.04.x LTS releases.

  Fix also is needed for 20.04 and 20.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+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 1848173] Re: Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not established by zcrypt device driver

2019-11-12 Thread Andrew Cloke

** Changed in: ubuntu-z-systems
   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/1848173

Title:
  Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not
  established by zcrypt device driver

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Ubuntu 16.04.6 systems on z15 with crypto CEX7C adapters under z/VM
  cannot see and make use of their hw crypto resources.

  * The patch/backport adds CEX7 toleration support (by mapping it to
  CEX5) to kernel 4.4.

  [Fix]

  * Backport:
  
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848173/+attachment/5297314/+files/s390
  -zcrypt-CEX7-toleration-support.patch

  [Test Case]

  * Define a z/VM guest with 'apvirt' (hardware crypto adapter
  virtualization) having CryptoExpress 7S adapters attached to z/VM
  LPAR.

  * Use lszcrypt command (ideally lszcrypt -VVV) from the s390-tools
  package to list the detected and available hardware crypto resources.

  * Canonical can only do a toleration test: IBM needs to do the
  functional test (due to hardware availability).

  [Regression Potential]

  * The regression potential can be considered as moderate since this is
  purely s390x specific

  * and limited to CryptoExpress 7S (CEX7) adapter cards

  * and again if they running under z/VM (on z15) with 'apvirt'
  configured for the guest.

  * and again only with 16.04.6's kernel 4.4.

  [Other Info]

  * The patch was already applied, kernel compiled and things tested on
  z15 und z/VM.

  __

  System: IBM Z15 z/VM with shared CEX7C adapters
  OS:  Ubuntu 16.04.6 LTS ( 4.4.0-165-generic kernel ) with latest updates
  Shared CEX7C adapters are not displayed on Ubuntu even though APAR 66266 had 
been installed onto the unterlying z/VM system.

  Details
  ===
  Defined shared CEX7C CCA adapters to provide cryptographic accelerators based 
on CCA cards to a z/VM guest system running Ubuntu 16.04.6 LTS.

  The adapters display all right under vm or when running vmcp commands
  under Linux.

  lszcrypt -VVV does not display any adapter.

  We observed that zcrypt_cex4 was not automatically loaded via
  dependency by modprobe ap. Explicitly loading by modprobe zcrypt_cex4
  did not change card availability.

  Please investigate.

  Thanks.

  Terminal output
  ==
  root@system:/sys/bus/ap/devices/card01# ls -l
  total 0
  -r--r--r-- 1 root root 4096 Oct  8 17:51 ap_functions
  -r--r--r-- 1 root root 4096 Oct  8 17:51 depth
  -r--r--r-- 1 root root 4096 Oct  8 17:51 hwtype
  -r--r--r-- 1 root root 4096 Oct  8 17:51 interrupt
  -r--r--r-- 1 root root 4096 Oct  8 17:51 modalias
  -r--r--r-- 1 root root 4096 Oct  8 17:51 pendingq_count
  drwxr-xr-x 2 root root0 Oct  8 17:51 power
  -r--r--r-- 1 root root 4096 Oct  8 17:51 raw_hwtype
  -r--r--r-- 1 root root 4096 Oct  8 17:51 request_count
  -r--r--r-- 1 root root 4096 Oct  8 17:51 requestq_count
  -r--r--r-- 1 root root 4096 Oct  8 17:51 reset
  lrwxrwxrwx 1 root root0 Oct  8 17:51 subsystem -> ../../../bus/ap
  -rw-r--r-- 1 root root 4096 Oct  8 17:50 uevent

  # lszcrypt -V// < No output displayed >
  # vmcp q v crypto
  AP 001 CEX7C Domain 001 shared online

  root@system:/sys/bus/ap/devices/card01# cat hwtype
  13
  root@system:/sys/bus/ap/devices/card01# cat raw_hwtype
  13

  # lsmod
  Module  Size  Used by
  ap 36864  0
  ghash_s390 16384  0
  prng   16384  0
  aes_s390   20480  0
  des_s390   16384  0
  des_generic28672  1 des_s390
  sha512_s39016384  0
  qeth_l253248  1
  sha256_s39016384  0
  sha1_s390  16384  0
  sha_common 16384  3 sha256_s390,sha1_s390,sha512_s390
  qeth  151552  1 qeth_l2
  vmur   20480  0
  ccwgroup   20480  1 qeth
  dm_multipath   36864  0
  zfcp  143360  0
  dasd_eckd_mod 118784  8
  qdio   73728  3 qeth,zfcp,qeth_l2
  scsi_transport_fc  86016  1 zfcp
  dasd_mod  135168  5 dasd_eckd_mod

  # modprobe zcrypt_cex4
  ...
  zcrypt_cex416384  0
  zcrypt_api 36864  1 zcrypt_cex4
  ap 36864  2 zcrypt_cex4,zcrypt_api
  ...

  Contact Information = christian.r...@de.ibm.com

  ---uname output---
  Linux system 4.4.0-164-generic #192-Ubuntu SMP Fri Sep 13 12:01:28 UTC 2019 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Type: 8561 Model:
  403  T01

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---

[Group.of.nepali.translators] [Bug 1832622] Re: QEMU - count cache flush Spectre v2 mitigation (CVE) (required for POWER9 DD2.3)

2019-10-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1832622

Title:
  QEMU -  count cache flush Spectre v2 mitigation (CVE) (required for
  POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Released
Status in qemu source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in qemu source package in Disco:
  Fix Released
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * This belongs to the overall context of spectre mitigations and even 
 more the try to minimize the related performance impacts.
 On ppc64el there is a new chip revision (DD 2.3) which provides
 a facility that helps to better mitigate some of this.

   * Backport the patches that will make the feature (if supported by the 
 HW) will pass the capability to the guest - to allow guests that 
 support the improved mitigation to use it.

  [Test Case]

   * Start guests with and without this capability
 * Check if the capability is guest visible as intented
 * Check if there are any issues on pre DD2.3 HW
   * Test migrations (IBM outlined the intented paths that will work 
 below)
   * The problem with the above (and also the reasons I didn't add a list 
 of commands this time) is that it needs special HW (mentioned DD2.3 
 revision) of the chips which aren't available to us right now.
 Due to that testing / verification of this on all releases is on IBM

  [Regression Potential]

   * Adding new capabilities usually works fine, there are three common 
 pitfalls which here are the regression potential.
 - (severe) the code would announce a capability that isn't really 
   available. The guest tries to use it and crashes
 - (medium) several migration paths especially from systems with the 
   new cap to older (un-updated systems) will fail. But that applies 
   to any "from machine with Feature to machine without that feature" 
   and isn't really a new regression. As outlined by IBM below they 
   even tried to make it somewhat compatible (by being a new value in 
   an existing cap)
 - (low) the guest will see new caps and or facilities. A really odd
   guest could stumble due to that (would actually be a guest bug 
   then)
Overall all of the above was considered by IBM when developing this 
and should be ok. For archive wide SRU considerations, this has NO 
effect on non ppc64el.

  [Other Info]
   
   * n/a

  ---

  Power9 DD 2.3  CPUs  running updated firmware will use a new Spectre
  v2 mitigation. The new mitigation improves performance of branch heavy
  workloads, but also requires kernel support in order to be fully
  secure.

  Without the kernel support there is a risk of a Spectre v2 attack
  across a process context switch, though it has not been demonstrated
  in practice.

  QEMU portion - platform definition needs to account for this new
  mitigation action.. so attribute for this needs to be added.

  In terms of support for virtualisation there are 2 sides, kvm and qemu
  support. Patch list for each,

  KVM:
  2b57ecd0208f KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
  This is part of LP1822870 already.

  QEMU:
  8ff43ee404 target/ppc/spapr: Add SPAPR_CAP_CCF_ASSIST
  399b2896d4 target/ppc/spapr: Add workaround option to SPAPR_CAP_IBS

  The KVM side is upstream as of v5.1-rc1.
  The QEMU side is upstream as of v4.0.0-rc0.

  In terms of migration the state is as follows.

  In order to specify to the guest to use the count cache flush
  workaround we use the spapr-cap cap-ibs (indirect branch speculation)
  with the value workaround. Previously the only valid values were
  broken, fixed-ibs (indirect branch serialisation) and fixed-ccd (count
  cache disabled). And add a new cap cap-ccf-assist (count cache flush
  assist) to specify the availability of the hardware assisted flush
  variant.

  Note the the way spapr caps work you can migrate to a host that supports a 
higher value, but not to one which doesn't support the current value (i.e. only 
supports lower values). Where for cap-ibs these are defined as:
  0 - Broken
  1 - Workaround
  2 - fixed-ibs
  3 - fixed-ccd

  So the following migrations would be valid for example:
  broken -> fixed-ccd, broken -> workaround, workaround -> fixed-ccd

  While the following would be invalid:
  fixed-ccd -> workaround, workaround ->broken, fixed-ccd -> broken

[Group.of.nepali.translators] [Bug 1842284] Re: initramfs does not copy ehci-platform

2019-09-03 Thread Andrew Cloke

** Changed in: initramfs-tools (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1842284

Title:
  initramfs does not copy ehci-platform

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  New

Bug description:
  [Impact]
  If you install Ubuntu onto USB storage behind a Platform USB host controller, 
it will not be able to boot because the generated initramfs will not include 
the host controller driver.

  [Test Case]
  Install to a USB stick attached to platform USB controller and reboot. 
Booting will fail because it will be unable to find the root file system.

  [Regression Risk]
  Driver is only loaded when system requires ehci-platform, minimizing the 
impact to all other systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1842284/+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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

2019-02-26 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1765660

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  ipcs command could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on live 
amd64, ppc64el and s390x system. In fact, the new upload introduces a test to 
verify this bug does not happen again.

  [Regression Potential]
  We have only introduced the fix for this specific bug, also adding a test for 
it. It's less likely to be more broken than the current version on the release 
as an entire new upstream version could be.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  files  mach   repeat timer
  alias  foreachmodrunq   tree
  ascii  fuser  mount  search union
  bt

[Group.of.nepali.translators] [Bug 1709877] Re: CPU hotplug fails in the system with empty numa nodes, "Invalid value '0-1, 16-17' for 'cpuset.mems': Invalid argument"

2019-01-23 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Incomplete => 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/1709877

Title:
  CPU hotplug fails in the system with empty numa nodes, "Invalid value
  '0-1,16-17' for 'cpuset.mems': Invalid argument"

Status in The Ubuntu-power-systems project:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Won't Fix

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-07-19 
04:13:18 ==
  CPU hotplug operation fails in the host with empty numa nodes(with no memory) 
even though VM placement is static and with/without numad is running.
  ..
   32
  ...

  
  # virsh setvcpus virt-tests-vm1 6 --live
  error: Invalid value '0-1,16-17' for 'cpuset.mems': Invalid argument

  
  # numactl --hardware
  available: 4 nodes (0-1,16-17)
  node 0 cpus: 0 8 16 24 32 40
  node 0 size: 16188 MB
  node 0 free: 1119 MB
  node 1 cpus: 48 56 64 72 80 88
  node 1 size: 32630 MB
  node 1 free: 13233 MB
  node 16 cpus: 96 104 112 120 128 136
  node 16 size: 0 MB
  node 16 free: 0 MB
  node 17 cpus: 144 152 160 168 176 184
  node 17 size: 0 MB
  node 17 free: 0 MB
  node distances:
  node   0   1  16  17 
0:  10  20  40  40 
1:  20  10  40  40 
   16:  40  40  10  20 
   17:  40  40  20  10 

  # cat /sys/fs/cgroup/cpuset/cpuset.mems 
  0-1

  Host:
  #uname -a
  Linux powerkvm4-lp1 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 
16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ii  libvirt-bin1.3.1-1ubuntu10.11 
  ii  numad  0.5+20150602-4 
  qemu-kvm   1:2.5+dfsg-5ubuntu10.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709877/+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 1709877] Re: CPU hotplug fails in the system with empty numa nodes, "Invalid value '0-1, 16-17' for 'cpuset.mems': Invalid argument"

2019-01-07 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Fix Released => Confirmed

** Changed in: libvirt (Ubuntu Xenial)
   Status: Incomplete => Confirmed

-- 
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/1709877

Title:
  CPU hotplug fails in the system with empty numa nodes, "Invalid value
  '0-1,16-17' for 'cpuset.mems': Invalid argument"

Status in The Ubuntu-power-systems project:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Confirmed

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-07-19 
04:13:18 ==
  CPU hotplug operation fails in the host with empty numa nodes(with no memory) 
even though VM placement is static and with/without numad is running.
  ..
   32
  ...

  
  # virsh setvcpus virt-tests-vm1 6 --live
  error: Invalid value '0-1,16-17' for 'cpuset.mems': Invalid argument

  
  # numactl --hardware
  available: 4 nodes (0-1,16-17)
  node 0 cpus: 0 8 16 24 32 40
  node 0 size: 16188 MB
  node 0 free: 1119 MB
  node 1 cpus: 48 56 64 72 80 88
  node 1 size: 32630 MB
  node 1 free: 13233 MB
  node 16 cpus: 96 104 112 120 128 136
  node 16 size: 0 MB
  node 16 free: 0 MB
  node 17 cpus: 144 152 160 168 176 184
  node 17 size: 0 MB
  node 17 free: 0 MB
  node distances:
  node   0   1  16  17 
0:  10  20  40  40 
1:  20  10  40  40 
   16:  40  40  10  20 
   17:  40  40  20  10 

  # cat /sys/fs/cgroup/cpuset/cpuset.mems 
  0-1

  Host:
  #uname -a
  Linux powerkvm4-lp1 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 
16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ii  libvirt-bin1.3.1-1ubuntu10.11 
  ii  numad  0.5+20150602-4 
  qemu-kvm   1:2.5+dfsg-5ubuntu10.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709877/+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 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

2018-12-28 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
Status: In Progress => 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/1746088

Title:
[Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
Fix Released
Status in crash package in Ubuntu:
Fix Released
Status in crash source package in Xenial:
Fix Released
Status in crash source package in Artful:
Won't Fix
Status in crash source package in Bionic:
Invalid

Bug description:
[Impact]
It won't be possible to analyze dumps produced by newer kernels (hwe on
xenial, for example).

[Test Case]
Tested that this version of crash can analyze both GA (4.4) and hwe (4.15)
kernels.

[Regression Potential]
New crash versions may have bugs and some commands not work with older
kernels. The smoke test helps a little, but more testing may be desirable.

---Problem Description---
Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel
(Ubuntu 16.04.4)

---uname output---
Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 8001-22C

---Steps to Reproduce---
This bug follow up bug of
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
The steps to create dump is as follows

Once you generate the kdump
use crash to analyze the vmcore and we get this error

console logs ==

root@ltc-briggs1:/var/crash/201801150227# ls
dmesg.201801150227 vmcore.201801150227
.0-26-generic vmcore.2018011502271150227# crash
/usr/lib/debug/boot/vmlinux-4.13.

crash 7.1.4
Copyright (C) 2002-2015 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.

GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-unknown-linux-gnu"...

please wait... (gathering module symbol data)
WARNING: cannot access vmalloc'd module memory

crash: invalid structure member offset: thread_info_task
FILE: task.c LINE: 598 FUNCTION: irqstacks_init()

[/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

== Comment from Hari Krishna Bathini ==

There are quite a few commits (all available upstream) that are needed for
crash tool to work fine. I think the right thing to do here would be to use
the latest crash tool version 7.2.0 to go with the kernel update. Also, the
below commit would be needed on top of 7.2.0 crash utility:

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson
Date: Thu Nov 9 11:39:05 2017 -0500

Update for support of Linux 4.14 and later PPC64 kernels where the
hash page table geometry accomodates a larger virtual address range.
Without the patch, the virtual-to-physical translation of user space
virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
invalid translation or otherwise fail.
(hbath...@linux.vnet.ibm.com)

Similar thing holds true for makedumpfile tool..

Thanks
Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+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 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04

2018-11-20 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1790832

Title:
  crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:

  == SRU Justification ==
  IBM is requesting this patch in all releases order to fix the sleep-in-atomic
  bugs in AES-CBC and AES-XTS VMX implementations.

  This patch is a clean cherry pick and has already been applied to
  Cosmic.  It is also needed in Xenial, but there was a minor context
  diff, so the Xenial SRU will be sent separatly.

  == Fix ==
  0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")

  == Regression Potential ==
  Low.  This patch has also been cc'd to upstream stable, so it has had
  additional upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  
  == Comment: #0 - Paulo Flabiano Smorigo
  Please include the following commit in order to fix the sleep-in-atomic bugs 
in AES-CBC and AES-XTS VMX implementations [1]:

  0522236 crypto: vmx - Fix sleep-in-atomic bugs

  [1]
  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+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 1650493] Re: numastat fails with double free or corruption

2018-11-12 Thread Andrew Cloke

Marking the ubuntu-power-systems series as fix released as it is Fix
Released in all released versions.

** Changed in: ubuntu-power-systems
   Status: Incomplete => 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/1650493

Title:
  numastat  fails with double free or corruption

Status in The Ubuntu-power-systems project:
  Fix Released
Status in numactl package in Ubuntu:
  Incomplete
Status in numactl source package in Xenial:
  Fix Released
Status in numactl source package in Bionic:
  Fix Released
Status in numactl source package in Cosmic:
  Fix Released
Status in numactl source package in Disco:
  Incomplete

Bug description:
  while trying to get stat of the guest process (configured with
  hugepages), numastat fails

  
  Environment details
  
  # uname -a
  Linux lep8b 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:46 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linu

  =
  Issue
  =
  2016-12-14 07:02:56,396 process  L0368 INFO | Running 'numastat 61257'
  2016-12-14 07:02:56,402 process  L0462 DEBUG| [stderr] *** Error in 
`numastat': double free or corruption (out): 0x0100265005a0 ***
  2016-12-14 07:02:56,403 process  L0462 DEBUG| [stdout]
  2016-12-14 07:02:56,403 process  L0482 INFO | Command 'numastat 
61257' finished with -6 after 0.00309896469116s
  2016-12-14 07:02:56,403 process  L0462 DEBUG| [stdout] Per-node 
process memory usage (in MBs) for PID 61257 (qemu-system-ppc)
  2016-12-14 07:02:56,404 process  L0462 DEBUG| [stderr] === 
Backtrace: =
  2016-12-14 07:02:56,404 process  L0462 DEBUG| [stderr] 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x86d54)[0x3fff9a736d54]
  2016-12-14 07:02:56,404 process  L0462 DEBUG| [stderr] 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x93c30)[0x3fff9a743c30]
  2016-12-14 07:02:56,404 process  L0462 DEBUG| [stderr] 
/lib/powerpc64le-linux-gnu/libc.so.6(cfree+0x68)[0x3fff9a748218]
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
/lib/powerpc64le-linux-gnu/libc.so.6(fclose+0x1c8)[0x3fff9a727d68]
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
numastat(+0x7aa4)[0x401d7aa4]
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
numastat(+0x2388)[0x401d2388]
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x2291c)[0x3fff9a6d291c]
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fff9a6d2b18]
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] === Memory 
map: 
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
401d-401e r-xp  08:92 40325510   
/usr/bin/numastat
  2016-12-14 07:02:56,405 process  L0462 DEBUG| [stderr] 
401e-401f r--p  08:92 40325510   
/usr/bin/numastat
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
401f-4020 rw-p 0001 08:92 40325510   
/usr/bin/numastat
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
1002650-1002653 rw-p  00:00 0[heap]
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
3fff9a6b-3fff9a86 r-xp  08:92 25745199   
/lib/powerpc64le-linux-gnu/libc-2.24.so
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
3fff9a86-3fff9a87 ---p 001b 08:92 25745199   
/lib/powerpc64le-linux-gnu/libc-2.24.so
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
3fff9a87-3fff9a88 r--p 001b 08:92 25745199   
/lib/powerpc64le-linux-gnu/libc-2.24.so
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
3fff9a88-3fff9a89 rw-p 001c 08:92 25745199   
/lib/powerpc64le-linux-gnu/libc-2.24.so
  2016-12-14 07:02:56,406 process  L0462 DEBUG| [stderr] 
3fff9a8b-3fff9a8c rw-p  00:00 0
  2016-12-14 07:02:56,407 process  L0462 DEBUG| [stderr] 
3fff9a8c-3fff9a8e r-xp  00:00 0  [vdso]
  2016-12-14 07:02:56,407 process  L0462 DEBUG| [stderr] 
3fff9a8e-3fff9a92 r-xp  08:92 25745195   
/lib/powerpc64le-linux-gnu/ld-2.24.so
  2016-12-14 07:02:56,407 process  L0462 DEBUG| [stderr] 
3fff9a92-3fff9a93 r--p 0003 08:92 25745195   
/lib/powerpc64le-linux-gnu/ld-2.24.so
  2016-12-14 07:02:56,407 process  L0462 DEBUG| [stderr] 
3fff9a93-3fff9a94 rw-p 0004 08:92 25745195   
/lib/powerpc64le-linux-gnu/ld-2.24.so
  2016-12-14

[Group.of.nepali.translators] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345

2018-10-11 Thread Andrew Cloke

Thanks for the update. Marking as "invalid".

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Invalid

-- 
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/1775527

Title:
  Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
  running after a day #345

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2016-09-08 15:01:30 
==
  We have installed 16.04.1 on our guest and running IO stress test against via 
virtual qlogic disk. After running around 8 hrs, this error popping up 
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these 
errors "xfs_log_force: error -5 returned" fill up all the log.

  Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error: 
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
  Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp: 
xfs_trans_read_buf() returned error -5.
  Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9): 
xfs_do_force_shutdown(0x8) called from line 3433 of file 
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address = 
0xd37951f4
  Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error: 
block 0x703d54 ("xlog_iodone") error 5 numblks 64
  Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9): 
xfs_do_force_shutdown(0x2) called from line 1197 of file 
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address = 
0xd37a4c00
  Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error 
Detected. Shutting down filesystem
  Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the 
filesystem and rectify the problem(s)

  follow with all of these error that quickly fill up dmesg log
  Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2 
file system using the ext4 subsystem
  Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted 
filesystem without journal. Opts: (null)
  Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
  Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force: 
error -5 returned.

  == Comment: #1 - Chanh H. Nguyen  - 2016-09-08 15:02:27 
==
  We recently re-created this bug on our new system "cressg2" which is using a 
different SAN on kernel -36. 
  My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test, 
and it is hitting "xfs_log_force: error -5 returned"  problem after it runs the 
tests for 15 hours. It is using our lab storage (SVC SAN storage configuation 
with access to DS8000 Volume) and switch, compare to tinyg3, so it is using 
different storage and fabric switch. 

  root@cressg2:~# uname -a
  Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  [Wed Sep  7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:49 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:56 2016] XFS (vdb8): xfs_log_force: error -5 returned.

[Group.of.nepali.translators] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

2018-10-10 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
Status: Fix Released => Triaged

Title:
[Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
Triaged
Status in crash package in Ubuntu:
Fix Released
Status in crash source package in Xenial:
Fix Released
Status in crash source package in Artful:
Won't Fix
Status in crash source package in Bionic:
Triaged

Bug description:
[Impact]
It won't be possible to analyze dumps produced by newer kernels (hwe on
xenial, for example).

[Test Case]
Tested that this version of crash can analyze both GA (4.4) and hwe (4.15)
kernels.

[Regression Potential]
New crash versions may have bugs and some commands not work with older
kernels. The smoke test helps a little, but more testing may be desirable.

---Problem Description---
Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel
(Ubuntu 16.04.4)

---uname output---
Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 8001-22C

---Steps to Reproduce---
This bug follow up bug of
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
The steps to create dump is as follows

Once you generate the kdump
use crash to analyze the vmcore and we get this error

console logs ==

root@ltc-briggs1:/var/crash/201801150227# ls
dmesg.201801150227 vmcore.201801150227
.0-26-generic vmcore.2018011502271150227# crash
/usr/lib/debug/boot/vmlinux-4.13.

please wait... (gathering module symbol data)
WARNING: cannot access vmalloc'd module memory

crash: invalid structure member offset: thread_info_task
FILE: task.c LINE: 598 FUNCTION: irqstacks_init()

[/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

== Comment from Hari Krishna Bathini ==

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson
Date: Thu Nov 9 11:39:05 2017 -0500

Similar thing holds true for makedumpfile tool..

Thanks
Hari

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

[Group.of.nepali.translators] [Bug 1709784] Re: KVM on 16.04.3 throws an error

2018-10-08 Thread Andrew Cloke

As this ticket only relates to Xenial and 4.4 kernel, marking as "Fix
Released".

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   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/1709784

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102

[Group.of.nepali.translators] [Bug 1765364] Re: Backport spectre/meltdown fixes on qemu for ppc64 into 16.04 and possibly 14.04 LTS releases

2018-10-08 Thread Andrew Cloke

** Also affects: ubuntu-power-systems/ubuntu-14.04
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems/ubuntu-14.04
   Importance: Undecided => Critical

** Changed in: ubuntu-power-systems/ubuntu-16.04
   Status: New => In Progress

-- 
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/1765364

Title:
  Backport spectre/meltdown fixes on qemu for ppc64 into 16.04 and
  possibly 14.04 LTS releases

Status in The Ubuntu-power-systems project:
  In Progress
Status in The Ubuntu-power-systems project ubuntu-14.04 series:
  New
Status in The Ubuntu-power-systems project ubuntu-16.04 series:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-04-19 
04:26:51 ==
  ---Problem Description---
  Backport spectre/meltdown fixes on qemu for ppc64 into all LTS releases
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  -
   
  Machine Type = power8,power9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   For pseries guests there are 3 tri-state -machine options/capabilities 
relating to Spectre/Meltdown mitigation: cap-cfpc, cap-sbbc, cap-ibs, which 
each correspond to a set of host machine capabilities advertised by the KVM 
kernel module in new/patched host kernels that can be used to mitigate various 
aspects of Spectre/Meltdown:

  cap-cfpc: Cache Flush on Privilege Change
  cap-sbbc: Speculation Barrier Bounds Checking
  cap-ibs: Indirect Branch Serialisation

  Details can be found here https://www.qemu.org/2018/02/14/qemu-2-11-1
  -and-spectre-update/

  Needed qemu commits:

  cb931c2108 target/ppc: Check mask when setting cap_ppc_safe_indirect_branch
  4f5b039d2b ppc/spapr-caps: Disallow setting workaround for spapr-cap-ibs
  8c5909c419 ppc/spapr-caps: Change migration macro to take full spapr-cap name
  c59704b254 target/ppc/spapr: Add H-Call H_GET_CPU_CHARACTERISTICS
  4be8d4e7d9 target/ppc/spapr_caps: Add new tristate cap safe_indirect_branch
  09114fd817 target/ppc/spapr_caps: Add new tristate cap safe_bounds_check
  8f38eaf8f9 target/ppc/spapr_caps: Add new tristate cap safe_cache
  6898aed77f target/ppc/spapr_caps: Add support for tristate spapr_capabilities
  8acc2ae5e9 target/ppc/kvm: Add 
cap_ppc_safe_[cache/bounds_check/indirect_branch]


  Optional commits to introduce a machine type variant pseries--sxxm, 
when used would set/enable the three machine capabilities explained above 
automatically, if host is capable(host kernel is supported). Bug 166426
  813f3cf655 ppc/spapr-caps: Define the pseries-2.12-sxxm machine type
  c76c0d3090 ppc/spapr-caps: Convert cap-ibs to custom spapr-cap
  aaf265ffde ppc/spapr-caps: Convert cap-sbbc to custom spapr-cap
  f27aa81e72 ppc/spapr-caps: Convert cap-cfpc to custom spapr-cap
  87175d1bc5 ppc/spapr-caps: Add support for custom spapr_capabilities

  
   
  Userspace tool common name: qemu-kvm 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: qemu-kvm

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for sathe...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1765364/+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 1709784] Re: KVM on 16.04.3 throws an error

2018-10-03 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Fix Released => Fix Committed

-- 
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/1709784

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102 ]---
  [  340.276202] 

  
  This was with the latest ubuntu cloud image. I get the same thing when trying 
to use virt-install with an ISO image. 

  I

[Group.of.nepali.translators] [Bug 1781242] Re: as segfault with invalid -march= option

2018-09-20 Thread Andrew Cloke

** Changed in: ubuntu-z-systems
   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/1781242

Title:
  as segfault with invalid -march= option

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * as segfaults, instead of exiting gracefully, when one specifies 
unsupported arch option (ie. one from future - cause xenial did not support z14)
   * this is bad, as detection fails around supported march options - as if 
binutils are completely broken, rather than just not supporting this or that 
CPU level of optimisations.

  [Test Case]

  Bad result:
   $ as -march=foo
  Segmentation fault

  Expected result:
  # as -march=foo
  Assembler messages:
  Error: invalid switch -march=foo
  Error: unrecognized option -march=foo

  [Regression Potential]

   * The result is still a failure condition, but with a proper exit
  code and standard error messages, rather than an unexplainable generic
  segfault.

  [Other Info]
   
   * Original bug report

  The GNU assembler segfaults with an invalid -march= option

  Contact Information = n/a

  ---uname output---
  n/a

  Machine Type = n/a

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   $ as -march=foo
  Segmentation fault

  Expected result:
  # as -march=foo
  Assembler messages:
  Error: invalid switch -march=foo
  Error: unrecognized option -march=foo

  Userspace tool common name: as

  The userspace tool has the following bit modes: 64

  Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6

  Userspace tool obtained from project website:  na

  *Additional Instructions for n/a:
  -Attach ltrace and strace of userspace application.

  The problem is not critical since usually 'as' is invoked through the
  gcc driver which itself errors out for wrong -march= options. It will
  only be a problem if somebody builds a more recent GCC from source and
  uses an -march= option for a machine not supported by the default
  binutils.

  Please consider integrating the attached patch into 16.04 binutils.

  The problem has been fixed in later binutils already. Ubuntu 18.04
  does not appear to be affected.

  --> Package has to set corectly by Canonical

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781242/+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 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

2018-09-06 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released

Title:
[Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
4.13.0-26-generic kernel

Bug description:
[Impact]
It won't be possible to analyze dumps produced by newer kernels (hwe on
xenial, for example).

[Test Case]
Tested that this version of crash can analyze both GA (4.4) and hwe (4.15)
kernels.

[Regression Potential]
New crash versions may have bugs and some commands not work with older
kernels. The smoke test helps a little, but more testing may be desirable.

---Problem Description---
Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel
(Ubuntu 16.04.4)

---uname output---
Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 8001-22C

---Steps to Reproduce---
This bug follow up bug of
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
The steps to create dump is as follows

Once you generate the kdump
use crash to analyze the vmcore and we get this error

console logs ==

root@ltc-briggs1:/var/crash/201801150227# ls
dmesg.201801150227 vmcore.201801150227
.0-26-generic vmcore.2018011502271150227# crash
/usr/lib/debug/boot/vmlinux-4.13.

please wait... (gathering module symbol data)
WARNING: cannot access vmalloc'd module memory

crash: invalid structure member offset: thread_info_task
FILE: task.c LINE: 598 FUNCTION: irqstacks_init()

[/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

== Comment from Hari Krishna Bathini ==

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson
Date: Thu Nov 9 11:39:05 2017 -0500

Similar thing holds true for makedumpfile tool..

Thanks
Hari

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

[Group.of.nepali.translators] [Bug 1783252] Re: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le

2018-08-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: In Progress => Won't Fix

-- 
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/1783252

Title:
  gcc on ppc64le has bogus r30 register handling, as exposed by greenlet
  0.4.14 will not build on ppc64le

Status in The Ubuntu-power-systems project:
  Won't Fix
Status in gcc-5 package in Ubuntu:
  Won't Fix
Status in python-greenlet package in Ubuntu:
  Fix Released
Status in gcc-5 source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * GCC has a minor bug w.r.t. clobber r30 register in PIC binaries.
   * A patch to fix this has been upstream in 6+
   * But it is not in gcc-5.4 as used on xenial
   * This prevents compiling future-proof and correct greenlet code, on Ubuntu 
16.04 LTS as used by current and supported Openstack Queens release on ppc64el
   * Whilst backported greenlet is available via the cloud archive for binary 
usage, the toolchain is still technically incorrect, and thus hinders using 
Ubuntu 16.04 LTS as workers in upstream Openstack CI
   * As a wishlist it would be nice to backport this one small gcc patch as an 
SRU

  [Test Case]

   * git clone https://github.com/python-greenlet/greenlet
   * cd greenlet
   * ./setup.py build
  Expect success

  Current result failure:

  creating build/temp.linux-ppc64le-2.7
  powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c greenlet.c -o 
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
  In file included from slp_platformselect.h:16:0,
   from greenlet.c:343:
  platform/switch_ppc64_linux.h: In function 'slp_switch':
  platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' in 
'asm'
   __asm__ volatile ("" : : : REGS_TO_SAVE);
   ^
  platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' in 
'asm'
   __asm__ volatile ("" : : : REGS_TO_SAVE);
   ^
  error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1

  
  [Regression Potential] 

   * Upstream cherrypick present in later releases including bionic
  
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361

  
  [Other Info]
   
   * Original bug report

  
  == Comment: #0 - William M. Edmonds  - 2018-07-23 
16:21:41 ==
  ---Problem Description---
  greenlet 0.4.14 will not build on ppc64le

  Opened https://github.com/python-greenlet/greenlet/issues/136 because
  attempting to build bdist_wheel for greenlet 0.4.14 on ppc64le Ubuntu
  16.04 LTS yields the following error:

  running build
  running build_ext
  building 'greenlet' extension
  creating build
  creating build/temp.linux-ppc64le-2.7
  powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c greenlet.c -o 
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
  In file included from slp_platformselect.h:16:0,
  from greenlet.c:343:
     platform/switch_ppc64_linux.h: In function 'slp_switch':
     platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' 
in 'asm'
  __asm__ volatile ("" : : : REGS_TO_SAVE);
  ^
     platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' 
in 'asm'
  __asm__ volatile ("" : : : REGS_TO_SAVE);
  ^
     error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1```

  But the greenlet community is saying this is a gcc bug and it would
  not be safe to revert the greenlet change that exposed this issue. I
  have no idea whether that is true or not. Supposedly this should be
  fixed by
  
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361
  but that fix is not present in the latest version of gcc (5.4.0)
  available for Ubuntu 16.04 LTS.

  ---uname output---
  unavailable due to lab outage

  Machine Type = unavailable due to lab outage

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  This should be reproducible with `git clone 
git://github.com/python-greenlet/greenlet; cd greenlet; python setup.py 
bdist_wheel`, though it was originally found using pypi rather than github and 
with a more complicated (scripted) command as detailed in the greenlet bug 
description.

  Contact Information = Matthew Edmonds / edmon...@us.ibm.com

  Userspace tool common name: greenlet

  The userspace tool has the following bit modes: no idea

  Userspace rpm: N/A

  Userspace tool obtained from project website:  0.4.14

  *Additional

[Group.of.nepali.translators] [Bug 1783252] Re: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le

2018-08-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Won't Fix => In Progress

-- 
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/1783252

Title:
  gcc on ppc64le has bogus r30 register handling, as exposed by greenlet
  0.4.14 will not build on ppc64le

Status in The Ubuntu-power-systems project:
  In Progress
Status in gcc-5 package in Ubuntu:
  Won't Fix
Status in python-greenlet package in Ubuntu:
  Fix Released
Status in gcc-5 source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * GCC has a minor bug w.r.t. clobber r30 register in PIC binaries.
   * A patch to fix this has been upstream in 6+
   * But it is not in gcc-5.4 as used on xenial
   * This prevents compiling future-proof and correct greenlet code, on Ubuntu 
16.04 LTS as used by current and supported Openstack Queens release on ppc64el
   * Whilst backported greenlet is available via the cloud archive for binary 
usage, the toolchain is still technically incorrect, and thus hinders using 
Ubuntu 16.04 LTS as workers in upstream Openstack CI
   * As a wishlist it would be nice to backport this one small gcc patch as an 
SRU

  [Test Case]

   * git clone https://github.com/python-greenlet/greenlet
   * cd greenlet
   * ./setup.py build
  Expect success

  Current result failure:

  creating build/temp.linux-ppc64le-2.7
  powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c greenlet.c -o 
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
  In file included from slp_platformselect.h:16:0,
   from greenlet.c:343:
  platform/switch_ppc64_linux.h: In function 'slp_switch':
  platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' in 
'asm'
   __asm__ volatile ("" : : : REGS_TO_SAVE);
   ^
  platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' in 
'asm'
   __asm__ volatile ("" : : : REGS_TO_SAVE);
   ^
  error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1

  
  [Regression Potential] 

   * Upstream cherrypick present in later releases including bionic
  
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361

  
  [Other Info]
   
   * Original bug report

  
  == Comment: #0 - William M. Edmonds  - 2018-07-23 
16:21:41 ==
  ---Problem Description---
  greenlet 0.4.14 will not build on ppc64le

  Opened https://github.com/python-greenlet/greenlet/issues/136 because
  attempting to build bdist_wheel for greenlet 0.4.14 on ppc64le Ubuntu
  16.04 LTS yields the following error:

  running build
  running build_ext
  building 'greenlet' extension
  creating build
  creating build/temp.linux-ppc64le-2.7
  powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c greenlet.c -o 
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
  In file included from slp_platformselect.h:16:0,
  from greenlet.c:343:
     platform/switch_ppc64_linux.h: In function 'slp_switch':
     platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' 
in 'asm'
  __asm__ volatile ("" : : : REGS_TO_SAVE);
  ^
     platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' 
in 'asm'
  __asm__ volatile ("" : : : REGS_TO_SAVE);
  ^
     error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1```

  But the greenlet community is saying this is a gcc bug and it would
  not be safe to revert the greenlet change that exposed this issue. I
  have no idea whether that is true or not. Supposedly this should be
  fixed by
  
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361
  but that fix is not present in the latest version of gcc (5.4.0)
  available for Ubuntu 16.04 LTS.

  ---uname output---
  unavailable due to lab outage

  Machine Type = unavailable due to lab outage

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  This should be reproducible with `git clone 
git://github.com/python-greenlet/greenlet; cd greenlet; python setup.py 
bdist_wheel`, though it was originally found using pypi rather than github and 
with a more complicated (scripted) command as detailed in the greenlet bug 
description.

  Contact Information = Matthew Edmonds / edmon...@us.ibm.com

  Userspace tool common name: greenlet

  The userspace tool has the following bit modes: no idea

  Userspace rpm: N/A

  Userspace tool obtained from project website:  0.4.14

  *Additional

[Group.of.nepali.translators] [Bug 1781293] Re: ipmitool reports NVIDIA BMCs as "Unknown"

2018-07-26 Thread Andrew Cloke

** Changed in: ipmitool (Ubuntu Artful)
   Status: New => Invalid

-- 
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/1781293

Title:
  ipmitool reports NVIDIA BMCs as "Unknown"

Status in ipmitool package in Ubuntu:
  Fix Released
Status in ipmitool source package in Xenial:
  New
Status in ipmitool source package in Artful:
  Invalid
Status in ipmitool source package in Bionic:
  Fix Released
Status in ipmitool source package in Cosmic:
  Fix Released
Status in ipmitool package in Debian:
  New

Bug description:
  [Impact]
  The command "ipmitool mc info" fails to recognize the Manufacturer ID for 
NVIDIA BMCs, causing it to report:

  Manufacturer Name : Unknown

  [Test Case]
  On an NVIDIA system, such as a DGX-1 system, run "sudo ipmitool mc info" and 
look for:

  Manufacturer Name : NVIDIA Corporation

  [Regression Risk]
  Adds a static entry to a lookup table. The biggest regression risk I see is 
if there are BMCs out there using NVIDIA's registered ID that aren't actually 
NVIDIA BMCs - ipmitool would now be reporting them incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1781293/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2018-07-26 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size

[Group.of.nepali.translators] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush

2018-07-25 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: In Progress => 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/1751994

Title:
  ppc64el: Support firmware disable of RFI flush

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+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 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

2018-07-23 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1714485

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+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 1751994] Re: ppc64el: Support firmware disable of RFI flush

2018-07-23 Thread Andrew Cloke

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Invalid

-- 
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/1751994

Title:
  ppc64el: Support firmware disable of RFI flush

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+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 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

2018-07-23 Thread Andrew Cloke

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Fix Committed => Invalid

-- 
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/1714485

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+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 1716517] Re: [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

2018-06-28 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Incomplete => 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/1716517

Title:
  [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

Status in The Ubuntu-power-systems project:
  Fix Released
Status in openipmi package in Ubuntu:
  Fix Released
Status in openipmi source package in Xenial:
  Fix Released
Status in openipmi source package in Artful:
  Fix Released
Status in openipmi source package in Bionic:
  Fix Released
Status in openipmi package in Debian:
  Fix Released

Bug description:
  [Impact]
  openipmi service fails to start on arm64/ppc64le servers because 
ipmi_ssif/ipmi_powernv is not loaded, and ipmi_si is loaded instead.

  [Test]
  sudo apt install openipmi
  sudo service openipmi status

  [Fix]
  ARM64 servers use ipmi_ssif instead of ipmi_si. Load ipmi_ssif instead.
  PPC64EL servers use ipmi_powernv instead of ipmi_si. Load ipmi_powernv 
instead.

  [Regression Potential]
  ipmitool tries to load ipmi_si for any given architecture. Thus fails to init 
on ARM and Power architecture. The patch adds logic for ipmitool to load 
ipmi_ssif or ipmi_powernv for ARM and Power architecture. You might see a 
regression on architectures that we still do not have official support for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1716517/+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 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".

2018-05-21 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1758037

Title:
  LTC Test- Ubuntu18.04: Starting the guest with network filter defined
  will fail with "cause is unknown".

Status in libvirt:
  Unknown
Status in The Ubuntu-power-systems project:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Fix Released
Status in libvirt source package in Artful:
  Fix Released
Status in libvirt source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * nwfilters were not usable if configured to use dhcp based learning

   * Fix by backporting upstream bug

  [Test Case]

   * Add the following to the interface section of a guest description in 
 libvirt:
   
 
   
  Then start the guest.

  Bad case:
  error: Failed to start domain VM1
  error: An error occurred, but the cause is unknown

  Fixed:
  Guest starts and works.

  [Regression Potential]

   * I thought a while on this. On first sight one might say there is a 
 regression risk due to increasing the size of the buffer. This risk 
 would arise on hyperscale environments where the memory consumption per 
 guest would increase by 2*128Kb*#guest-interfaces (not much, but can 
 sum up on MANY guests).
 But then I realized that this is only true for the use case using 
 dhcpsnoop which is
 a) clearly not the most common case
 b) failing to work at all before this fix
 So there can't be anyone today with a working setup that then runs OOM, 
 due to the setup either not using the feature (=no change) or failing 
 missing this fix.
 So I actually think this mem consumption increase is not an issue in 
 terms of SRU considerations.
 Due to that the only remaining regression would be users that had a 
 self-built libpcap without TPACKET_V3 to drive a workload like the 
 above, and even then only the rather small size bump is what changes.

  [Other Info]
   
   * I have added this case and a few deeper checks on the created rules for 
 iptables to the regression tests

  ---

  == Comment: #2 - Mallesh N. Koti  - 2018-02-28
  05:02:49 ==

  Guest Xml

  ===
  ISSUE
  ===
  Defining a network filter and Starting a VM with this nwfiter in VM's xml is 
failing with "cause is unknown".

  ==
  Recreation Steps
  ==

  1. Define a network filter as:
    virsh nwfilter-define filter.xml

  2. Add nwfilter in guest xml and start guest.
    virsh start VM1

  It fails with :
  # virsh start VM1
  error: Failed to start domain VM1
  error: An error occurred, but the cause is unknown

  XML used for defining network filter:
  ```
  
    -b071-6127-b4ec-
    
  
  
  ```

  will be attaching the guest xml

  The issue happens with Ubuntu 18.04 host - where not able to start the
  guest with network defined with value dhcp.

  
  .
  Found following commit is not there in 18.04 Ubuntu source. There could be 
some dependent commit too.  we are facing some build issue and hence not able 
to verify it.
  .
  
https://github.com/libvirt/libvirt/commit/e62cb4a9b78c7f4499a206635fb4f06e6ac627e5
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1758037/+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 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".

2018-05-11 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Fix Released => Fix Committed

-- 
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/1758037

Title:
  LTC Test- Ubuntu18.04: Starting the guest with network filter defined
  will fail with "cause is unknown".

Status in libvirt:
  Unknown
Status in The Ubuntu-power-systems project:
  Fix Committed
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Fix Committed
Status in libvirt source package in Artful:
  Fix Committed
Status in libvirt source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * nwfilters were not usable if configured to use dhcp based learning

   * Fix by backporting upstream bug

  [Test Case]

   * Add the following to the interface section of a guest description in 
 libvirt:
   
 
   
  Then start the guest.

  Bad case:
  error: Failed to start domain VM1
  error: An error occurred, but the cause is unknown

  Fixed:
  Guest starts and works.

  [Regression Potential]

   * I thought a while on this. On first sight one might say there is a 
 regression risk due to increasing the size of the buffer. This risk 
 would arise on hyperscale environments where the memory consumption per 
 guest would increase by 2*128Kb*#guest-interfaces (not much, but can 
 sum up on MANY guests).
 But then I realized that this is only true for the use case using 
 dhcpsnoop which is
 a) clearly not the most common case
 b) failing to work at all before this fix
 So there can't be anyone today with a working setup that then runs OOM, 
 due to the setup either not using the feature (=no change) or failing 
 missing this fix.
 So I actually think this mem consumption increase is not an issue in 
 terms of SRU considerations.
 Due to that the only remaining regression would be users that had a 
 self-built libpcap without TPACKET_V3 to drive a workload like the 
 above, and even then only the rather small size bump is what changes.

  [Other Info]
   
   * I have added this case and a few deeper checks on the created rules for 
 iptables to the regression tests

  ---

  == Comment: #2 - Mallesh N. Koti  - 2018-02-28
  05:02:49 ==

  Guest Xml

  ===
  ISSUE
  ===
  Defining a network filter and Starting a VM with this nwfiter in VM's xml is 
failing with "cause is unknown".

  ==
  Recreation Steps
  ==

  1. Define a network filter as:
    virsh nwfilter-define filter.xml

  2. Add nwfilter in guest xml and start guest.
    virsh start VM1

  It fails with :
  # virsh start VM1
  error: Failed to start domain VM1
  error: An error occurred, but the cause is unknown

  XML used for defining network filter:
  ```
  
    -b071-6127-b4ec-
    
  
  
  ```

  will be attaching the guest xml

  The issue happens with Ubuntu 18.04 host - where not able to start the
  guest with network defined with value dhcp.

  
  .
  Found following commit is not there in 18.04 Ubuntu source. There could be 
some dependent commit too.  we are facing some build issue and hence not able 
to verify it.
  .
  
https://github.com/libvirt/libvirt/commit/e62cb4a9b78c7f4499a206635fb4f06e6ac627e5
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1758037/+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 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

2018-03-08 Thread Andrew Cloke

** Changed in: makedumpfile (Ubuntu Trusty)
   Status: New => Invalid

-- 
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/1658733

Title:
  Ubuntu 16.04 KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Invalid
Status in kexec-tools source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  >

[Group.of.nepali.translators] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2018-03-05 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1732032

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Released
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Won't Fix
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1

  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32

[Group.of.nepali.translators] [Bug 1709784] Re: KVM on 16.04.3 throws an error

2017-11-06 Thread Andrew Cloke

Based on comments above, moving to "Fix Released". If this issue re-
occurs, please update with a new comment.

** Changed in: ubuntu-power-systems
   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/1709784

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102 ]---
  [

[Group.of.nepali.translators] [Bug 1705582] Re: Update Package request for lsvpd

2017-10-12 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1705582

Title:
  Update Package request for lsvpd

Status in The Ubuntu-power-systems project:
  Fix Released
Status in lsvpd package in Ubuntu:
  Fix Released
Status in lsvpd source package in Xenial:
  Fix Released

Bug description:
  SRU
  

  ---Problem Description---
  Update Package request for lsvpd

  ---uname output---
  Linux tuleta4u-lp9 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 
16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to Reproduce---
   lsvpd

  Userspace tool common name: lsvpd

  Please pull below patches for lsvpd package.

  --
  commit 7499dcc199da96befef7bb788d62e446833137b2
  Author: Ankit Kumar 
  Date:   Mon Dec 7 11:59:05 2015 +0530

  lsvpd: Unique name for temp Device file given and file closed
  before deleting it.

  This piece of code used mkstemp to get unique name of file in that 
particular
  directory. As file name is not hardcoded, so parameter for device_close 
and
  device_open is changed to pass device location path.

  This patch also fixes the issue of opened file which is not closed by 
closing
  file descriptor.

  Signed-off-by: Ankit Kumar 
  [Removed redundant variable - Vasant]
  Signed-off-by: Vasant Hegde 

  -

  Backported patch on top of 1.7.6 provided

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1705582/+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 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

2017-09-28 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1696102

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Fix Released

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+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 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

2017-09-22 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Fix Released => Fix Committed

-- 
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/1696102

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+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 1709877] Re: CPU hotplug fails in the system with empty numa nodes, "Invalid value '0-1, 16-17' for 'cpuset.mems': Invalid argument"

2017-09-13 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Invalid => Triaged

-- 
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/1709877

Title:
  CPU hotplug fails in the system with empty numa nodes, "Invalid value
  '0-1,16-17' for 'cpuset.mems': Invalid argument"

Status in The Ubuntu-power-systems project:
  Triaged
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Triaged

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-07-19 
04:13:18 ==
  CPU hotplug operation fails in the host with empty numa nodes(with no memory) 
even though VM placement is static and with/without numad is running.
  ..
   32
  ...

  
  # virsh setvcpus virt-tests-vm1 6 --live
  error: Invalid value '0-1,16-17' for 'cpuset.mems': Invalid argument

  
  # numactl --hardware
  available: 4 nodes (0-1,16-17)
  node 0 cpus: 0 8 16 24 32 40
  node 0 size: 16188 MB
  node 0 free: 1119 MB
  node 1 cpus: 48 56 64 72 80 88
  node 1 size: 32630 MB
  node 1 free: 13233 MB
  node 16 cpus: 96 104 112 120 128 136
  node 16 size: 0 MB
  node 16 free: 0 MB
  node 17 cpus: 144 152 160 168 176 184
  node 17 size: 0 MB
  node 17 free: 0 MB
  node distances:
  node   0   1  16  17 
0:  10  20  40  40 
1:  20  10  40  40 
   16:  40  40  10  20 
   17:  40  40  20  10 

  # cat /sys/fs/cgroup/cpuset/cpuset.mems 
  0-1

  Host:
  #uname -a
  Linux powerkvm4-lp1 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 
16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ii  libvirt-bin1.3.1-1ubuntu10.11 
  ii  numad  0.5+20150602-4 
  qemu-kvm   1:2.5+dfsg-5ubuntu10.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709877/+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 1670481] Re: Backport "populate PCI DT in reverse order" patch

2017-09-06 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Status: New => Fix Released

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

-- 
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/1670481

Title:
  Backport "populate PCI DT in reverse order" patch

Status in The Ubuntu-power-systems project:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Invalid
Status in qemu source package in Yakkety:
  Won't Fix
Status in qemu source package in Zesty:
  Fix Released

Bug description:
  == Comment: #0 - MIKHAIL S. MEDVEDEV  - 2017-03-03 
14:21:43 ==
  ---Problem Description---
  On ppc64el qemu the order of device scanning was recently changed, causing 
device names to be in reverse order compared to e.g. x86. This is creating a 
need for all sorts of work arounds to make the code that assumes certain order 
of devices to work on Power.

  The fix has been proposed and it appears it would go into Qemu 2.9, see [1]. 
It might be awhile until qemu 2.9 gets widely adopted as default. It would be 
beneficial if the fix can be backported to an earlier versions of Qemu.
   
  [1] http://patchwork.ozlabs.org/patch/731061/

  ---uname output---
  Linux devstack-xenial-ppc64-84615 4.8.0-39-generic #42~16.04.1-Ubuntu SMP Mon 
Feb 20 15:09:38 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-21L 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---

   
  Contact Information = Mikhail Medvedev mmedv...@us.ibm.com / Tiago Rodrigues 
de Mello tme...@br.ibm.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1670481/+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 1709877] Re: CPU hotplug fails in the system with empty numa nodes, "Invalid value '0-1, 16-17' for 'cpuset.mems': Invalid argument"

2017-09-06 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

-- 
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/1709877

Title:
  CPU hotplug fails in the system with empty numa nodes, "Invalid value
  '0-1,16-17' for 'cpuset.mems': Invalid argument"

Status in The Ubuntu-power-systems project:
  Invalid
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-07-19 
04:13:18 ==
  CPU hotplug operation fails in the host with empty numa nodes(with no memory) 
even though VM placement is static and with/without numad is running.
  ..
   32
  ...

  
  # virsh setvcpus virt-tests-vm1 6 --live
  error: Invalid value '0-1,16-17' for 'cpuset.mems': Invalid argument

  
  # numactl --hardware
  available: 4 nodes (0-1,16-17)
  node 0 cpus: 0 8 16 24 32 40
  node 0 size: 16188 MB
  node 0 free: 1119 MB
  node 1 cpus: 48 56 64 72 80 88
  node 1 size: 32630 MB
  node 1 free: 13233 MB
  node 16 cpus: 96 104 112 120 128 136
  node 16 size: 0 MB
  node 16 free: 0 MB
  node 17 cpus: 144 152 160 168 176 184
  node 17 size: 0 MB
  node 17 free: 0 MB
  node distances:
  node   0   1  16  17 
0:  10  20  40  40 
1:  20  10  40  40 
   16:  40  40  10  20 
   17:  40  40  20  10 

  # cat /sys/fs/cgroup/cpuset/cpuset.mems 
  0-1

  Host:
  #uname -a
  Linux powerkvm4-lp1 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 
16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ii  libvirt-bin1.3.1-1ubuntu10.11 
  ii  numad  0.5+20150602-4 
  qemu-kvm   1:2.5+dfsg-5ubuntu10.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709877/+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 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

2017-09-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: In Progress => 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/1689946

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689946/+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 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create

2017-09-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1651518

Title:
  systemd/logind parsing problem: HTX exercisers stopped on error: rc
  11, errno 11 from main(): pthread_create

Status in The Ubuntu-power-systems project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Before systemd 232, UserTasksMax=infinity is not respected in logind.conf, 
despite the documentation referring to systemd.resource-control(5) for the 
definition of this field. This limits the use of Ubuntu 16.04 and later in 
contexts where a user session should be permitted to allocate large numbers of 
processes.

  [Test case]
  1. Set UserTasksMax=infinity in /etc/systemd/logind.conf.
  2. Create a new login session.
  3. Check the ulimit for user processes with 'ulimit -u'.
  4. Verify that the limit has a numeric value.
  5. Upgrade to systemd from -proposed.
  6. Create a new login session.
  7. Check the ulimit for user processes with 'ulimit -u'.
  8. Verify that the limit is now set to 'unlimited'.

  [Regression potential]
  This is an upstream patch which is part of 232 and later without issues and 
clearly addresses the bug in question.  While the upstream commit includes code 
changes that are not strictly required in order to fix this bug, these are 
mostly cosmetic and should not carry significant additional risk.


  == Comment: #1 - Application Cdeadmin  -
  2016-12-19 04:15:10 ==

  Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk
  drawers, HDD (180) 7.3TB

  Problem: HTX exercisers stopped on error, with HTX log showing "rc 11,
  errno 11 from main(): pthread_create"

  htxubuntu-425

  lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd)

  root@busybee:~# uname -a
  Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@busybee:~# cat /tmp/htxerr

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  No errors logged in syslog after starting HTX:

   State: Open by: asperez on 16 December 2016 10:28:02 
  This error recreated on the smaller 1U Open Power system with the same 
smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the 
drawer (one to each ESM) that requires multipath enabled.

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

  /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdak Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdt  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdaz Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdn  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdv  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdaj Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdal Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

   State: Open by: cde00 on 19 December 2016 02:48:46 

  This defect will go to Linux as even after making the below 2 changes
  in systemd resource limit, errors are seen:

  root@yellowbee:/etc/systemd/logind.conf.d#

[Group.of.nepali.translators] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

2017-08-22 Thread Andrew Cloke

** Changed in: linux (Ubuntu)
   Status: Invalid => New

** Changed in: linux (Ubuntu Trusty)
   Status: Invalid => New

** Changed in: linux (Ubuntu Xenial)
   Status: Invalid => New

** Changed in: linux (Ubuntu Zesty)
   Status: Invalid => 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/1635597

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache:

[Group.of.nepali.translators] [Bug 1628520] Re: nvme: Missing patch in Ubuntu-4.4.0-41.61

2017-02-27 Thread Andrew Cloke

Marking "root" bug as fix released, as the bug is specifically against
the Xenial 4.4 kernel, and that is "Fix Released".

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

** Changed in: linux (Ubuntu)
   Status: New => 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/1628520

Title:
  nvme: Missing patch in Ubuntu-4.4.0-41.61

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Gabriel Krisman Bertazi  - 2016-09-27 
22:59:44 ==
  Ubuntu-4.4.0-40.60 included my backport of :

  b00a726a9fd ("NVMe: Don't unmap controller registers on reset") #upstream 
commit
[ 30d6592fce71 on the Ubuntu -proposed branch]

  But missed the fix up that came later:

  81e9a969c441 ("nvme: Call pci_disable_device on the error path.") #
  4.4.y tree

  This means that we may hit an Oops if we need to go into the error
  path of  the nvme probe.

  
  Please cherry-pick this fix to your kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628520/+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

41 matches

Mail list logo