[Kernel-packages] [Bug 1736794] [NEW] iwlwifi driver for Intel 7260 crashing

[Mike Rushton]

Public bug reported:

Intel NUC's from Axiomtek with Intel Corporation Wireless 7260 (rev bb)
chipsets. We have this running on almost 200 of these devices.

Ubuntu 16.04.3 as well as Ubuntu 14.04.5

"loaded firmware version 17.608620.0 op_mode iwlmvm"

linux-firmware trusty: 1.127.24
linux-firmware xenial: 1.157.14

The wireless driver will crash at least daily, if not multiple times in
a day depending on the machine. Swapping the chipset out for an Atheros
works just fine.

I have followed the many other bug reports related to this same chipset
and they are either marked incomplete, refer to hardware we aren't
running or have been marked as fix released.

The latest linux-firmware did not resolve or change the behavior of the
issue.

Output from dmesg when the crash occurs:

[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: Queue 16 stuck for 1 ms.
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: Current SW read_ptr 236 
write_ptr 88
[Wed Dec  6 18:56:38 2017] [ cut here ]
[Wed Dec  6 18:56:38 2017] WARNING: CPU: 3 PID: 0 at 
/build/linux-lts-xenial-CtFtiH/linux-lts-xenial-4.4.0/drivers/net/wireless/iwlwifi/pcie/trans.c:1552
 iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]()
[Wed Dec  6 18:56:38 2017] Timeout waiting for hardware access (CSR_GP_CNTRL 
0x)
[Wed Dec  6 18:56:38 2017] Modules linked in: drbg ansi_cprng ctr ccm uvcvideo 
videobuf2_vmalloc btusb videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel 
videobuf2_core hid_generic bluetooth v4l2_common videodev usbhid media arc4 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlmvm mac80211 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass iwlwifi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cfg80211 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
snd_soc_rt5640 snd_soc_rl6231 snd_soc_ssm4567 serio_raw lpc_ich i915 shpchp 
binfmt_misc snd_hda_intel snd_soc_core snd_compress snd_hda_codec ac97_bus 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_dmaengine snd_hda_core 
snd_hwdep snd_pcm 8250_fintek snd_seq video snd_seq_device snd_timer 
drm_kms_helper snd elan_i2c 8250_dw drm dw_dmac i2c_hid hid dw_dmac_core mei_me 
fb_sys_fops syscopyarea snd_soc_sst_acpi i2c_designware_platform mac_hid 
sysfillrect spi_pxa2xx_platform mei i2c_designware_core soundcore acpi_pad 
sysimgblt acpi_als kfifo_buf industrialio lp parport igb psmouse ahci e1000e 
i2c_algo_bit libahci dca ptp pps_core fjes sdhci_acpi sdhci
[Wed Dec  6 18:56:38 2017] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 
4.4.0-101-generic #124~14.04.1-Ubuntu
[Wed Dec  6 18:56:38 2017] Hardware name: To be filled by O.E.M. To be filled 
by O.E.M./CRESCENTBAY, BIOS 5.6.5 12/14/2016
[Wed Dec  6 18:56:38 2017]   88012dd83d00 813dfc6c 
88012dd83d48
[Wed Dec  6 18:56:38 2017]  c07ca6e0 88012dd83d38 8107ea26 
8800ca47
[Wed Dec  6 18:56:38 2017]  8800ca4735f0 88012dd83dd8  
880128108bc0
[Wed Dec  6 18:56:38 2017] Call Trace:
[Wed Dec  6 18:56:38 2017][] dump_stack+0x63/0x87
[Wed Dec  6 18:56:38 2017]  [] warn_slowpath_common+0x86/0xc0
[Wed Dec  6 18:56:38 2017]  [] warn_slowpath_fmt+0x4c/0x50
[Wed Dec  6 18:56:38 2017]  [] ? iwl_read32+0x1f/0x90 
[iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] 
iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] 
iwl_trans_pcie_read_mem+0x2f/0xa0 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] 
iwl_pcie_txq_stuck_timer+0xd8/0x390 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] ? 
intel_pstate_timer_func+0x2db/0x3a0
[Wed Dec  6 18:56:38 2017]  [] ? 
iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] call_timer_fn+0x35/0x130
[Wed Dec  6 18:56:38 2017]  [] ? 
iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] run_timer_softirq+0x20e/0x2c0
[Wed Dec  6 18:56:38 2017]  [] __do_softirq+0xdd/0x290
[Wed Dec  6 18:56:38 2017]  [] irq_exit+0x95/0xa0
[Wed Dec  6 18:56:38 2017]  [] 
smp_apic_timer_interrupt+0x42/0x50
[Wed Dec  6 18:56:38 2017]  [] apic_timer_interrupt+0x82/0x90
[Wed Dec  6 18:56:38 2017][] ? 
cpuidle_enter_state+0xd8/0x250
[Wed Dec  6 18:56:38 2017]  [] ? 
cpuidle_enter_state+0xb4/0x250
[Wed Dec  6 18:56:38 2017]  [] cpuidle_enter+0x17/0x20
[Wed Dec  6 18:56:38 2017]  [] call_cpuidle+0x32/0x60
[Wed Dec  6 18:56:38 2017]  [] ? cpuidle_select+0x13/0x20
[Wed Dec  6 18:56:38 2017]  [] cpu_startup_entry+0x289/0x350
[Wed Dec  6 18:56:38 2017]  [] start_secondary+0x149/0x170
[Wed Dec  6 18:56:38 2017] ---[ end trace ad9659e8d87e5230 ]---
[Wed Dec  6 18:56:38 2017] iwl data: : b0 68 00 00 14 00 00 00 b8 8a 5c 
00 00 00 00 00  .h\.
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(0) = 0x5a5a5a5a
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(1) = 0x5a5a5a5a
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(2) = 0x5a5a5a5a
[Wed Dec  6 18:56:38 2017] iwlwifi 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

I have tested the qemu-system-ppc package from both PPA's and both work
without issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  

[Kernel-packages] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

I tested 4.4.0-72 from above and got the same results as 4.4.0-71.

In the process of testing 4.4.0-71 more, I found all is not as well as
we assumed. At first deployment everything seems to be fine. And after
most reboots, we are still able to ping across both interfaces. But
bringing interfaces up and down seems to intermittently bring about the
issue of not being able to ping the interfaces. I cannot seem to find a
pattern of replicated it breaking or even resolving. Sometimes rebooting
is required and even then, sometimes rebooting twice. Other times
bringing up and down the 2 interfaces in some random pattern will allow
both interfaces to be pinged.

One scenario I can replicate is if both enP8p1s0 and enP8p1s0d1 are up
and pingable, if I bring down enP8p1s0, both will become unpingable.
Bringing enP8p1s0 back up does not resolve anything. Bringing enP8p1s0
up and then enP8p1s0d1 down will allow enP8p1s0 to be pingable. Bringing
enP8p1s0d1 up does not make it become bootable. Only after bringing
enP8p1s0 down, then back up, then bringing enP8p1s0d1 up will both
become pingable.

I do not think it is possible to have enP8p1s0d1 up and pingable by
itself. It almost acts like a slave to enP8p1s0.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] 

[Kernel-packages] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

4.4.0-71-generic is tested as working now.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
  Kernel driver in use: mlx4_core
  Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
     

[Kernel-packages] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

4.8.0-45.48~16.04.1 from xenial updates works

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
  Kernel driver in use: mlx4_core
  Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
  

[Kernel-packages] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

linux-image-4.10.6-041006 has also failed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
  Kernel driver in use: mlx4_core
  Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
     

[Kernel-packages] [Bug 1677337] [NEW] Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

Public bug reported:

After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
brought up and assigned an ip via MAAS. This is where functionality
stops on this kernel. Pinging the MAAS server  which is connected
directly(no switch) fails. There's no traffic  from tcpdump.

linux-image-generic-hwe-16.04 4.8.0.44.16 fails
mainline kernel 4.10.0-041000-generic fails
mainline kernel 4.11.0-041100rc1-generic resolves the issue.

Both the test server (ppc64le) and MAAS server(amd64) need the upgraded
kernel to work.

=== 4.4.0-70-generic ===

lspci -v
0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
 Subsystem: IBM MT27500 Family [ConnectX-3]
 Flags: bus master, fast devsel, latency 0, IRQ 473
 Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
 Memory at 2400 (64-bit, prefetchable) [size=128M]
 [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
Capabilities: 
 Kernel driver in use: mlx4_core
 Kernel modules: mlx4_core

ethtool enP8p1s0
Settings for enP8p1s0:
 Supported ports: [ FIBRE ]
 Supported link modes:   1000baseKX/Full
 1baseKX4/Full
 1baseKR/Full
 4baseCR4/Full
 4baseSR4/Full
 56000baseCR4/Full
 56000baseSR4/Full
 Supported pause frame use: Symmetric Receive-only
 Supports auto-negotiation: Yes
 Advertised link modes:  1000baseKX/Full
 1baseKX4/Full
 1baseKR/Full
 4baseCR4/Full
 4baseSR4/Full
 Advertised pause frame use: Symmetric
 Advertised auto-negotiation: Yes
 Link partner advertised link modes:  4baseCR4/Full
 Link partner advertised pause frame use: No
 Link partner advertised auto-negotiation: Yes
 Speed: 4Mb/s
 Duplex: Full
 Port: Direct Attach Copper
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: d
 Wake-on: d
 Current message level: 0x0014 (20)
  link ifdown
 Link detected: yes

dmesg
[3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
[3.494624] mlx4_core: Initializing 0008:01:00.0
[3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

[8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
[8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports x8
[8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 2014)
[8.472907] mlx4_en 0008:01:00.0: Activating port:1
[8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
[8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
[8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
[8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
[8.482320] mlx4_en 0008:01:00.0: registered PHC clock
[8.485058] mlx4_en 0008:01:00.0: Activating port:2
[8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
[8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
[8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
[8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
[8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
[8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

=== 4.11.0-041100rc1-generic ===

lspci -v
0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
Subsystem: IBM MT27500 Family [ConnectX-3]
Flags: bus master, fast devsel, latency 0, IRQ 473
Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
Memory at 2400 (64-bit, prefetchable) [size=128M]
[virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
Capabilities: 
Kernel driver in use: mlx4_core
Kernel modules: mlx4_core

ethtool enP8p1s0
Settings for enP8p1s0:
 Supported ports: [ FIBRE ]
 Supported link modes:   1000baseKX/Full
 1baseKX4/Full
 1baseKR/Full
 4baseCR4/Full
 4baseSR4/Full
 56000baseCR4/Full
 56000baseSR4/Full
 Supported pause frame use: Symmetric Receive-only
 Supports auto-negotiation: Yes
 Advertised link modes:  1000baseKX/Full
 1baseKX4/Full
 1baseKR/Full
 4baseCR4/Full
 4baseSR4/Full
 Advertised pause frame use: Symmetric
 Advertised auto-negotiation: Yes
 Link partner advertised link modes:  4baseCR4/Full
 Link partner advertised pause frame use: No
 Link partner advertised auto-negotiation: Yes
 Speed: 4Mb/s
 Duplex: Full
 Port: Direct Attach Copper
 PHYAD: 0

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Changed in: plainbox-provider-checkbox
   Status: Fix Released => Confirmed

** Changed in: plainbox-provider-checkbox
 Assignee: Mike Rushton (leftyfb) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in Provider for Plainbox - Checkbox:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

** Changed in: qemu (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Incomplete

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

** Summary changed:

- Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: 
Invalid argument
+ Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: 
Invalid argument

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Incomplete

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

[Mike Rushton]

kernel 4.11.0-041100rc3-generic failed with the same symptoms.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
  ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 4149 00:14:817 0 EOF
   2: POSIX  ADVISORY  WRITE 1701 00:14:477 0 EOF
   3: POSIX  ADVISORY  

[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

[Mike Rushton]

** Also affects: checkbox (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
  ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 4149 00:14:817 0 EOF
   2: POSIX  ADVISORY  WRITE 1701 00:14:477 0 EOF
   3: POSIX  

[Kernel-packages] [Bug 1675091] [NEW] Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

[Mike Rushton]

Public bug reported:

During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.


ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager saw 
8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev ]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID:   [14e4:1657]
Subsystem ID: [1014:0420]

Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID:   [14e4:1657]
Subsystem ID: [1014:0420]

Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID:   [14e4:1657]
Subsystem ID: [1014:0420]

Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID:   [14e4:1657]
Subsystem ID: [1014:0420]

Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID:   [14e4:1657]
Subsystem ID: [14e4:1981]

Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID:   [14e4:1657]
Subsystem ID: [14e4:1657]

--[ Devices found by Network Manager ]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged

Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged

Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged

Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged

Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged

Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged

Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged

Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
 crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
 
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
ProcLocks:
 1: POSIX  ADVISORY  WRITE 4149 00:14:817 0 EOF
 2: POSIX  ADVISORY  WRITE 1701 00:14:477 0 EOF
 3: POSIX  ADVISORY  WRITE 4014 00:14:789 0 EOF
 4: POSIX  ADVISORY  WRITE 4033 00:14:802 0 EOF
 5: FLOCK  ADVISORY  WRITE 4012 00:14:798 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -1
ProcVersion: Linux version 4.4.0-66-generic (buildd@bos01-ppc64el-025) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #87-Ubuntu SMP Fri 
Mar 3 15:30:20 UTC 2017
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-66-generic N/A
 linux-backports-modules-4.4.0-66-generic  N/A
 linux-firmware1.157.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh 

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

This issue, or similar symptoms doesn't seem to be fixed. This is with
stock kernel, stock stress-ng but with the suggested changes to the
memory_stress_ng test script. The machine locks up completely maybe 1
out of 5-10 runs. See attached dmesg for errors.

Kernel: 4.4.0-64-generic-85-Ubuntu
stress-ng Version: 0.07.21-1~ppa

** Attachment added: "FAIL-2017-03-09-15-21-47.dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4837690/+files/FAIL-2017-03-09-15-21-47.dmesg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in Provider for Plainbox - Checkbox:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

Just to be sure I installed qemu-system-ppc version 1:2.6.1+dfsg-
0ubuntu5.3 from yakkety-updates and the tests pass.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Incomplete

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

We received the hardware back and have started testing all blockers
again. The latest test of the above mentioned PPA did not yield positive
results:

"Unable to find PowerPC CPU definition"

$ apt-cache policy qemu-system-ppc
qemu-system-ppc:
  Installed: 1:2.5+dfsg-5ubuntu10.10
  Candidate: 1:2.5+dfsg-5ubuntu10.10
  Version table:
 *** 1:2.5+dfsg-5ubuntu10.10 500
500 http://ppa.launchpad.net/ci-train-ppa-service/2502/ubuntu 
xenial/main ppc64el Packages
100 /var/lib/dpkg/status
 1:2.5+dfsg-5ubuntu10.9 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el 
Packages
 1:2.5+dfsg-5ubuntu10.6 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
 1:2.5+dfsg-5ubuntu10 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
$ uname -a
Linux fesenkov 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:30:20 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Incomplete

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

We still have not received the machine back from IBM.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

@paelzer the machine was sent out for repair/replacement. We expect it
to return later this week. I will test the package from the above PPA as
soon as it is back.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

@Christian

The qemu fix is still necessary in order to resolve the issue.

While I do have access to the hardware, it is currently having issues
booting. Once we resolve the issue with IBM, I plan on testing out the
qemu fix from the PPA.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

@Christian The branch is for a fix in the plainbox-provider-checkbox
package which is part of the certification suite. It is not for qemu-
system-ppc but is a necessary part of the overall fix since the script
was originally assuming POWER8.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

** Merge proposal linked:
   
https://code.launchpad.net/~leftyfb/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/315823

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

In my testing, only qemu-system-ppc version 1:2.6.1+dfsg-0ubuntu5.2
available in yakkety and the template to set -cpu POWER8NVL was needed
to resolve the issue. No kernel patches were necessary.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  New

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

KVM was never tested successfully on this particular model. The
virtualization test works fine on all other open power servers we have
in the labs.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

4.10 RC3 gives a kernel panic:

[3.863436] ahci 0009:04:00.0: AHCI 0001. 32 slots 4 ports 6 Gbps 0xf 
impl SATA mode
[3.863631] ahci 0009:04:00.0: flags: 64bit ncq sntf led only pmp fbs pio 
slum part sxs 
[3.864221] scsi host0: ahci
[3.864404] scsi host1: ahci
[3.864562] scsi host2: ahci
[3.864715] scsi host3: ahci
[3.864781] ata1: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810100 irq 447
[3.864826] ata2: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810180 irq 447
[3.864871] ata3: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810200 irq 447
[3.864917] ata4: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810280 irq 447
[3.869801] [drm] platform has no IO space, trying MMIO
[3.869832] [drm] AST 2400 detected
[3.869863] [drm] Analog VGA only
[3.869896] [drm] dram 163200 7 16 00c0
[3.869970] [TTM] Zone  kernel: Available graphics memory: 267838144 kiB
[3.870007] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[3.870044] [TTM] Initializing pool allocator
[3.870076] [TTM] Initializing DMA pool allocator
[3.874823] fb: switching to astdrmfb from OFfb vga
[3.874938] Console: switching to colour dummy device 80x25
[3.899718] nouveau 0002:01:00.0: enabling device (0140 -> 0142)
[3.928774] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: c02ad0d4
[3.928774] 
[3.928776] CPU: 11 PID: 1118 Comm: systemd-udevd Not tainted 4.10.0-041000r

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

As mentioned above, I have run the test multiple times with SMT both
enabled and disabled. I get the same error. This is from running the
test just now with SMT disabled:

WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.
kvm_init_vcpu failed: Invalid argument


Also, KVM does in fact work with SMT enabled on ppc64el in PowerNV mode. KVM 
does not work with SMT enabled on a guest in PowerKVM mode. I have just run the 
test on the Power S822LC (8335-GTA Non-Virtualized) in PowerNV mode with SMT 
enabled and the guest booted fine.

That said, to limit variables, I will run the tests on the current
server with SMT disabled for the duration of the troubleshooting.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present

[Mike Rushton]

This test has been run dozens of times across multiple machines and
deployments and reboots. It is completely reproducible.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1652132/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1656112] [NEW] Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

Public bug reported:

Upon running the virtualization test from the certification test suite,
the kvm guest test fails with the following error:

kvm_init_vcpu failed: Invalid argument

This same test works on multiple other IBM Power 8 and Openpower
servers. kvm-ok tells us that kvm virtualization is supported. I have
tried with SMT enabled and disabled. I have tried the latest cloud image
as well as previous onces we had saved. I have tried running the qemu-
system-ppc64 command found below manually with the same error.


The full output from the test is as follows:

Executing KVM Test
DEBUG:root:Starting KVM Test
DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
DEBUG:root:Creating cloud user-data
DEBUG:root:Creating cloud meta-data
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 331
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
183 extents written (0 MB)
DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
DEBUG:root:Attaching Cloud config disk
DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm 
-machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic ppc64le
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
 crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Jan 12 22:45:34 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
 Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
ProcLocks:
 1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
 2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
 3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
 4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
 5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -1
ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware1.157.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_dscr: DSCR is 0
cpu_freq:
 min:   3.959 GHz (cpu 79)
 max:   3.988 GHz (cpu 81)
 avg:   3.974 GHz
cpu_runmode:
 Could not retrieve current diagnostics mode,
 No kernel interface to firmware
cpu_smt: SMT=8

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug blocks-hwcert-server ppc64el uec-images xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is 

[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present

[Mike Rushton]

apport-collect is not functioning on this server:

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: /var/log/opal-elog: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
...dpkg-query: no packages found matching linux
.


The dots go on forever

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1652132/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present

[Mike Rushton]

** Summary changed:

- Call trace when testing fstat stressor on ppc64el with virtual  keyboard and 
mouse
+ Call trace when testing fstat stressor on ppc64el with virtual  keyboard and 
mouse present

** Tags added: blocks-hwcert-server

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse

[Mike Rushton]

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+attachment/4795377/+files/kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse

[Mike Rushton]

** Attachment added: "dmesg1.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+attachment/4795378/+files/dmesg1.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1652132] [NEW] Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present

[Mike Rushton]

Public bug reported:

Ubuntu 16.04.1
Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

When running the stress-ng "fstat" stressor, it is trying to access the
USB bus and giving a call trace and locking up any further USB activity
(lsusb hangs). This only seems to occur so far on openpower(Firestone
and Garrison) where there is a virtual USB keyboard and mouse built into
the BMC.

>From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
Megatrends, Inc. Virtual Keyboard and Mouse

Another openpower server(Briggs) has no virtual usb devices and does not
experience the failure.

Please see attached kern.log and dmesg output for further details.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

dmesg output while stress_ng test was running on Power 8 Tuleta LPAR

** Attachment added: "dmesg2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788537/+files/dmesg2

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

output of stress_ng test running on Power 8 Tuleta LPAR

** Attachment added: "3.19.0-15-generic-15-Ubuntu.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788536/+files/3.19.0-15-generic-15-Ubuntu.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

`ps -ax` output while stress_ng test was running on Power 8 Tuleta LPAR

** Attachment added: "ps2.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788538/+files/ps2.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1640547] Re: stress-ng tests failing

[Mike Rushton]

** Also affects: plainbox-provider-checkbox (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

** Changed in: plainbox-provider-checkbox (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1640547

Title:
  stress-ng tests failing

Status in plainbox-provider-checkbox package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in plainbox-provider-checkbox source package in Xenial:
  New

Bug description:
  When running the stress-ng disk test, we are seeing the following
  failures as well as I/O lockup:

  /dev/sda is a block device
  Found largest partition: "/dev/sda2"
  Test will use /dev/sda2, mounted at "/", using "ext4"
  test_dir is /tmp/disk_stress_ng
  Estimated total run time is 4560 seconds

  Running stress-ng aio stressor for 240 seconds
  stress-ng: info:  [4305] dispatching hogs: 160 aio
  stress-ng: info:  [4305] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4305] cache allocate: default cache size: 2048K
  stress-ng: info:  [4305] successful run completed in 240.27s (4 mins, 0.27 
secs)
  return_code is 0
  Running stress-ng aiol stressor for 240 seconds
  stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
  stress-ng: info:  [4917] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4917] cache allocate: default cache size: 2048K
  stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5040] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5026] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5027] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5031] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5049] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5021] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5045] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5047] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5044] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5052] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5029] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5015] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5053] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5051] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5063] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5058] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5054] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5061] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5059] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5055] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5023] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not 

[Kernel-packages] [Bug 1640547] Re: stress-ng tests failing

[Mike Rushton]

** Summary changed:

- Disk test fails on IBM Power S822LC (8335-GTB)
+ stress-ng tests failing

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1640547

Title:
  stress-ng tests failing

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  When running the stress-ng disk test, we are seeing the following
  failures as well as I/O lockup:

  /dev/sda is a block device
  Found largest partition: "/dev/sda2"
  Test will use /dev/sda2, mounted at "/", using "ext4"
  test_dir is /tmp/disk_stress_ng
  Estimated total run time is 4560 seconds

  Running stress-ng aio stressor for 240 seconds
  stress-ng: info:  [4305] dispatching hogs: 160 aio
  stress-ng: info:  [4305] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4305] cache allocate: default cache size: 2048K
  stress-ng: info:  [4305] successful run completed in 240.27s (4 mins, 0.27 
secs)
  return_code is 0
  Running stress-ng aiol stressor for 240 seconds
  stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
  stress-ng: info:  [4917] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4917] cache allocate: default cache size: 2048K
  stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5040] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5026] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5027] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5031] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5049] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5021] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5045] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5047] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5044] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5052] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5029] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5015] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5053] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5051] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5063] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5058] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5054] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5061] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5059] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5055] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5023] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5036] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5030] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  

[Kernel-packages] [Bug 1640547] Re: Disk test fails on IBM Power S822LC (8335-GTB)

[Mike Rushton]

Also seeing this problem on Dell PowerEdge with a xeon phi processor and
4.8 kernel on Ubuntu 16.10.

See attached.

** Attachment added: "disk_test.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640547/+attachment/4775439/+files/disk_test.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1640547

Title:
  Disk test fails on IBM Power S822LC (8335-GTB)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  When running the stress-ng disk test, we are seeing the following
  failures as well as I/O lockup:

  /dev/sda is a block device
  Found largest partition: "/dev/sda2"
  Test will use /dev/sda2, mounted at "/", using "ext4"
  test_dir is /tmp/disk_stress_ng
  Estimated total run time is 4560 seconds

  Running stress-ng aio stressor for 240 seconds
  stress-ng: info:  [4305] dispatching hogs: 160 aio
  stress-ng: info:  [4305] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4305] cache allocate: default cache size: 2048K
  stress-ng: info:  [4305] successful run completed in 240.27s (4 mins, 0.27 
secs)
  return_code is 0
  Running stress-ng aiol stressor for 240 seconds
  stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
  stress-ng: info:  [4917] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4917] cache allocate: default cache size: 2048K
  stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5040] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5026] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5027] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5031] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5049] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5021] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5045] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5047] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5044] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5052] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5029] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5015] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5053] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5051] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5063] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5058] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5054] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5061] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5059] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5055] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5023] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  

[Kernel-packages] [Bug 1640547] [NEW] Disk test fails on IBM Power S822LC (8335-GTB)

[Mike Rushton]

Public bug reported:

When running the stress-ng disk test, we are seeing the following
failures as well as I/O lockup:

/dev/sda is a block device
Found largest partition: "/dev/sda2"
Test will use /dev/sda2, mounted at "/", using "ext4"
test_dir is /tmp/disk_stress_ng
Estimated total run time is 4560 seconds

Running stress-ng aio stressor for 240 seconds
stress-ng: info:  [4305] dispatching hogs: 160 aio
stress-ng: info:  [4305] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [4305] cache allocate: default cache size: 2048K
stress-ng: info:  [4305] successful run completed in 240.27s (4 mins, 0.27 secs)
return_code is 0
Running stress-ng aiol stressor for 240 seconds
stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
stress-ng: info:  [4917] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [4917] cache allocate: default cache size: 2048K
stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5040] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5026] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5027] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5031] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5049] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5021] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5045] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5047] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5044] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5052] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5029] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5015] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5053] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5051] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5063] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5058] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5054] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5061] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5059] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5055] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5023] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5036] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5030] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5060] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5046] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5066] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5050] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  [5048] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
stress-ng: fail:  

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Attachment added: "alpine.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740352/+files/alpine.xml

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Attachment added: "gulpin.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740353/+files/gulpin.xml

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Attachment added: "tuleta.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740354/+files/tuleta.xml

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

1. Can we get the configurations of the machines.

XML files for all 4 machines with hardware information from the
certification process will be attached in the next few comments


2. The first column is the number of times the test ran?

Yes


4. Did any of the tests result in system hang? Can we find out from the summary?

All failed tests failed with a complete system hang. The only way to
recover would be to reboot.

** Attachment added: "binacle.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740351/+files/binacle.xml

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

Sorry, I should have taken out the 4.4.0-31 tests. That test was not
using stress-ng but our original memory stress test.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

Attached is the cultivation of all the kernel testing we have done.

** Attachment added: "Power Testing Result.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4732427/+files/Power%20Testing%20Result.pdf

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Summary changed:

- memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
+ memory_stress_ng failing for Power architecture for 16.04

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

dmesg from failed test on Firestone

** Attachment added: "dmesg1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723529/+files/dmesg1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Out of the 4 tests last night (Habanero(NV), Firstone(NV), Tuleta(NV),
Alpine(VM) only the Firestone failed. Attached is the output from the
test, kern.log and dmesg output I was running in a while loop during
testing.

** Attachment added: "FAIL-2016-08-18-03-25-32.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723527/+files/FAIL-2016-08-18-03-25-32.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

kern.log from failed test on Firestone

** Attachment added: "FAIL-2016-08-18-03-25-32.kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723528/+files/FAIL-2016-08-18-03-25-32.kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

kern.log from the Habanero 4.4.0-34-generic-53~lp1573062PATCHED test

** Attachment added: "FAIL-2016-08-17-17-49-41.kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723089/+files/FAIL-2016-08-17-17-49-41.kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

kern.log from the Firestone 4.4.0-34-generic-53~lp1573062PATCHED test

** Attachment added: "FAIL-2016-08-17-17-12-46.kern.log.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723091/+files/FAIL-2016-08-17-17-12-46.kern.log.tar.gz

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

This is a failed test from today on the Firestone. Find the test output
and kern.log attached:

ubuntu@gulpin:~/4.4.0-34-generic-53~lp1573062PATCHED$ free -m
  totalusedfree  shared  buff/cache   available
Mem:  32565 342   30092  212131   30918
Swap:  8191   08191


** Attachment added: "FAIL-2016-08-17-17-12-46.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723090/+files/FAIL-2016-08-17-17-12-46.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

This is a failed test from today on the Habanero. Find the test output
and kern.log attached:

ubuntu@binacle:~/4.4.0-34-generic-53~lp1573062PATCHED$ free -m
  totalusedfree  shared  buff/cache   available
Mem: 261533 621  259912  201000  259938
Swap:  8191   08191


** Attachment added: "FAIL-2016-08-17-17-49-41.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723088/+files/FAIL-2016-08-17-17-49-41.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Kalpana:

The above failed test was run on only 1 of the possible 4 machines we
have been testing with for months now. The other openpower server is a
Habanero with 256G. I am running tests on that as we speak and going to
include the kern.log as well.

Just to clarify, the memory test I'm running is /usr/lib/plainbox-
provider-checkbox/bin/memory_stress_ng

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

I had this fail on 2 openpower boxes. I have attached the output from
the test.

** Attachment added: "4.4.0-34-generic-53~lp1573062PATCHED.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4722751/+files/4.4.0-34-generic-53~lp1573062PATCHED.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

mainline kernel 4.7 failed.


** Attachment added: "kern.log from 4.7 testing failure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4708871/+files/kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Output of 4.7 mainline kernel testing failure

** Attachment added: "4.7.0-040700-generic-201607241632.log from 4.7 testing 
failure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4708872/+files/4.7.0-040700-generic-201607241632.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Attached is the kern.log from the Firestone PowerNV server. This one is
failing with stack traces which only started after we started testing
patched kernels.

The Habanero PowerNV failed with the typical locked up console and
OOM's.

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4703165/+files/kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

I'm running the tests as we speak across 2 LPAR's and 2 openpower
PowerNV installations. One of the open power boxes has 256G of memory so
it takes up to 7 hours for a test to pass or to be determined failed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

4.4.0-32-generic-51~lp1573062.1 failed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

kern.log attached to show additional failures with patched kernel

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4698878/+files/kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Commit failed:
4f1b50c3e3082b31c94cee2b897bd9f5d0f3e7c8

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Commit failed:
ddc8f6feec76b5deea8090db015920a283006044

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Commit failed:
ee61e95b6b33c82f6fa1382585faed66aa01245

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

The memory_stress_ng test is part of the plainbox-provider-checkbox
package which can be installed from the hardware-certification PPA:

https://code.launchpad.net/~hardware-
certification/+archive/ubuntu/public

The full path once installed is:
/usr/lib/plainbox-provider-checkbox/bin/memory_stress_ng

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

895a1067d5b83065afbad3bb02c3c464b71f1b3f failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

d9dddbf556674bf125ecd925b24e43a5cf2a568a failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

45996492e5c85aa0ac93a95d1b2d1ed56851c865 failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

8f40842e4260f73792c156aded004197a19135ee failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

4.5.0-040500-generic-201605251558 failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

PASS,2016-05-23-13-21-37,4.5.0-040500-generic-201605230752
FAIL,2016-05-23-21-06-07,4.5.0-040500-generic-201605230752
PASS,2016-05-24-04-32-39,4.5.0-040500-generic-201605230752
FAIL,2016-05-24-13-31-01,4.5.0-040500-generic-201605230752
FAIL,2016-05-25-04-06-51,4.5.0-040500-generic-201605230752

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

4.5.0-040500.201605171117 failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

I would go ahead and assume it's good. I haven't had 2 tests run good
twice in a row yet.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

So far, after 2 runs, 4.5.0-040500-generic_4.5.0-040500.201605161244
seems to be working. I'm running it a 3rd time now just to be sure. It
takes about 7 hours to finish.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Testing now...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

4.5.0-040500.201603140130_ppc64el - fail
4.6.0-040600rc1.201603261930_ppc64el - pass

4.6 was run twice and passed both times.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

I have noticed only on the Alpine hardware within an LPAR that is has
been sporadic. I assume that is due to the additional hardware resources
that can better handle the memory/stress test. All other tests have been
2 or 3 times each. More more than that. I can run the above kernel
tests, but mind you, each test takes several hours to half a days worth.
Running each test multiple times could take about a week to complete. We
really need to get this sorted out ASAP since it is holding up all Power
certification.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Ubuntu 14.04
3.19.0-58-generic - pass
4.2.0-35-generic - fails
4.1.0-040100-generic - fail
4.6.0-040600rc6-generic - pass

Ubuntu 16.04
4.4.0-22-generic - fail
4.1.0-040100-generic - fail
4.6.0-040600rc6-generic - pass

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Confirmed the above kernel fails in the same manner.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Are there ppc64le versions of those kernels?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

The tests run manually above were NOT run as root. The test during
certification does run as root. I have run the test as root and as the
ubuntu user, both with the same results.

Also, as shown above, this test ran fine manually while running Ubuntu
14.04 without root and during proper certification testing as root.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

The very first line of the screen session shows how the test is being
run:

/usr/lib/plainbox-provider-checkbox/bin/memory_stress_ng

The machine is completely unresponsive. No ssh, no ping and the console
over ipmi is locked up. Hitting CTRL+C over the sol console does nothing
at all. This is after leaving the test running for 18+ hours where it
should only take around 1-3 hours tops to complete depending on the
machine. As you can see on the same machine running the same test on
14.04, the test took about an hour to complete with no lockup at the
end.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

screen session log from successful test on 14.04

** Attachment added: "screen session log from successful test on 14.04"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641500/+files/14.04.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

screen session of failure

** Attachment added: "screen session of failure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641490/+files/screenlog.0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

kern.log from successful test on 14.04

** Attachment added: "kern.log from successful test on 14.04"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641501/+files/1404-kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

kern.log from failure

** Attachment added: "kern.log from failure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641492/+files/kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1573062] [NEW] memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Public bug reported:

memory_stress_ng, as part of server certification is failing for IBM
Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
defined by the test locking up the server in an unrecoverable state
which only a reboot will fix.

I will be attaching screen and kern logs for the failures and a
successful run on 14.04 on the same server.

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


** Tags: blocks-hwcert-server

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

I have also shown that this issue has the exact same results on PowerNV
above.


** Changed in: qemu
   Status: Invalid => Confirmed

** Changed in: qemu (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.

PowerVM mode is an LPAR. It is not a kvm instance trying to run an KVM
within. This was also working in 14.04 without issue and is being asked
of us from IBM to certify

2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv. A workaround is to use the isos which do boot.
This is a cloud-images bug.

All the Xenial daily images i've been using from MAAS deployments have
been the 4.4 kernel which is still not working.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

The PowerVM  machine I've been using for these tests has the following
output:

ubuntu@alpine01:~/kvm$ cat /proc/cpuinfo | grep platform
platform: pSeries


The PowerNV server has the following output:

ubuntu@binacle:~$ cat /etc/issue; uname -a ; ppc64_cpu --smt ; cat 
/proc/cpuinfo |grep platform
Ubuntu Xenial Xerus (development branch) \n \l

Linux binacle 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
SMT is off
platform: PowerNV

ubuntu@binacle:~$ sudo qemu-system-ppc64 -enable-kvm -m 256 -display none 
-nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.


SLOF **
QEMU Starting
 Build Date = Jan 29 2016 18:58:37
 FW Version = buildd@ release 20151103
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103
   SCSI: Looking for devices
  8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
Populating /pci@8002000
 00 1800 (D) : 1af4 1001virtio [ block ]
 00 1000 (D) : 1af4 1001virtio [ block ]
 00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
 00  (D) : 1234 qemu vga
No NVRAM common partition, re-initializing...
Installing QEMU fb


Scanning USB 
  OHCI: initializing
USB Keyboard 
USB mouse 
No console specified using screen & keyboard
 
  Welcome to Open Firmware

  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php


Trying to load:  from: /pci@8002000/scsi@3 ... 
E3404: Not a bootable device!
Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
Linux ppc64le
#32-Ubuntu SMP T

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

Sorry, I copied the wrong thing:

sudo qemu-system-ppc64 -enable-kvm -m 256 -display none -nographic -net nic 
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries 
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
ioctl(KVM_CREATE_VM) failed: 22 Invalid argument
failed to initialize KVM: Invalid argument

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

@mdroth

I don't think PPC supports kvm the same way as x86:

ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -m 256 -display none 
-nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

@serge-hallyn

ubuntu@alpine01:~/kvm$ cat /etc/issue; uname -a ; ppc64_cpu --smt
Ubuntu Xenial Xerus (development branch) \n \l

Linux alpine01 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
SMT is off
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.


SLOF **
QEMU Starting
 Build Date = Jan 29 2016 18:58:37
 FW Version = buildd@ release 20151103
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103
   SCSI: Looking for devices
  8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
Populating /pci@8002000
 00 1800 (D) : 1af4 1001virtio [ block ]
 00 1000 (D) : 1af4 1001virtio [ block ]
 00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
 00  (D) : 1234 qemu vga
No NVRAM common partition, re-initializing...
Installing QEMU fb


Scanning USB 
  OHCI: initializing
USB Keyboard 
USB mouse 
No console specified using screen & keyboard
 
  Welcome to Open Firmware

  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php


Trying to load:  from: /pci@8002000/scsi@3 ... 
E3404: Not a bootable device!
Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
Linux ppc64le
#31-Ubuntu SMP F

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

ubuntu@alpine01:~$ sudo  ppc64_cpu --smt=1
ubuntu@alpine01:~$ ppc64_cpu --info
Core   0:0*1 2 3 4 5 6 7  
Core   1:8*9101112131415  
Core   2:   16*   17181920212223  
Core   3:   24*   25262728293031  
Core   4:   32*   33343536373839  
Core   5:   40*   41424344454647  
Core   6:   48*   49505152535455  
Core   7:   56*   57585960616263  

ubuntu@alpine01:~$ sudo ppc64_cpu --smt
SMT is off


Still freezing at the same point.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

ubuntu@alpine01:~$ ppc64_cpu --info
Core   0:0*1*2*3*4*5*6*7* 
Core   1:8*9*   10*   11*   12*   13*   14*   15* 
Core   2:   16*   17*   18*   19*   20*   21*   22*   23* 
Core   3:   24*   25*   26*   27*   28*   29*   30*   31* 
Core   4:   32*   33*   34*   35*   36*   37*   38*   39* 
Core   5:   40*   41*   42*   43*   44*   45*   46*   47* 
Core   6:   48*   49*   50*   51*   52*   53*   54*   55* 
Core   7:   56*   57*   58*   59*   60*   61*   62*   63* 
ubuntu@alpine01:~$ ppc64_cpu --smt off
SMT=8
ubuntu@alpine01:~$ ppc64_cpu --info
Core   0:0*1*2*3*4*5*6*7* 
Core   1:8*9*   10*   11*   12*   13*   14*   15* 
Core   2:   16*   17*   18*   19*   20*   21*   22*   23* 
Core   3:   24*   25*   26*   27*   28*   29*   30*   31* 
Core   4:   32*   33*   34*   35*   36*   37*   38*   39* 
Core   5:   40*   41*   42*   43*   44*   45*   46*   47* 
Core   6:   48*   49*   50*   51*   52*   53*   54*   55* 
Core   7:   56*   57*   58*   59*   60*   61*   62*   63* 

Still freezing at the same point:

Trying to load:  from: disk ...   Successfully loaded
* finddevice /memory grub workaround *
* finddevice /memory grub workaround *
* finddevice /memory grub workaround *
Linux ppc64le
#31-Ubuntu SMP F


This is running on an LPAR in PowerNV mode.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 

[Kernel-packages] [Bug 1563055] Re: IBM ppc64le MAAS images booting with no network

[Mike Rushton]

Due to the nature of no network connectivity, We cannot login (curtin
preseed didn't run to setup credentials) or submit logs.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563055

Title:
  IBM ppc64le MAAS images booting with no network

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest daily Xenial image for MAAS seems to lack network
  connectivity. Tested with kernel version 4.4.0-15 from the 20160328
  image from the daily stream

  Attached are logs from the boot sequence as well as the maas
  deployment logs.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1563055] Re: IBM Power8 PPC MAAS images booting with no network

[Mike Rushton]

** Attachment added: "regiond.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615238/+files/regiond.log

** Summary changed:

- IBM Power8 PPC MAAS images booting with no network
+ IBM ppc64le MAAS images booting with no network

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563055

Title:
  IBM ppc64le MAAS images booting with no network

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest daily Xenial image for MAAS seems to lack network
  connectivity. Tested with kernel version 4.4.0-15 from the 20160328
  image from the daily stream

  Attached are logs from the boot sequence as well as the maas
  deployment logs.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1563055] Re: IBM Power8 PPC MAAS images booting with no network

[Mike Rushton]

** Attachment added: "sutboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615236/+files/sutboot.txt

** Description changed:

  The latest daily Xenial image for MAAS seems to lack network
  connectivity. Tested with kernel version 4.4.0-15 from the 20160328
  image from the daily stream
  
- Loading Linux 4.4.0-15-generic ...
- [0.481658] Trying to unpack rootfs image as initramfs...
- [0.937992] Freeing initrd memory: 34944K (ca10 - 
cc32)
- [0.953239] hv-24x7: read 1246 catalog entries, created 1265 event attrs 
(0 failures), 127 descs
- [0.954323] futex hash table entries: 16384 (order: 5, 2097152 bytes)
- [0.954592] audit: initializing netlink subsys (disabled)
- [0.954616] audit: type=2000 audit(1459199110.948:1): initialized
- [0.955795] Initialise system trusted keyring
- [0.956644] HugeTLB registered 16 MB page size, pre-allocated 0 pages
- [0.956647] HugeTLB registered 16 GB page size, pre-allocated 0 pages
- [0.958246] zbud: loaded
- [0.959110] VFS: Disk quotas dquot_6.6.0
- [0.959386] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 
bytes)
- [0.962783] fuse init (API version 7.23)
- [0.963583] Key type big_key registered
- [0.963988] Key type asymmetric registered
- [0.963992] Asymmetric key parser 'x509' registered
- [0.964246] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 247)
- [0.964499] io scheduler noop registered
- [0.964504] io scheduler deadline registered (default)
- [0.964755] io scheduler cfq registered
- [0.964811] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
- [0.965118] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
- [0.966332] Linux agpgart interface v0.103
- [0.972959] brd: module loaded
- [0.977622] loop: module loaded
- [0.978001] libphy: Fixed MDIO Bus: probed
- [0.978004] tun: Universal TUN/TAP device driver, 1.6
- [0.978006] tun: (C) 1999-2004 Max Krasnyansky 
- [0.978064] tg3.c:v3.137 (May 11, 2014)
- [0.978228] tg3 0002:01:00.0: enabling device (0140 -> 0142)
- [1.006932] tg3 0002:01:00.0: ibm,query-pe-dma-windows(53) 1 800 
2018 returned 0
- [1.007194] tg3 0002:01:00.0 eth0: Tigon3 [partno(00E2872) rev 5719001] 
(PCI Express) MAC address 40:f2:e9:5d:be:68
- [1.007200] tg3 0002:01:00.0 eth0: attached PHY is 5719C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
- [1.007204] tg3 0002:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
- [1.007207] tg3 0002:01:00.0 eth0: dma_rwctrl[] dma_mask[64-bit]
- [1.01] tg3 0002:01:00.1: enabling device (0140 -> 0142)
- [1.039069] tg3 0002:01:00.1 eth1: Tigon3 [partno(00E2872) rev 5719001] 
(PCI Express) MAC address 40:f2:e9:5d:be:69
- [1.039079] tg3 0002:01:00.1 eth1: attached PHY is 5719C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
- [1.039083] tg3 0002:01:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
- [1.039087] tg3 0002:01:00.1 eth1: dma_rwctrl[] dma_mask[64-bit]
- [1.041876] tg3 0002:01:00.2: enabling device (0140 -> 0142)
- [1.067054] tg3 0002:01:00.2 eth2: Tigon3 [partno(00E2872) rev 5719001] 
(PCI Express) MAC address 40:f2:e9:5d:be:6a
- [1.067063] tg3 0002:01:00.2 eth2: attached PHY is 5719C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
- [1.067067] tg3 0002:01:00.2 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
- [1.067070] tg3 0002:01:00.2 eth2: dma_rwctrl[] dma_mask[64-bit]
- [1.069862] tg3 0002:01:00.3: enabling device (0140 -> 0142)
- [1.095119] tg3 0002:01:00.3 eth3: Tigon3 [partno(00E2872) rev 5719001] 
(PCI Express) MAC address 40:f2:e9:5d:be:6b
- [1.095129] tg3 0002:01:00.3 eth3: attached PHY is 5719C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
- [1.095134] tg3 0002:01:00.3 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
- [1.095137] tg3 0002:01:00.3 eth3: dma_rwctrl[] dma_mask[64-bit]
- [1.097856] ehea: IBM eHEA ethernet device driver (Release EHEA_0107)
- [1.097873] PPP generic driver version 2.4.2
- [1.097928] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
- [1.097938] ehci-pci: EHCI PCI platform driver
- [1.097948] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
- [1.097952] ohci-pci: OHCI PCI platform driver
- [1.097962] uhci_hcd: USB Universal Host Controller Interface driver
- [1.098083] mousedev: PS/2 mouse device common for all mice
- [1.098139] i2c /dev entries driver
- [1.098394] device-mapper: uevent: version 1.0.3
- [1.098764] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: 
dm-de...@redhat.com
- [1.099548] ledtrig-cpu: registered to indicate activity on CPUs
- [1.101295] NET: Registered protocol family 10
- [1.102023] NET: Registered protocol family 17
- [1.102035] 

[Kernel-packages] [Bug 1563055] Re: IBM Power8 PPC MAAS images booting with no network

[Mike Rushton]

** Attachment added: "clusterd.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615237/+files/clusterd.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563055

Title:
  IBM ppc64le MAAS images booting with no network

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest daily Xenial image for MAAS seems to lack network
  connectivity. Tested with kernel version 4.4.0-15 from the 20160328
  image from the daily stream

  Attached are logs from the boot sequence as well as the maas
  deployment logs.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp