[Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Manoj Iyer]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773162

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773964] Re: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773964

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

As per the kernel team, release from -proposed to -updates should happen
today. June 11th.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Manoj Iyer]

** Tags removed: triage-g
** Tags added: triage-a

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765364

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel

[Manoj Iyer]

Looks like the bionic-proposed kernel works for IBM, and so marking this
fix-committed.

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768898] Re: smp_call_function_single/many core hangs with stop4 alone

[Manoj Iyer]

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

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768898

Title:
  smp_call_function_single/many core hangs with stop4 alone

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

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

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Manoj Iyer]

** Tags removed: triage-a
** Tags added: triage-g

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.

[Manoj Iyer]

These patches were accepted and are in route for 18.04.1.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759723

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel

[Manoj Iyer]

** Tags added: triage-a

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1757402] Re: Ubuntu18.04:pKVM - Host in hung state and out of network after few hours of stress run on all guests

[Manoj Iyer]

** Changed in: linux (Ubuntu Artful)
   Status: Incomplete => Won't Fix

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757402

Title:
  Ubuntu18.04:pKVM - Host  in hung state and out of network after few
  hours of stress run on all guests

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773162

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776211

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751986] Re: [LTCTest][OPAL][OP920] lsmcode -A is not showing any output

[Manoj Iyer]

** Description changed:

+ -- SRU Bionic --
+ [Impact]
+ lsmcode does not display product version information on Power system (AC922) 
with OPAL firmware (OP920). 
+ 
+ [Test]
+ Running lsmcode -A command on Power system does not print the "Product 
Version" information.
+ $ sudo lsmcode -A | grep "Product Version" || { echo "failed to print product 
version"; exit ; }
+ 
+ [Fix]
+ Comment #3 identifies the patches needed to fix this issue.
+ 
+ [Regression Potential]
+ None
+ 
+ 
  == Comment: #5 - Pridhiviraj Paidipeddi  - 2018-02-26 
11:02:21 ==
  We are missing Product Version in lsmcode output, due to which "lsmcode -A" 
fails.
  lsmcode(incorrect output)
  =
  Version of System Firmware :
   Product Name  : OpenPOWER Firmware
   Product Extra :  occ-fce2d94
   Product Extra :  skiboot-v5.9-238-g43eb8bbcbaa5
   Product Extra :  buildroot-2017.11-5-g65679be
   Product Extra :  capp-ucode-p9-dd2-v2
   Product Extra :  petitboot-v1.6.6-p91994c3
   Product Extra :  sbe-86ae83c
   Product Extra :  hostboot-binaries-8b5adb5
   Product Extra :  machine-xml-4374657
   Product Extra :  hostboot-52ca812
   Product Extra :  linux-4.14.13-openpower1-pdb952b4
  
  lsmcode(correct output)
  
  Version of System Firmware :
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee
  
  So we need two fixes here, one is to form Product Version string and
  another one is to fix "lsmcode -A"  empty output bug when there is no
  Product Version available.
  
  == Comment: #6 - Pridhiviraj Paidipeddi  - 2018-02-26 
11:10:23 ==
  Attached patch will fix "lsmcode -A" empty output issue.
  
  [root@ltc-wspoon2 lsvpd]# ./lsmcode -A
  enP5p1s0f0 !.5719-v1.43 NCSI v1.3.12.0
  enP5p1s0f1 !.5719-v1.43 NCSI v1.3.12.0
  sg0 0:0:0:0 sda !ST1000NX0313.BE35
  sg1 1:0:0:0 sdb !ST1000NX0313.BE35
  [root@ltc-wspoon2 lsvpd]# ./lsmcode -v
  lsmcode 1.7.8
  [root@ltc-wspoon2 lsvpd]# ./lsmcode
  Version of System Firmware :
   Product Name  : OpenPOWER Firmware
   Product Extra :  occ-fce2d94
   Product Extra :  skiboot-v5.9-238-g43eb8bbcbaa5
   Product Extra :  buildroot-2017.11-5-g65679be
   Product Extra :  capp-ucode-p9-dd2-v2
   Product Extra :  petitboot-v1.6.6-p91994c3
   Product Extra :  sbe-86ae83c
   Product Extra :  hostboot-binaries-8b5adb5
   Product Extra :  machine-xml-4374657
   Product Extra :  hostboot-52ca812
   Product Extra :  linux-4.14.13-openpower1-pdb952b4
  
  Tested on a AC922 system where the failure occurs when it is having a
  firmware OP920.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751986

Title:
  [LTCTest][OPAL][OP920] lsmcode -A is not showing any output

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716517] Re: [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

[Manoj Iyer]

@ahasenack yes I would need, I dont have the powers to upload.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716517

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1775242] Re: [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing doorbell

[Manoj Iyer]

A test kernel with the patch applied is available in:
https://launchpad.net/~manjo/+archive/ubuntu/lp1775242

To enable this ppa: 
$ sudo add-apt-repository -y ppa:manjo/lp1775242
$ sudo apt-get update

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775242

Title:
  [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing
  doorbell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1775242] [NEW] [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing doorbell

[Manoj Iyer]

Public bug reported:

[Impact]
RDMA applications might hang with qlogic cards. This happens because
of a bug in the doorbell implementation.

[Test]
1) Set IP addresses on both server and client
2) On RoCE Server run "ib_send_bw -d qedr0 -x 2 -R"
3) On RoCE client run "ib_send_bw -d qedr0 -x 2  -R"
4) Notice that the command fails to run

[Fix]
30bf066cd998 RDMA/qedr: Fix doorbell bar mapping for dpi > 1

[Regression Potential]
None

** Affects: linux (Ubuntu)
 Importance: Critical
 Status: Incomplete


** Tags: artful cavium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775242

Title:
  [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing
  doorbell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Please review and consider this debdiff to iperf that fixes this iperf
bug for Xenial

** Patch added: "[Xenial] iperf debdiff"
   
https://bugs.launchpad.net/debian/+source/iperf/+bug/1771283/+attachment/5149036/+files/xenial-fix-for-iperf2-long-time-run-on-40Gb-s-NIC-crashes-f.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Please review and consider this debdiff to iperf that fixes this iperf
bug for Artful

** Patch added: "[Artful] iperf debdiff"
   
https://bugs.launchpad.net/debian/+source/iperf/+bug/1771283/+attachment/5149034/+files/artful-fix-for-iperf2-long-time-run-on-40Gb-s-NIC-crashes-f.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Please review and consider this debdiff to iperf that fixes this iperf
bug for Bionic

** Patch added: "[Bionic] iperf debdiff"
   
https://bugs.launchpad.net/debian/+source/iperf/+bug/1771283/+attachment/5149020/+files/bionic-fix-for-iperf2-long-time-run-on-40Gb-s-NIC-crashes-f.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

** Bug watch added: Debian Bug tracker #900793
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900793

** Also affects: iperf (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900793
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Please review and consider this debdiff to iperf that fixes this iperf
bug for cosmic.

A build with this patch is available in  ppa:manjo/iperf

** Patch added: "[Cosmic] debdiff for iperf"
   
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+attachment/5148789/+files/fix-for-iperf2-long-time-run-on-40Gb-s-NIC-crashes-f.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770254] Re: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic.

[Manoj Iyer]

-- Host with -proposed kernel --

ubuntu@anuchin:~$ virsh nodedev-detach pci_0002_01_00_1
Device pci_0002_01_00_1 detached

ubuntu@anuchin:~$

ubuntu@anuchin:~$ readlink /sys/bus/pci/devices/0002\:01\:00.1/driver
../../../../../../../bus/pci/drivers/vfio-pci
ubuntu@anuchin:~$

-- Bionic Guest --
ubuntu@ubuntu-pcitest:~$ lspci -k
00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge
Subsystem: Red Hat, Inc QEMU PCIe Host bridge
00:01.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01)
Subsystem: Red Hat, Inc Virtio network device
Kernel driver in use: virtio-pci
02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01)
Subsystem: Red Hat, Inc Virtio console
Kernel driver in use: virtio-pci
03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
Subsystem: Red Hat, Inc Virtio block device
Kernel driver in use: virtio-pci
04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
Subsystem: Red Hat, Inc Virtio block device
Kernel driver in use: virtio-pci
05:00.0 Ethernet controller: Cavium, Inc. THUNDERX Network Interface Controller 
virtual function (rev 08)
Subsystem: Cavium, Inc. THUNDERX Network Interface Controller virtual 
function
Kernel modules: nicvf
ubuntu@ubuntu-pcitest:~$


** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770254

Title:
  [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI
  devices results in a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Thank you for applying that, I will SRU that to Bionic/Artful/Xenial for
Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Robert,

Please review and consider this patch to iperf to fix the segfault.
Looks like in function byte_snprintf() when calculating SUM, where SUM
is in terabyte, we go past the kLabel_Byte/kLabel_bit array limit (by
increment of conv past kConv_Giga)  and this causes iperf to segfault
because suffix is pointing past the array bounds. The attached patch
addresses this issue.

-- Before patch --
$ iperf -c 192.168.120.2 -P10 -w 130k -t 1200

Client connecting to 192.168.120.2, TCP port 5001
TCP window size:  254 KByte (WARNING: requested  127 KByte)

[ 12] local 192.168.120.3 port 47668 connected with 192.168.120.2 port 5001
[ 10] local 192.168.120.3 port 47664 connected with 192.168.120.2 port 5001
[ 11] local 192.168.120.3 port 47666 connected with 192.168.120.2 port 5001
[  8] local 192.168.120.3 port 47662 connected with 192.168.120.2 port 5001
[  5] local 192.168.120.3 port 47656 connected with 192.168.120.2 port 5001
[  4] local 192.168.120.3 port 47650 connected with 192.168.120.2 port 5001
[  6] local 192.168.120.3 port 47654 connected with 192.168.120.2 port 5001
[  9] local 192.168.120.3 port 47660 connected with 192.168.120.2 port 5001
[  7] local 192.168.120.3 port 47658 connected with 192.168.120.2 port 5001
[  3] local 192.168.120.3 port 47652 connected with 192.168.120.2 port 5001
 [ ID] Interval   Transfer Bandwidth
[ 12]  0.0-1200.0 sec  73.3 GBytes   525 Mbits/sec
[ 10]  0.0-1200.0 sec   164 GBytes  1.17 Gbits/sec
[ 11]  0.0-1200.0 sec   219 GBytes  1.57 Gbits/sec
[  8]  0.0-1200.0 sec  73.3 GBytes   525 Mbits/sec
[  5]  0.0-1200.0 sec   164 GBytes  1.18 Gbits/sec
[  4]  0.0-1200.0 sec   165 GBytes  1.18 Gbits/sec
[  6]  0.0-1200.0 sec   109 GBytes   784 Mbits/sec
[  9]  0.0-1200.0 sec   165 GBytes  1.18 Gbits/sec
[  7]  0.0-1200.0 sec   109 GBytes   783 Mbits/sec
[  3]  0.0-1200.0 sec  73.3 GBytes   525 Mbits/sec
Segmentation fault (core dumped)

-- After patch --
$ src/iperf -c 192.168.120.2 -P10 -w 130k -t 1200

Client connecting to 192.168.120.2, TCP port 5001
TCP window size:  254 KByte (WARNING: requested  127 KByte)

[ 12] local 192.168.120.3 port 47626 connected with 192.168.120.2 port 5001
[  8] local 192.168.120.3 port 47616 connected with 192.168.120.2 port 5001
[ 10] local 192.168.120.3 port 47622 connected with 192.168.120.2 port 5001
[  3] local 192.168.120.3 port 47610 connected with 192.168.120.2 port 5001
[  9] local 192.168.120.3 port 47620 connected with 192.168.120.2 port 5001
[  4] local 192.168.120.3 port 47608 connected with 192.168.120.2 port 5001
[  7] local 192.168.120.3 port 47614 connected with 192.168.120.2 port 5001
[ 11] local 192.168.120.3 port 47624 connected with 192.168.120.2 port 5001
[  5] local 192.168.120.3 port 47612 connected with 192.168.120.2 port 5001
[  6] local 192.168.120.3 port 47618 connected with 192.168.120.2 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-1200.0 sec   142 GBytes  1.02 Gbits/sec
[  9]  0.0-1200.0 sec   120 GBytes   862 Mbits/sec
[ 11]  0.0-1200.0 sec   121 GBytes   867 Mbits/sec
[  5]  0.0-1200.0 sec   122 GBytes   874 Mbits/sec
[ 12]  0.0-1200.0 sec   120 GBytes   856 Mbits/sec
[  8]  0.0-1200.0 sec   122 GBytes   871 Mbits/sec
[ 10]  0.0-1200.0 sec   146 GBytes  1.04 Gbits/sec
[  4]  0.0-1200.0 sec   141 GBytes  1.01 Gbits/sec
[  7]  0.0-1200.0 sec   122 GBytes   873 Mbits/sec
[  6]  0.0-1200.0 sec   143 GBytes  1.02 Gbits/sec
[SUM]  0.0-1200.0 sec  1299 GBytes  9.30 Gbits/sec


** Patch added: "fix segfault in iperf"
   
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+attachment/5147771/+files/0001-Fix-segfault-while-calculating-sum-on-long-iperf-run.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking

[Manoj Iyer]

-- Bionic verification --
ubuntu@starbuck:~$ uname -a 
Linux starbuck 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$ dmesg | grep -i "W+X"
[   34.983869] Checked W+X mappings: passed, no W+X pages found
ubuntu@starbuck:~$ 

-- Artful verification --
ubuntu@starbuck:~$ uname -a 
Linux starbuck 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:03 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$dmesg | grep -i "W+X"
[   35.566350] Checked W+X mappings: passed, no W+X pages found
ubuntu@starbuck:~$ 

-- Xenial Verification --
ubuntu@seuss:~$ uname -a 
Linux seuss 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:17:06 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@seuss:~$ dmesg | grep -i "W+X"
ubuntu@seuss:~$ 


** Tags removed: verification-needed-artful verification-needed-bionic 
verification-needed-xenial
** Tags added: verification-done-artful verification-done-bionic 
verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769696

Title:
  [SRU][Bionic/Artful] fix false positives in W+X checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Robert, could you pls give me the git repo or source for iperf? Or would
a debdiff of the version in ubuntu bionic work just fine?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Available in PPA: ppa:manjo/lp1771283

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

After fixing that bug iperf no longer seg faults. I will submit an SRU
for B/A/X releases.

ubuntu@recht:~/iperf-2.0.10+dfsg1$ src/iperf -c 192.168.120.2 -P10 -w 130k -t 
3600

Client connecting to 192.168.120.2, TCP port 5001
TCP window size:  254 KByte (WARNING: requested  127 KByte)

[ 11] local 192.168.120.3 port 58206 connected with 192.168.120.2 port 5001
[  4] local 192.168.120.3 port 58192 connected with 192.168.120.2 port 5001
[  5] local 192.168.120.3 port 58194 connected with 192.168.120.2 port 5001
[  3] local 192.168.120.3 port 58196 connected with 192.168.120.2 port 5001
[  7] local 192.168.120.3 port 58198 connected with 192.168.120.2 port 5001
[  6] local 192.168.120.3 port 58200 connected with 192.168.120.2 port 5001
[  9] local 192.168.120.3 port 58202 connected with 192.168.120.2 port 5001
[ 10] local 192.168.120.3 port 58204 connected with 192.168.120.2 port 5001
[ 12] local 192.168.120.3 port 58208 connected with 192.168.120.2 port 5001
[  8] local 192.168.120.3 port 58210 connected with 192.168.120.2 port 5001
[ ID] Interval   Transfer Bandwidth
[ 11]  0.0-3600.0 sec   157 GBytes   376 Mbits/sec
[  4]  0.0-3600.0 sec   986 GBytes  2.35 Gbits/sec
[  5]  0.0-3600.0 sec   981 GBytes  2.34 Gbits/sec
[  3]  0.0-3600.0 sec   113 GBytes   269 Mbits/sec
[  7]  0.0-3600.0 sec   495 GBytes  1.18 Gbits/sec
[  6]  0.0-3600.0 sec   493 GBytes  1.18 Gbits/sec
[  9]  0.0-3600.0 sec   257 GBytes   614 Mbits/sec
[ 10]  0.0-3600.0 sec   112 GBytes   268 Mbits/sec
[ 12]  0.0-3600.0 sec   113 GBytes   270 Mbits/sec
[  8]  0.0-3600.0 sec   238 GBytes   568 Mbits/sec
[SUM]  0.0-3600.0 sec  4236189630464 bits  9.41 Gbits/sec

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

byte_snprintf() calls snprintf() with a bad format pointer and
snprintf() segfaults. The root cause of the bad pointer is very elusive
because there is so much information being printed. Further debug needed
to find out the root cause.

-- with GDB and debug --
(gdb) bt
#0  strlen () at ../sysdeps/aarch64/strlen.S:94
#1  0xa35b5f18 in _IO_vfprintf_internal (s=s@entry=0x99ffa578,
format=format@entry=0xd52878f0 "%4.0f %s", ap=...) at vfprintf.c:1643
#2  0xa364ca64 in ___vsnprintf_chk (
s=s@entry=0xd529a280  "4235479613440 ",
maxlen=, maxlen@entry=32, flags=flags@entry=1,
slen=slen@entry=18446744073709551615, format=0xd52878f0 "%4.0f %s",
args=...) at vsnprintf_chk.c:63
#3  0xa364c980 in ___snprintf_chk (
s=s@entry=0xd529a280  "4235479613440 ",
maxlen=maxlen@entry=32, flags=flags@entry=1, 
slen=slen@entry=18446744073709551615, format=)
at snprintf_chk.c:34
#4  0xd5283cb8 in snprintf (__fmt=, __n=32,
__s=0xd529a280  "4235479613440 ")
at /usr/include/aarch64-linux-gnu/bits/stdio2.h:64
#5  byte_snprintf (
outString=outString@entry=0xd529a280  "4235479613440 ",
inLen=inLen@entry=32, inNum=, inFormat=)
at stdio.c:247
#6  0xd527d928 in reporter_multistats (stats=0xaaab104a38e0)
at ReportDefault.c:205
#7  0xd527f264 in reporter_print (stats=0xaaab104a3850,
type=type@entry=16, end=end@entry=1) at Reporter.c:1154
#8  0xd527f628 in reporter_handle_multiple_reports (
reporthdr=reporthdr@entry=0xaaab104a37c0,
stats=stats@entry=0xa03910a8, force=force@entry=1) at Reporter.c:996
#9  0xd527f938 in reporter_condprintstats (stats=0xa0391018,
multireport=0xaaab104a37c0, force=1) at Reporter.c:1075
#10 0xd527fd6c in reporter_process_report (reporthdr=0xa0391010)
at Reporter.c:759
#11 0xd527fdfc in reporter_process_report (reporthdr=0xa04cb010)
at Reporter.c:719
#12 0xd527fdfc in reporter_process_report (reporthdr=0xa01ba010)
at Reporter.c:719
#13 0xd527fdfc in reporter_process_report (reporthdr=0xa0080010)
at Reporter.c:719
#14 0xd527fdfc in reporter_process_report (
reporthdr=reporthdr@entry=0xa02f4010) at Reporter.c:719
#15 0xd527ff10 in reporter_spawn (thread=0xaaab104a5cd0)
at Reporter.c:627
#16 0xd52843cc in thread_run_wrapper (paramPtr=0xaaab104a5cd0)
at Thread.c:247
#17 0xa36ce088 in start_thread (arg=0xc669f3ff)
at pthread_create.c:463
#18 0xa363e4ec in thread_start ()
at ../sysdeps/unix/sysv/linux/aarch64/clone.S:78

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

-- Core dump with gdb --
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
Core was generated by `iperf -c 192.168.120.2 -P10 -w 130k -t 3600'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  strlen () at ../sysdeps/aarch64/strlen.S:94
94  ../sysdeps/aarch64/strlen.S: No such file or directory.
[Current thread is 1 (Thread 0x827fc1d0 (LWP 3788))]
(gdb) bt
#0  strlen () at ../sysdeps/aarch64/strlen.S:94
#1  0x9b2caf18 in _IO_vfprintf_internal (s=s@entry=0x827fb5f8, 
format=format@entry=0xe1c3b0a8 "%4.0f %s", ap=...) at vfprintf.c:1643
#2  0x9b361a64 in ___vsnprintf_chk (
s=0xe1c4e280  "4227448246536 ", maxlen=, 
flags=1, slen=, format=0xe1c3b0a8 "%4.0f %s", args=...)
at vsnprintf_chk.c:63
#3  0x9b361980 in ___snprintf_chk (s=, 
maxlen=, flags=, slen=, 
format=) at snprintf_chk.c:34
#4  0xe1c310d0 in ?? ()
#5  0x0001 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: ./configure --enable-arm needed for ARM events

[Manoj Iyer]

I have posted test results to
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978

** Tags removed: verification-needed verification-needed-artful 
verification-needed-bionic verification-needed-xenial
** Tags added: verification-done verification-done-artful 
verification-done-bionic verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758205

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Manoj Iyer]

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

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773162

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770095] Re: Need fix to aacraid driver to prevent panic

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770095

Title:
  Need fix to aacraid driver to prevent panic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

-- bionic verification --
ubuntu@awrep2:~$ sudo apt install -y rasdaemon
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libdbd-sqlite3-perl libdbi-perl sqlite3
Suggested packages:
  libclone-perl libmldbm-perl libnet-daemon-perl libsql-statement-perl
  sqlite3-doc
The following NEW packages will be installed:
  libdbd-sqlite3-perl libdbi-perl rasdaemon sqlite3
0 upgraded, 4 newly installed, 0 to remove and 25 not upgraded.
Need to get 1553 kB of archives.
After this operation, 4981 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 libdbi-perl arm64 
1.640-1 [716 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports bionic/universe arm64 
libdbd-sqlite3-perl arm64 1.56-1 [135 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 sqlite3 arm64 
3.22.0-1 [634 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/universe arm64 
rasdaemon arm64 0.6.0-1ubuntu0.1 [68.3 kB]
Fetched 1553 kB in 1s (2224 kB/s)
Selecting previously unselected package libdbi-perl.
(Reading database ... 28570 files and directories currently installed.)
Preparing to unpack .../libdbi-perl_1.640-1_arm64.deb ...
Unpacking libdbi-perl (1.640-1) ...
Selecting previously unselected package libdbd-sqlite3-perl.
Preparing to unpack .../libdbd-sqlite3-perl_1.56-1_arm64.deb ...
Unpacking libdbd-sqlite3-perl (1.56-1) ...
Selecting previously unselected package sqlite3.
Preparing to unpack .../sqlite3_3.22.0-1_arm64.deb ...
Unpacking sqlite3 (3.22.0-1) ...
Selecting previously unselected package rasdaemon.
Preparing to unpack .../rasdaemon_0.6.0-1ubuntu0.1_arm64.deb ...
Unpacking rasdaemon (0.6.0-1ubuntu0.1) ...
Setting up sqlite3 (3.22.0-1) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up libdbi-perl (1.640-1) ...
Setting up libdbd-sqlite3-perl (1.56-1) ...
Setting up rasdaemon (0.6.0-1ubuntu0.1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/rasdaemon.service → 
/lib/systemd/system/rasdaemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/ras-mc-ctl.service 
→ /lib/systemd/system/ras-mc-ctl.service.
ubuntu@awrep2:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Wed 2018-05-23 18:15:05 UTC; 12s ago
 Main PID: 14212 (rasdaemon)
Tasks: 1 (limit: 7065)
   CGroup: /system.slice/rasdaemon.service
   └─14212 /usr/sbin/rasdaemon -f -r

May 23 18:15:05 awrep2 rasdaemon[14212]: ras:arm_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14212]: Enabled event ras:arm_event
May 23 18:15:05 awrep2 rasdaemon[14212]: Can't parse /proc/cpuinfo: missing [ven
May 23 18:15:05 awrep2 rasdaemon[14212]: Can't register mce handler
May 23 18:15:05 awrep2 rasdaemon[14212]: Can't get traces from ras:aer_event
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Recording mc_event events
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Recording aer_event events
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Recording extlog_event event
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Recording mce_record events
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Recording arm_event events

ubuntu@awrep2:~$ grep rasdaemon /var/log/syslog 
May 23 18:15:05 awrep2 rasdaemon: ras:mc_event event enabled
May 23 18:15:05 awrep2 rasdaemon: ras:mc_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14213]: rasdaemon: ras:mc_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14213]: rasdaemon: ras:aer_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14213]: rasdaemon: Can't write to set_event
May 23 18:15:05 awrep2 rasdaemon[14213]: rasdaemon: Can't write to set_event
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: ras:mc_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Enabled event ras:mc_event
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: ras:aer_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Enabled event ras:aer_event
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: ras:arm_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Enabled event ras:arm_event
May 23 18:15:05 awrep2 rasdaemon: Enabled event ras:mc_event
May 23 18:15:05 awrep2 rasdaemon[14213]: rasdaemon: ras:arm_event event enabled
May 23 18:15:05 awrep2 rasdaemon: ras:aer_event event enabled
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Can't parse /proc/cpuinfo: 
missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Can't register mce handler
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Can't get 
ras:extlog_mem_event traces. Perhaps this feature is not supported on your 
system.
May 23 18:15:05 awrep2 rasdaemon[14212]: rasdaemon: Can't get traces from 
ras:aer_event
May 

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

-- Artful verification --
ubuntu@awrep2:~$ sudo apt install rasdaemon
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  sqlite3
Suggested packages:
  sqlite3-doc
The following NEW packages will be installed:
  rasdaemon sqlite3
0 upgraded, 2 newly installed, 0 to remove and 26 not upgraded.
Need to get 651 kB of archives.
After this operation, 2356 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ports.ubuntu.com/ubuntu-ports artful/main arm64 sqlite3 arm64 
3.19.3-3 [583 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports artful-proposed/universe arm64 
rasdaemon arm64 0.5.8-1ubuntu2.1 [68.3 kB]
Fetched 651 kB in 0s (1553 kB/s)   
Selecting previously unselected package sqlite3.
(Reading database ... 63686 files and directories currently installed.)
Preparing to unpack .../sqlite3_3.19.3-3_arm64.deb ...
Unpacking sqlite3 (3.19.3-3) ...
Selecting previously unselected package rasdaemon.
Preparing to unpack .../rasdaemon_0.5.8-1ubuntu2.1_arm64.deb ...
Unpacking rasdaemon (0.5.8-1ubuntu2.1) ...
Setting up sqlite3 (3.19.3-3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up rasdaemon (0.5.8-1ubuntu2.1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/rasdaemon.service → 
/lib/systemd/system/rasdaemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/ras-mc-ctl.service 
→ /lib/systemd/system/ras-mc-ctl.service.
ubuntu@awrep2:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Wed 2018-05-23 18:06:59 UTC; 11s ago
 Main PID: 3417 (rasdaemon)
Tasks: 1 (limit: 7065)
   Memory: 7.9M
  CPU: 53ms
   CGroup: /system.slice/rasdaemon.service
   └─3417 /usr/sbin/rasdaemon -f -r

May 23 18:06:59 awrep2 rasdaemon[3417]: ras:arm_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3417]: Enabled event ras:arm_event
May 23 18:06:59 awrep2 rasdaemon[3417]: Can't parse /proc/cpuinfo: missing [vend
May 23 18:06:59 awrep2 rasdaemon[3417]: Can't register mce handler
May 23 18:06:59 awrep2 rasdaemon[3417]: Can't get traces from ras:aer_event
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Recording mc_event events
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Recording aer_event events
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Recording extlog_event events
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Recording mce_record events
May 23 18:07:00 awrep2 rasdaemon[3417]: rasdaemon: Recording arm_event events

ubuntu@awrep2:~$ grep rasdaemon /var/log/syslog 
May 23 18:06:59 awrep2 rasdaemon: ras:mc_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: ras:mc_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Enabled event ras:mc_event
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: ras:aer_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Enabled event ras:aer_event
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: ras:arm_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Enabled event ras:arm_event
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Can't parse /proc/cpuinfo: 
missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Can't register mce handler
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Can't get 
ras:extlog_mem_event traces. Perhaps this feature is not supported on your 
system.
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Can't get traces from 
ras:aer_event
May 23 18:06:59 awrep2 rasdaemon[3418]: rasdaemon: ras:mc_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3418]: rasdaemon: ras:aer_event event enabled
May 23 18:06:59 awrep2 rasdaemon[3418]: rasdaemon: Can't write to set_event
May 23 18:06:59 awrep2 rasdaemon[3418]: rasdaemon: Can't write to set_event
May 23 18:06:59 awrep2 rasdaemon[3418]: rasdaemon: ras:arm_event event enabled
May 23 18:06:59 awrep2 rasdaemon: Enabled event ras:mc_event
May 23 18:06:59 awrep2 rasdaemon[3417]: rasdaemon: Listening to events for cpus 
0 to 45
May 23 18:06:59 awrep2 rasdaemon: ras:aer_event event enabled
May 23 18:06:59 awrep2 rasdaemon: Enabled event ras:aer_event
May 23 18:06:59 awrep2 rasdaemon: ras:arm_event event enabled
May 23 18:06:59 awrep2 rasdaemon: Enabled event ras:arm_event
May 23 18:06:59 awrep2 rasdaemon: ras:mc_event event enabled
May 23 18:06:59 awrep2 rasdaemon: ras:aer_event event enabled
May 23 18:06:59 awrep2 rasdaemon: Can't write to set_event
May 23 18:06:59 awrep2 rasdaemon: Can't write to set_event
May 23 18:06:59 awrep2 rasdaemon: ras:arm_event event enabled
May 23 18:06:59 awrep2 rasdaemon: Can't parse /proc/cpuinfo: missing 
[vendor_id] [cpu family] [model] [cpu MHz] [flags]
May 23 18:06:59 awrep2 rasdaemon: Can't register mce handler
May 

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

-- verification xenial --
ubuntu@awrep2:~$ sudo apt install rasdaemon
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  sqlite3
Suggested packages:
  sqlite3-doc
The following NEW packages will be installed:
  rasdaemon sqlite3
0 upgraded, 2 newly installed, 0 to remove and 23 not upgraded.
Need to get 492 kB of archives.
After this operation, 1,932 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 sqlite3 arm64 
3.11.0-1ubuntu1 [428 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/universe arm64 
rasdaemon arm64 0.5.6-2ubuntu1.1 [64.1 kB]
Fetched 492 kB in 0s (1,205 kB/s)
Selecting previously unselected package sqlite3.
(Reading database ... 62682 files and directories currently installed.)
Preparing to unpack .../sqlite3_3.11.0-1ubuntu1_arm64.deb ...
Unpacking sqlite3 (3.11.0-1ubuntu1) ...
Selecting previously unselected package rasdaemon.
Preparing to unpack .../rasdaemon_0.5.6-2ubuntu1.1_arm64.deb ...
Unpacking rasdaemon (0.5.6-2ubuntu1.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up sqlite3 (3.11.0-1ubuntu1) ...
Setting up rasdaemon (0.5.6-2ubuntu1.1) ...
ubuntu@awrep2:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Wed 2018-05-23 17:40:03 UTC; 1min 1s ago
 Main PID: 4572 (rasdaemon)
Tasks: 1
   Memory: 7.8M
  CPU: 55ms
   CGroup: /system.slice/rasdaemon.service
   └─4572 /usr/sbin/rasdaemon -f -r

May 23 17:40:03 awrep2 rasdaemon[4572]: ras:arm_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4572]: Enabled event ras:arm_event
May 23 17:40:03 awrep2 rasdaemon[4572]: Can't parse /proc/cpuinfo: missing [vend
May 23 17:40:03 awrep2 rasdaemon[4572]: Can't register mce handler
May 23 17:40:03 awrep2 rasdaemon[4572]: Can't get traces from ras:aer_event
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording mc_event events
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording aer_event events
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording extlog_event events
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording mce_record events
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording arm_event events

ubuntu@awrep2:~$ 
ubuntu@awrep2:~$ grep rasdaemon /var/log/syslog 
May 23 17:40:03 awrep2 rasdaemon: ras:mc_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4573]: rasdaemon: ras:mc_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4573]: rasdaemon: ras:aer_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4573]: rasdaemon: Can't write to set_event
May 23 17:40:03 awrep2 rasdaemon[4573]: rasdaemon: Can't write to set_event
May 23 17:40:03 awrep2 rasdaemon[4573]: rasdaemon: ras:arm_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: ras:mc_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Enabled event ras:mc_event
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: ras:aer_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Enabled event ras:aer_event
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: ras:arm_event event enabled
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Enabled event ras:arm_event
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Can't parse /proc/cpuinfo: 
missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Can't register mce handler
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Can't get 
ras:extlog_mem_event traces. Perhaps this feature is not supported on your 
system.
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Can't get traces from 
ras:aer_event
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Listening to events for cpus 
0 to 45
May 23 17:40:03 awrep2 rasdaemon: Enabled event ras:mc_event
May 23 17:40:03 awrep2 rasdaemon: ras:aer_event event enabled
May 23 17:40:03 awrep2 rasdaemon: Enabled event ras:aer_event
May 23 17:40:03 awrep2 rasdaemon: ras:mc_event event enabled
May 23 17:40:03 awrep2 rasdaemon: ras:arm_event event enabled
May 23 17:40:03 awrep2 rasdaemon: Enabled event ras:arm_event
May 23 17:40:03 awrep2 rasdaemon: ras:aer_event event enabled
May 23 17:40:03 awrep2 rasdaemon: Can't write to set_event
May 23 17:40:03 awrep2 rasdaemon: Can't write to set_event
May 23 17:40:03 awrep2 rasdaemon: ras:arm_event event enabled
May 23 17:40:03 awrep2 rasdaemon: Can't parse /proc/cpuinfo: missing 
[vendor_id] [cpu family] [model] [cpu MHz] [flags]
May 23 17:40:03 awrep2 rasdaemon: Can't register mce handler
May 23 17:40:03 awrep2 rasdaemon: Can't get traces from ras:aer_event
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording mc_event events
May 23 17:40:03 awrep2 rasdaemon[4572]: rasdaemon: Recording 

[Bug 1772516] [NEW] [Config] enable EDAC_DEBUG on ARM64

[Manoj Iyer]

Public bug reported:

[Impact]
Testing EDAC requires EDAC_DEBUG to be enabled. ARM64 server customers 
currently need to rebuild Ubuntu kernels with this config option to test EDAC 
support. 

[Fix]
Enable EDAC_DEBUG config option in the kernel.

[Test]


[Regression Potential]
None. Limited to ARM64 architecture.

** Affects: linux (Ubuntu)
 Importance: High
 Status: New


** Tags: cn99xx

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772516

Title:
  [Config] enable EDAC_DEBUG on ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772516/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716517] Re: [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

[Manoj Iyer]

Bionic debdiff for openipmi

** Patch added: "Bionic debdiff for openipmi"
   
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1716517/+attachment/5142575/+files/bionic-openipmi.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716517

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716517] Re: [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

[Manoj Iyer]

Artful debdiff for openipmi

** Patch added: "Artful debdiff for openipmi"
   
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1716517/+attachment/5142576/+files/artful-openipmi.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716517

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716517] Re: [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

[Manoj Iyer]

Xenial debdiff for openipmi


** Patch added: "Xenial debdiff for openipmi"
   
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1716517/+attachment/5142577/+files/xenial-openipmi.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716517

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716517] Re: [arm64/ppc64le] load ipmi_ssif/ipmi_powernv instead of ipmi_si

[Manoj Iyer]

The patch is now in debian (unstable). Please consider the patch for
bionic, artful and xenial.

openipmi (2.0.25-2) unstable; urgency=medium

  * Fixed openipmi init file for other archs. Thanks Majon!
closes: Bug#875537
  * debian/copyright change to dep5 format

 -- Noël Köthe   Sat, 19 May 2018 11:04:51 +0200

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716517

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772509] [NEW] Sync openipmi 2.0.25-2 (main) from Debian unstable (main)

[Manoj Iyer]

Public bug reported:

Please sync openipmi 2.0.25-2 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * No-change rebuild for ncurses soname changes.
  * No change rebuild against openssl1.1.
  * No change rebuild against openssl1.1.
  * Merge with Debian unstable. Remaining changes:
- debian/openipmi.init: Change lockfile path. '/var/log/subsys' does
  not exists in Debian. (LP #722770)
- Fix up packaging to install and use /etc/default/openipmi.
  (LP #473332) Thanks to Serge Hallyn.
- Detect that a module is built into the kernel.
  + LP #1309860
- debian/openipmi.init: Do not unload all modules if some configured
  HW modules are not successfully loaded (LP #1318317).
- debian/openipmi.init: add Default-Start and Default-Stop values
  (LP #1596474).
- debian/patches/fix_pthread_pkg_config.patch: fix pkg-config files:
  pthread.pc does not exist in Ubuntu.  Thanks to Simon McVittie
  .  Closes #474087, LP #1311888.
  * Merge with Debian unstable. Remaining changes:
- debian/openipmi.init: Change lockfile path. '/var/log/subsys' does
  not exists in Debian. (LP #722770)
- Fix up packaging to install and use /etc/default/openipmi.
  (LP #473332) Thanks to Serge Hallyn.
- Detect that a module is built into the kernel.
  + LP #1309860
- debian/openipmi.init: Do not unload all modules if some configured
  HW modules are not successfully loaded (LP #1318317).
- debian/openipmi.init: add Default-Start and Default-Stop values
  (LP #1596474).
- debian/patches/fix_pthread_pkg_config.patch: fix pkg-config files:
  pthread.pc does not exist in Ubuntu.  Thanks to Simon McVittie
  .  Closes #474087, LP #1311888.
  * Merge with Debian unstable (LP: #1593461). Remaining changes:
- debian/openipmi.init: Change lockfile path. '/var/log/subsys' does
  not exists in Debian. (LP #722770)
- Fix up packaging to install and use /etc/default/openipmi.
  (LP #473332) Thanks to Serge Hallyn.
- Detect that a module is built into the kernel.
  + LP #1309860
- debian/openipmi.init: Do not unload all modules if some configured
  HW modules are not successfully loaded (LP #1318317).
- debian/openipmi.init: add Default-Start and Default-Stop values
  (LP #1596474).
- debian/patches/fix_pthread_pkg_config.patch: fix pkg-config files:
  pthread.pc does not exist in Ubuntu.  Thanks to Simon McVittie
  .  Closes #474087, LP #1311888.
  * Drop:
- debian/rules, debian/openipmi.init:
  + added init script
  [ Fixed in Debian ]
- Do not explicitly depend on pthread.
  [ previously documented ]
- Only use SIGPWR if defined.
  [ Previously undocumented ]
- Delete copyright.
  [ previously undocumented ]
- Add usr/sbin to debian/dirs
  [ previously undocumented ]
- d/watch: update for new location
  [ previously undocumented ]
- swig/pythong/openipmigui/Makefile: new file
  [ previously undocumented ]
- New upstream version.
  [ Debian has moved past ]
- Revert local changes to config.guess/config.sub; instead, use
  autotools-dev's debhelper integration to update these files for
  each build.
  [ Fixed in Debian ]
- Enabling openssl support as it is causing
  problems running third party applications. (closes #775847)
  (LP #1546735)
  [ Fixed in 2.0.21-1 ]
- Patch libtool macro support in for ppc64el shared libaries.
  [ Fixed in 2.0.16-1.4 by moving to autotools-dev ]
  * Merge with Debian unstable (LP: #1593461). Remaining changes:
- debian/openipmi.init: Change lockfile path. '/var/log/subsys' does
  not exists in Debian. (LP #722770)
- Fix up packaging to install and use /etc/default/openipmi.
  (LP #473332) Thanks to Serge Hallyn.
- Detect that a module is built into the kernel.
  + LP #1309860
- debian/openipmi.init: Do not unload all modules if some configured
  HW modules are not successfully loaded (LP #1318317).
- debian/openipmi.init: add Default-Start and Default-Stop values
  (LP #1596474).
- debian/patches/fix_pthread_pkg_config.patch: fix pkg-config files:
  pthread.pc does not exist in Ubuntu.  Thanks to Simon McVittie
  .  Closes #474087, LP #1311888.
  * Drop:
- debian/rules, debian/openipmi.init:
  + added init script
  [ Fixed in Debian ]
- Do not explicitly depend on pthread.
  [ previously documented ]
- Only use SIGPWR if defined.
  [ Previously undocumented ]
- Delete copyright.
  [ previously undocumented ]
- Add usr/sbin to debian/dirs
  [ previously undocumented ]
- d/watch: update for new location
  [ previously undocumented ]
- swig/pythong/openipmigui/Makefile: new file
  [ previously undocumented ]
- New upstream version.
 

[Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Tags added: p9

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771780

Title:
  [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and
  stop5 idle states when all CORES are guarded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

[Manoj Iyer]

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

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758205

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

[Manoj Iyer]

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

** Tags added: triage-g

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771813

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1752523] Re: Ubuntu 18.04 [ P9 WSP DD2.2 ]: lshw version is displayed as "unknown" and -json option is not available in help message.

[Manoj Iyer]

** Tags added: p9 ubuntu-18.04.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752523

Title:
  Ubuntu 18.04 [ P9 WSP DD2.2 ]: lshw version is displayed as "unknown"
  and -json option is not available in help message.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766527] Re: [ubuntu 18.04][netplan] Machine network goes down when second gateway is configured

[Manoj Iyer]

** Tags added: ubuntu-18.04.1

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766527

Title:
  [ubuntu 18.04][netplan] Machine network goes down when second gateway
  is configured

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766527] Re: [ubuntu 18.04][netplan] Machine network goes down when second gateway is configured

[Manoj Iyer]

** Changed in: netplan.io (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766527

Title:
  [ubuntu 18.04][netplan] Machine network goes down when second gateway
  is configured

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768115] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160.

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768115

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running
  with IO stress crashed@security_file_permission+0xf4/0x160.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751404] Re: cxl: patches for POWER9 support missing (CAPI)

[Manoj Iyer]

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751404

Title:
  cxl: patches for POWER9 support missing (CAPI)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

[Manoj Iyer]

Regarding introducing this new package in 18.04 (universe) here are the
next steps to consider.

1. This package would first need to make it into 18.10, this bug would 
accomplish that. 
2. Once it is introduced in 18.10, it needs to be tested, and tested to work 
with the 18.04 kernel.
3. Once it is tested and verified in 18.10 and with 18.04 kernel, *in a 
separate bug* request a backport of this package to 18.04.

It is my understanding that introducing this package in the 'universe'
archive would be the path of least resistance. Introducing this in the
'main' archive, have it included in the iso, and auto pre-installed etc
would be much harder.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771813

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

[Manoj Iyer]

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771813

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

[Manoj Iyer]

Is your packet size bigger than the MTU size? Could you use jumbo and
see if you still see this issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771344] Re: Fix enabling bridge MMIO windows

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu)
   Importance: Critical => High

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771344

Title:
  Fix enabling bridge MMIO windows

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

Sorry, my apologies .. I misunderstood your requirement ..again.. I have
bumped the kernel version to 4.15.0-21 from 4.15.0-20. After you install
you should be able to choose between old and new kernel. It will take
approx 5hrs for the kernel to be published in the PPA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

I don't see the issue you are reporting. I don't have the storage device
that uses this driver, but I am able to install the new kernel from PPA
and load the qla2xxx driver on our P9.

ubuntu@dradis:~$ uname -a 
Linux dradis 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

ubuntu@dradis:~$ sudo add-apt-repository -y ppa:ubuntu-power-
triage/lp1770003

ubuntu@dradis:~$ apt search linux-image-unsigned
Sorting... Done
Full Text Search... Done
linux-image-unsigned-4.15.0-20-generic/bionic 4.15.0-20.23~lp1770003+build.7 
ppc64el
  Linux kernel image for version 4.15.0 on PowerPC 64el SMP

ubuntu@dradis:~$ apt search linux-modules
Sorting... Done
Full Text Search... Done
linux-modules-4.15.0-20-generic/bionic 4.15.0-20.23~lp1770003+build.7 ppc64el 
[upgradable from: 4.15.0-20.21]
  Linux kernel extra modules for version 4.15.0 on PowerPC 64el SMP

linux-modules-extra-4.15.0-20-generic/bionic 4.15.0-20.23~lp1770003+build.7 
ppc64el [upgradable from: 4.15.0-20.21]
  Linux kernel extra modules for version 4.15.0 on PowerPC 64el SMP

ubuntu@dradis:~$ sudo apt install -y --assume-yes 
linux-image-unsigned-4.15.0-20-generic linux-modules-4.15.0-20-generic 
linux-modules-extra-4.15.0-20-generic
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-headers-generic
Use 'sudo apt autoremove' to remove it.
Suggested packages:
  fdutils linux-doc-4.15.0 | linux-source-4.15.0 linux-tools
The following packages will be REMOVED:
  linux-generic linux-image-4.15.0-20-generic linux-image-generic
The following NEW packages will be installed:
  linux-image-unsigned-4.15.0-20-generic
The following packages will be upgraded:
  linux-modules-4.15.0-20-generic linux-modules-extra-4.15.0-20-generic
2 upgraded, 1 newly installed, 3 to remove and 2 not upgraded.
Need to get 50.1 MB of archives.
After this operation, 72.7 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/ubuntu-power-triage/lp1770003/ubuntu bionic/main 
ppc64el linux-image-unsigned-4.15.0-20-generic ppc64el 
4.15.0-20.23~lp1770003+build.7 [6143 kB]
Get:2 http://ppa.launchpad.net/ubuntu-power-triage/lp1770003/ubuntu bionic/main 
ppc64el linux-modules-4.15.0-20-generic ppc64el 4.15.0-20.23~lp1770003+build.7 
[12.5 MB]
Get:3 http://ppa.launchpad.net/ubuntu-power-triage/lp1770003/ubuntu bionic/main 
ppc64el linux-modules-extra-4.15.0-20-generic ppc64el 
4.15.0-20.23~lp1770003+build.7 [31.5 MB]
Fetched 50.1 MB in 1min 10s (714 kB/s) 
(Reading database ... 64762 files and directories currently installed.)
Removing linux-generic (4.15.0.20.23) ...
Removing linux-image-generic (4.15.0.20.23) ...
dpkg: linux-image-4.15.0-20-generic: dependency problems, but removing anyway 
as you requested:
 linux-modules-extra-4.15.0-20-generic depends on linux-image-4.15.0-20-generic 
| linux-image-unsigned-4.15.0-20-generic; however:
  Package linux-image-4.15.0-20-generic is to be removed.
  Package linux-image-unsigned-4.15.0-20-generic is not installed.

Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ...
W: Removing the running kernel
W: Last kernel image has been removed, so removing the default symlinks
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-4.15.0-20-generic
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
done
Selecting previously unselected package linux-image-unsigned-4.15.0-20-generic.
(Reading database ... 64752 files and directories currently installed.)
Preparing to unpack 
.../linux-image-unsigned-4.15.0-20-generic_4.15.0-20.23~lp1770003+build.7_ppc64el.deb
 ...
Unpacking linux-image-unsigned-4.15.0-20-generic 
(4.15.0-20.23~lp1770003+build.7) ...
Preparing to unpack 
.../linux-modules-4.15.0-20-generic_4.15.0-20.23~lp1770003+build.7_ppc64el.deb 
...
Unpacking linux-modules-4.15.0-20-generic (4.15.0-20.23~lp1770003+build.7) over 
(4.15.0-20.21) ...
Preparing to unpack 
.../linux-modules-extra-4.15.0-20-generic_4.15.0-20.23~lp1770003+build.7_ppc64el.deb
 ...
Unpacking linux-modules-extra-4.15.0-20-generic 
(4.15.0-20.23~lp1770003+build.7) over (4.15.0-20.21) ...
Setting up linux-modules-4.15.0-20-generic (4.15.0-20.23~lp1770003+build.7) ...
Setting up linux-image-unsigned-4.15.0-20-generic 
(4.15.0-20.23~lp1770003+build.7) ...
I: /boot/vmlinux.old is now a symlink to vmlinux-4.15.0-20-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-4.15.0-20-generic
I: /boot/vmlinux is now a symlink to vmlinux-4.15.0-20-generic
I: /boot/initrd.img is now a symlink to initrd.img-4.15.0-20-generic
Setting up linux-modules-extra-4.15.0-20-generic 
(4.15.0-20.23~lp1770003+build.7) ...
Processing triggers for linux-image-unsigned-4.15.0-20-generic 
(4.15.0-20.23~lp1770003+build.7) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating 

[Bug 1770254] Re: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic.

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770254

Title:
  [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI
  devices results in a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767194] Re: [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

[Manoj Iyer]

you could preseed your installer to install the kernel in the PPA. I
have not tested the instructions below.. but should give you an idea how
to preseed. From your comment above looks like you might not have a
booting system to be able to install the new kernel etc.

Assuming you are using a netboot install.

-- tell installer grub to use preseed --
Edit ubuntu-installer/ppc64el/grub/grub.cfg and add your preseed file. Like for 
example:

menuentry 'Install' {
set background_color=black
linux/ubuntu-installer/ppc64el/linux auto=true priority=critical 
url=http:///preseed/preseed.ppc64el --- quiet
initrd   /ubuntu-installer/ppc64el/initrd.gz
}

-- preseed example --
You can use late-commands in your preseed file to install the PPA kernel like:

# Install kernel from PPA
d-i preseed/late_command string in-target add-apt-repository -y 
ppa:ubuntu-power-triage/lp1770003
d-i preseed/late_command string in-target apt update
d-i preseed/late_command string in-target apt install -y 
linux-image-unsigned-4.15.0-20-generic linux-modules-extra-4.15.0-20-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767194

Title:
  [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

you could preseed your installer to install the kernel in the PPA. I
have not tested the instructions below.. but should give you an idea how
to preseed. From your comment above looks like you might not have a
booting system to be able to install the new kernel etc.

Assuming you are using a netboot install.

-- tell installer grub to use preseed --
Edit ubuntu-installer/ppc64el/grub/grub.cfg and add your preseed file. Like for 
example:

menuentry 'Install' {
set background_color=black
linux /ubuntu-installer/ppc64el/linux auto=true priority=critical 
url=http:///preseed/preseed.ppc64el --- quiet
initrd /ubuntu-installer/ppc64el/initrd.gz
}

-- preseed example --
You can use late-commands in your preseed file to install the PPA kernel like:

# Install kernel from PPA
d-i preseed/late_command string in-target add-apt-repository -y 
ppa:ubuntu-power-triage/lp1770003
d-i preseed/late_command string in-target apt update
d-i preseed/late_command string in-target apt install -y 
linux-image-unsigned-4.15.0-20-generic linux-modules-extra-4.15.0-20-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

Its building in the PPA as we speak, it should be ready for your use in
about 45mts or so. You can monitor progress here: https://launchpad.net
/~ubuntu-power-triage/+archive/ubuntu/lp1770003/+packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769927] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config show' shows Not ready to kdump even after doing kdump setup.

[Manoj Iyer]

Could you please try your testing with linux-hwe kernel (4.13) ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769927

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config
  show' shows Not ready to kdump even after doing kdump setup.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770254] Re: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic.

[Manoj Iyer]

I was able to pass through a PCIE virtual function NIC from the host to
the guest. No kernel panics seen in the host.

-- Host with kernel patches --
ubuntu@seuss:~$ ethtool -i enP2p1s0f1
driver: thunder-nicvf
version: 1.0
firmware-version:
expansion-rom-version:
bus-info: 0002:01:00.1
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

ubuntu@seuss:~$ readlink /sys/bus/pci/devices/0002\:01\:00.1/driver
../../../../../../../bus/pci/drivers/thunder-nicvf
ubuntu@seuss:~$

ubuntu@seuss:~$ virsh nodedev-detach pci_0002_01_00_1
Device pci_0002_01_00_1 detached

ubuntu@seuss:~$ readlink /sys/bus/pci/devices/0002\:01\:00.1/driver
../../../../../../../bus/pci/drivers/vfio-pci
ubuntu@seuss:~$

-- Bionic Guest --

ubuntu@vm1:~$ lspci -k
00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge
Subsystem: Red Hat, Inc QEMU PCIe Host bridge
00:01.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
Kernel driver in use: pcieport
Kernel modules: shpchp
01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01)
Subsystem: Red Hat, Inc Virtio network device
Kernel driver in use: virtio-pci
02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01)
Subsystem: Red Hat, Inc Virtio console
Kernel driver in use: virtio-pci
03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
Subsystem: Red Hat, Inc Virtio block device
Kernel driver in use: virtio-pci
04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
Subsystem: Red Hat, Inc Virtio block device
Kernel driver in use: virtio-pci
05:00.0 Ethernet controller: Cavium, Inc. THUNDERX Network Interface Controller 
virtual function (rev 09)
Subsystem: Cavium, Inc. THUNDERX Network Interface Controller virtual 
function
Kernel driver in use: thunder-nicvf
Kernel modules: nicvf
ubuntu@vm1:~$

ubuntu@vm1:~$ ethtool -i enp5s0
driver: thunder-nicvf
version: 1.0
firmware-version:
expansion-rom-version:
bus-info: :05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
ubuntu@vm1:~$


** Description changed:

  [Impact]
  Using vfio-pci on a combination of cn8xxx and some PCI devices results in a 
kernel panic. This is triggered by issuing a bus or a slot reset on the PCI 
device.
  
  [Fix]
  The following patches checks indicate that the reset is not possible
  preventing the kernel panic.
  357027786f35 PCI: Avoid bus reset if bridge itself is broken
  822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset
  33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken
  
  These patches are already in Bionic, we need these patches in Artful so
  that xenial linux-hwe also has the fix. The platforms of interest were
  certified with Xenial and linux-hwe, so we are interested in fixing this
  only in Artful.
  
  [Test]
  - Artful Host with Artful/bionic guests
  - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its 
usable.
  - The device should pass through and not cause a kernel panic.
  
+ A test kernel is available in ppa:manjo/lp1770254
+ 
  [Regression Potential]
  None.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770254

Title:
  [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI
  devices results in a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769927] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config show' shows Not ready to kdump even after doing kdump setup.

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => Critical

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769927

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config
  show' shows Not ready to kdump even after doing kdump setup.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

** Changed in: linux (Ubuntu)
   Importance: High => Critical

** Changed in: linux (Ubuntu Bionic)
   Importance: High => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

That is because the package I provided has the same version number as
the -proposed package, my bad, I should have accounted for -proposed
version. I will bump the version an update the package in the PPA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770254] [NEW] [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic.

[Manoj Iyer]

Public bug reported:

[Impact]
Using vfio-pci on a combination of cn8xxx and some PCI devices results in a 
kernel panic. This is triggered by issuing a bus or a slot reset on the PCI 
device.

[Fix]
The following patches checks indicate that the reset is not possible
preventing the kernel panic.
357027786f35 PCI: Avoid bus reset if bridge itself is broken
822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset
33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken

These patches are already in Bionic, we need these patches in Artful so
that xenial linux-hwe also has the fix. The platforms of interest were
certified with Xenial and linux-hwe, so we are interested in fixing this
only in Artful.

[Test]
- Artful Host with Artful/bionic guests
- Pass though PCI device (vfio-pci) from Artful to bionic and make sure its 
usable.
- The device should pass through and not cause a kernel panic.

[Regression Potential]
None.

** Affects: linux (Ubuntu)
 Importance: Critical
 Status: New


** Tags: cn88xx

** Description changed:

  [Impact]
  Using vfio-pci on a combination of cn8xxx and some PCI devices results in a 
kernel panic. This is triggered by issuing a bus or a slot reset on the PCI 
device.
  
  [Fix]
  The following patches checks indicate that the reset is not possible
  preventing the kernel panic.
  357027786f35 PCI: Avoid bus reset if bridge itself is broken
  822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset
  33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken
  
  These patches are already in Bionic, we need these patches in Artful so
- that xenial linux-hwe also has the fix.
+ that xenial linux-hwe also has the fix. The platforms of interest were
+ certified with Xenial and linux-hwe, so we are interested in fixing this
+ only in Artful.
  
  [Test]
  - Artful Host with Artful/bionic guests
  - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its 
usable.
  - The device should pass through and not cause a kernel panic.
  
  [Regression Potential]
  None.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770254

Title:
  [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI
  devices results in a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: ./configure --enable-arm needed for ARM events

[Manoj Iyer]

Patch to enable arm events for aarch64 in xenial

** Patch added: "Patch to enable arm events for aarch64 in xenial"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5136906/+files/xenial-enable-arm-v1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: ./configure --enable-arm needed for ARM events

[Manoj Iyer]

Patch to enable arm events for aarch64 in artful

** Patch added: "Patch to enable arm events for aarch64 in artful"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5136905/+files/artful-enable-arm-v1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

Here is the set of patches I needed to backport/cherry-pick to get a
kernel that would build.

2853192e154b scsi: qla2xxx: Use IOCB path to submit Control VP MBX command
11aea16ab3f5 scsi: qla2xxx: Add ability to send PRLO
1c6cacf4ea6c scsi: qla2xxx: Fixup locking for session deletion
eaf75d1815da scsi: qla2xxx: Fix double free bug after firmware timeout
6d67492764b3 scsi: qla2xxx: Prevent relogin trigger from sending too many 
commands
7ac0c332f96b scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
045d6ea200af scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
1ae634eb2853 scsi: qla2xxx: Serialize session free in qlt_free_session_done
d8630bb95f46 scsi: qla2xxx: Serialize session deletion by using work_lock
94cff6e114df scsi: qla2xxx: Remove unused argument from 
qlt_schedule_sess_for_deletion()
a4239945b8ad scsi: qla2xxx: Add switch command to simplify fabric discovery
040036bb0bc1 scsi: qla2xxx: Delay loop id allocation at login
9cd883f07a54 scsi: qla2xxx: Fix session cleanup for N2N
f13515acdcb5 scsi: qla2xxx: Replace GPDB with async ADISC command


I have this kernel built in a PPA: ppa:ubuntu-power-triage/lp1770003. This 
kernel needs to be tested on the platform (bug does not say if this was found 
in P8 or P9) where the issue was reported, and will also need to be tested on 
Cavium (ARM64) to make sure there are no regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

The patches identified here does no seem to cleanly cherry-pick. How
ever I cherry-picked several of the dependencies and came up with this
list.

scsi: qla2xxx: Fix double free bug after firmware timeout
scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
scsi: qla2xxx: Serialize session free in qlt_free_session_done
scsi: qla2xxx: Serialize session deletion by using work_lock
scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion()
scsi: qla2xxx: Prevent relogin trigger from sending too many commands
scsi: qla2xxx: Prevent multiple active discovery commands per session
scsi: qla2xxx: Delay loop id allocation at login
scsi: qla2xxx: Allow relogin and session creation after reset
scsi: qla2xxx: Add ability to use GPNFT/GNNFT for RSCN handling
scsi: qla2xxx: Properly extract ADISC error codes
scsi: qla2xxx: Fix GPNFT/GNNFT error handling
scsi: qla2xxx: Fix login state machine freeze
scsi: qla2xxx: Add lock protection around host lookup
scsi: qla2xxx: Add switch command to simplify fabric discovery
scsi: qla2xxx: Fix session cleanup for N2N
scsi: qla2xxx: Allow target mode to accept PRLI in dual mode 
scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
scsi: qla2xxx: Add ability to send PRLO 
scsi: qla2xxx: Add option for use reserve exch for ELS 
scsi: qla2xxx: Move work element processing out of DPC thread
scsi: qla2xxx: Replace GPDB with async ADISC command
scsi: qla2xxx: Fix Firmware dump size for Extended login and Exchange Offload
scsi: qla2xxx: Use IOCB path to submit Control VP MBX command

It is a longer list of patches to the drive, please let me know if this
is acceptable ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770003

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking

[Manoj Iyer]

** Description changed:

  [Impact]
  on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping 
at address 00a99000/0xa99000" while booting. These messages are a false 
positive and triggered at random.
  
  [Test]
- There is no reliable way to reproduce these warnings, they are triggered at 
random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. 
A test kernel is available in 
- ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system. 
+ There is no reliable way to reproduce these warnings, they are triggered at 
random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. 
A test kernel is available in
+ ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and 
Cavium Thunderx.
  
- ubuntu@awrep2:~$ uname -a 
+ ubuntu@awrep2:~$ uname -a
  Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 
16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
+ 
+ ubuntu@boomer:~$ uname -a 
+ Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 
16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
+ ubuntu@boomer:~$ 
+ 
  
  [Fix]
  Upstream fix is available in linux-next
  
  65d313ee1a7d init: fix false positives in W+X checking
  
  [Regression Potential]
  potential for any regression is low.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769696

Title:
  [SRU][Bionic/Artful] fix false positives in W+X checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769696] Re: [SRU][Bionic] fix false positives in W+X checking

[Manoj Iyer]

** Description changed:

  [Impact]
  on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping 
at address 00a99000/0xa99000" while booting. These messages are a false 
positive and triggered at random.
  
  [Test]
- There is no reliable way to reproduce these warnings, they are triggered at 
random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. 
+ There is no reliable way to reproduce these warnings, they are triggered at 
random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. 
A test kernel is available in 
+ ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system. 
+ 
+ ubuntu@awrep2:~$ uname -a 
+ Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 
16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
  
  [Fix]
  Upstream fix is available in linux-next
  
  65d313ee1a7d init: fix false positives in W+X checking
  
  [Regression Potential]
  potential for any regression is low.

** Summary changed:

- [SRU][Bionic] fix false positives in W+X checking
+ [SRU][Bionic/Artful] fix false positives in W+X checking

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769696

Title:
  [SRU][Bionic/Artful] fix false positives in W+X checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769696] [NEW] [SRU][Bionic] fix false positives in W+X checking

[Manoj Iyer]

Public bug reported:

[Impact]
on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at 
address 00a99000/0xa99000" while booting. These messages are a false 
positive and triggered at random.

[Test]
There is no reliable way to reproduce these warnings, they are triggered at 
random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. 

[Fix]
Upstream fix is available in linux-next

65d313ee1a7d init: fix false positives in W+X checking

[Regression Potential]
potential for any regression is low.

** Affects: linux (Ubuntu)
 Importance: High
 Status: Incomplete


** Tags: bionic qdf2400

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769696

Title:
  [SRU][Bionic] fix false positives in W+X checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: ./configure --enable-arm needed for ARM events

[Manoj Iyer]

[v3] Patch to enable arm events for aarch64 in bionc

** Patch added: "[v3] Patch to enable arm events for aarch64 in bionc"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5134117/+files/bionic-enable-arm-v3.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: ./configure --enable-arm needed for ARM events

[Manoj Iyer]

Patch to enable arm events for aarch64 in bionic

** Patch added: "[V2] Patch to enable arm events for aarch64 in bionic"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5134083/+files/bionic-enable-arm-v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: [SRU][BIONIC] enable ARM event

[Manoj Iyer]

Patch to enable arm events for aarch64 in artful

** Patch added: "Patch to enable arm events for aarch64 in artful"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5133833/+files/artful-enable-arm.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: [SRU][BIONIC] enable ARM event

[Manoj Iyer]

Patch to enable arm events for aarch64 in xenial

** Patch added: "Patch to enable arm events for aarch64 in xenial"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5133834/+files/xenial-enable-arm.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] Re: [SRU][BIONIC] enable ARM event

[Manoj Iyer]

Patch to enable arm events for aarch64 in bionic

** Patch added: "Patch to enable arm events for aarch64 in bionic"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+attachment/5133832/+files/bionic-enable-arm.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769182] [NEW] [SRU][BIONIC] enable ARM event

[Manoj Iyer]

Public bug reported:

[Impact]
The UEFI 2.6 spec added support for ARM processor errors and errors
that have unrecognized CPER section types. rasdaemon needs to support ARM 
kernel trace events. To enable arm events we need to configure rasdaemon 
package with --enable-arm 

[Test]
debian/rules needs --enable-arm to enable arm events. I have a test build of 
the rasdaemon package in ppa:centriq-team/lp1741978-rasdaemon. I tested this on 
an a QDF2400 system. Here are the results for bionic, artful and xenial.

--- bionic ---
ubuntu@awrep3:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Mon 2018-04-23 15:25:18 UTC; 17s ago
 Main PID: 3369 (rasdaemon)
Tasks: 1 (limit: 7065)
   CGroup: /system.slice/rasdaemon.service
   └─3369 /usr/sbin/rasdaemon -f -r

Apr 23 15:25:18 awrep3 rasdaemon[3369]: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Enabled event ras:arm_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't parse /proc/cpuinfo: missing [vend
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't register mce handler
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't get traces from ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog 
Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:mc_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:mc_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:arm_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't parse /proc/cpuinfo: 
missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't register mce handler
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get 
ras:extlog_mem_event traces. Perhaps this feature is not supported on your 
system.
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get traces from 
ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Listening to events for cpus 
0 to 45
Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:arm_event
Apr 23 15:25:18 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing 
[vendor_id] [cpu family] [model] [cpu MHz] [flags]
Apr 23 15:25:18 awrep3 rasdaemon: Can't register mce handler
Apr 23 15:25:18 awrep3 rasdaemon: Can't get traces from ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

-- artful --
ubuntu@awrep3:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Mon 2018-04-23 15:51:55 UTC; 13s ago
 Main PID: 3683 (rasdaemon)
Tasks: 1 (limit: 7065)
   Memory: 7.9M
  CPU: 48ms
   CGroup: /system.slice/rasdaemon.service
   └─3683 /usr/sbin/rasdaemon -f -r

Apr 23 15:51:55 awrep3 rasdaemon[3683]: ras:arm_event event enabled
Apr 23 15:51:55 awrep3 rasdaemon[3683]: 

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

Patch to enable arm events for aarch64 in xenial

** Patch added: "Patch to enable arm events for aarch64 in xenial"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+attachment/5132439/+files/xenial-enable-arm.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741978

Title:
  Add support for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

Patch to enable arm events for aarch64 in artful

** Patch added: "Patch to enable arm events for aarch64 in artful"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+attachment/5132441/+files/artful-enable-arm.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741978

Title:
  Add support for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

Patch to enable arm events for aarch64 in bionic

** Patch added: "Patch to enable arm events for aarch64 in bionic"
   
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+attachment/5132452/+files/bionic-enable-arm.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741978

Title:
  Add support for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767194] [NEW] [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

[Manoj Iyer]

Public bug reported:

[Impact]
If a PLX bridge is connected on a ThunderX2 the Linux kernel panics on boot.

[Fix]
The following patches upstream fixes this issue.
204f4afa7ae5 PCI: Remove redundant probes for device reset support
5b0764cac9f1 PCI: Probe for device reset support during enumeration

[Test]
1) Connect a PLX bridge to the root complex
2) Boot Ubuntu kernel

[Regression Potential]
This only impacts ThunderX2.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Manoj Iyer (manjo)
 Status: New


** Tags: thunder

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767194

Title:
  [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

Based on the results, rasdaemon needs to reuploaded to -proposed with
--enable-arm in debian/rules.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741978

Title:
  Add support for ARM events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707875] Re: [18.04] include support for Python bindings in "perf"

[Manoj Iyer]

The patches identified here are already in bionic. However we have not
enabled py bindings for perf in bionic. This has been the case since
13.04 days, and the reason for this is py (like 2.x vs 3.x) build
dependencies, and it is unlikely that this support will be added going
forward. jsalisbury (kernel team) is looking into this again to make
sure that is still the case.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707875

Title:
  [18.04] include support for Python bindings in "perf"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741978] Re: Add support for ARM events

[Manoj Iyer]

debian/rules needs --enable-arm to enable arm events. I have a test
build of the rasdaemon package in ppa:centriq-team/lp1741978-rasdaemon.
I tested this on an a QDF2400 system. Here are the results for bionic,
artful and xenial.

--- bionic ---
ubuntu@awrep3:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Mon 2018-04-23 15:25:18 UTC; 17s ago
 Main PID: 3369 (rasdaemon)
Tasks: 1 (limit: 7065)
   CGroup: /system.slice/rasdaemon.service
   └─3369 /usr/sbin/rasdaemon -f -r

Apr 23 15:25:18 awrep3 rasdaemon[3369]: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Enabled event ras:arm_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't parse /proc/cpuinfo: missing [vend
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't register mce handler
Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't get traces from ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog 
Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:mc_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:mc_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:mc_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:arm_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't parse /proc/cpuinfo: 
missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't register mce handler
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get 
ras:extlog_mem_event traces. Perhaps this feature is not supported on your 
system.
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get traces from 
ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Listening to events for cpus 
0 to 45
Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:arm_event
Apr 23 15:25:18 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing 
[vendor_id] [cpu family] [model] [cpu MHz] [flags]
Apr 23 15:25:18 awrep3 rasdaemon: Can't register mce handler
Apr 23 15:25:18 awrep3 rasdaemon: Can't get traces from ras:aer_event
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events
Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

-- artful --
ubuntu@awrep3:~$ sudo service rasdaemon status
● rasdaemon.service - RAS daemon to log the RAS events
   Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
   Active: active (running) since Mon 2018-04-23 15:51:55 UTC; 13s ago
 Main PID: 3683 (rasdaemon)
Tasks: 1 (limit: 7065)
   Memory: 7.9M
  CPU: 48ms
   CGroup: /system.slice/rasdaemon.service
   └─3683 /usr/sbin/rasdaemon -f -r

Apr 23 15:51:55 awrep3 rasdaemon[3683]: ras:arm_event event enabled
Apr 23 15:51:55 awrep3 rasdaemon[3683]: Enabled event ras:arm_event
Apr 23 15:51:55 awrep3 rasdaemon[3683]: Can't parse /proc/cpuinfo: missing [vend
Apr 23 15:51:55 awrep3 rasdaemon[3683]: Can't register mce handler
Apr 23 15:51:55 awrep3 rasdaemon[3683]: Can't get traces from ras:aer_event
Apr 23 15:51:55 awrep3 

[Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10

[Manoj Iyer]

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201

Title:
  CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
  error Checking for all LINUX clients for devops4p10

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Manoj Iyer]

** Changed in: crash (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: crash (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765660

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1755979] Re: Cpu utilization showing system time for kvm guests (performance) (sysstat)

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755979

Title:
  Cpu utilization showing system time for kvm guests (performance)
  (sysstat)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758206] Re: Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails to capture dump when smt=2 or off.

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758206

Title:
  Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails
  to capture dump when smt=2 or off.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1757497] Re: Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe)

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757497

Title:
  Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
  namespaces  (Bolt / NVMe)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1755161] Re: Update to ocxl driver

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755161

Title:
  Update to ocxl driver

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754206] Re: Allow hugepage backing for "p8compat" mode kvm guests

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754206

Title:
  Allow hugepage backing for "p8compat" mode kvm guests

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758884] Re: Ubuntu18.04[P9, WSP]: Not able to configure 2MB hugepage while installation as i provided default_hugepagesz=2MB hugepagesz=2MB huegpage=20000 while installation cmdline

[Manoj Iyer]

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758884

Title:
  Ubuntu18.04[P9, WSP]: Not able to configure 2MB hugepage while
  installation as i provided default_hugepagesz=2MB hugepagesz=2MB
  huegpage=2  while installation cmdline

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

[Manoj Iyer]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751813

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765364] Re: Backport spectre/meltdown fixes on qemu for ppc64 into all LTS releases

[Manoj Iyer]

** Changed in: qemu (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765364

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765364] Re: Backport spectre/meltdown fixes on qemu for ppc64 into all LTS releases

[Manoj Iyer]

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

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

** Changed in: ubuntu-power-systems/ubuntu-16.04
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765364

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs