from:"Mike"

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

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

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

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

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

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

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

2016-04-06 Thread 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
   
/pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.00

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-04-06 Thread 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

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!
  Try

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

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
   
/pci@8002018/ethernet@0:speed=auto,duplex

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

@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

@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
  U

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

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 5.3.1-12ubunt

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-04-04 Thread 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 1564237] Re: Acer touchpad stopped working with kernel 3.19.0-56

** Attachment added: "dmesg log from 3.19.0-56, not working"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1564237/+attachment/4617903/+files/bad.dmesg

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

Title:
  Acer touchpad stopped working with kernel 3.19.0-56

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  After Ubuntu updated the kernel to 3.19.0-56 the touchpad stopped working.
  The mouse pointer never appears and touching/dragging/clicking has no effect.
  I can make it work by using the GRUB menu to boot 3.19.0-49 instead.

  On the older, working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYN1B7D:01 06CB:2991 UNKNOWNid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=13   [slave  
keyboard (3)]

  On the new, not working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=12   [slave  
keyboard (3)]

  Hardware is Acer ES1-111M-C40S laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 30 21:52:31 2016
  InstallationDate: Installed on 2015-10-20 (162 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1564237/+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 1564237] Re: Acer touchpad stopped working with kernel 3.19.0-56

I noticed in dmesg:

Working kernel:
[3.565137] i2c_hid i2c-SYN1B7D:01: failed to retrieve report from device.
[3.565306] input: SYN1B7D:01 06CB:2991 UNKNOWN as 
/devices/platform/80860F41:00/i2c-0/i2c-SYN1B7D:01/0018:06CB:2991.0001/input/input8
[3.565618] hid-multitouch 0018:06CB:2991.0001: input,hidraw0:  HID 
v1.00 Mouse [SYN1B7D:01 06CB:2991] on

Not working kernel:
[3.572672] i2c_designware 80860F41:00: controller timed out
[3.572682] i2c_designware 80860F41:00: Unknown Synopsys component type: 
0x
[3.572690] i2c_hid i2c-SYN1B7D:01: hid_descr_cmd failed

I'll attach both full dmesg logs.

** Attachment added: "dmesg log from 3.19.0-49, working"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1564237/+attachment/4617902/+files/good.dmesg

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

Title:
  Acer touchpad stopped working with kernel 3.19.0-56

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  After Ubuntu updated the kernel to 3.19.0-56 the touchpad stopped working.
  The mouse pointer never appears and touching/dragging/clicking has no effect.
  I can make it work by using the GRUB menu to boot 3.19.0-49 instead.

  On the older, working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYN1B7D:01 06CB:2991 UNKNOWNid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=13   [slave  
keyboard (3)]

  On the new, not working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=12   [slave  
keyboard (3)]

  Hardware is Acer ES1-111M-C40S laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 30 21:52:31 2016
  InstallationDate: Installed on 2015-10-20 (162 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1564237/+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 1564237] Re: Acer touchpad stopped working with kernel 3.19.0-56

I noticed in dmesg:

Working kernel:
[3.565137] i2c_hid i2c-SYN1B7D:01: failed to retrieve report from device.
[3.565306] input: SYN1B7D:01 06CB:2991 UNKNOWN as 
/devices/platform/80860F41:00/i2c-0/i2c-SYN1B7D:01/0018:06CB:2991.0001/input/input8
[3.565618] hid-multitouch 0018:06CB:2991.0001: input,hidraw0:  HID 
v1.00 Mouse [SYN1B7D:01 06CB:2991] on

Not working kernel:
[3.572672] i2c_designware 80860F41:00: controller timed out
[3.572682] i2c_designware 80860F41:00: Unknown Synopsys component type: 
0x
[3.572690] i2c_hid i2c-SYN1B7D:01: hid_descr_cmd failed

I'll attach both full dmesg logs.

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

Title:
  Acer touchpad stopped working with kernel 3.19.0-56

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  After Ubuntu updated the kernel to 3.19.0-56 the touchpad stopped working.
  The mouse pointer never appears and touching/dragging/clicking has no effect.
  I can make it work by using the GRUB menu to boot 3.19.0-49 instead.

  On the older, working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYN1B7D:01 06CB:2991 UNKNOWNid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=13   [slave  
keyboard (3)]

  On the new, not working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=12   [slave  
keyboard (3)]

  Hardware is Acer ES1-111M-C40S laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 30 21:52:31 2016
  InstallationDate: Installed on 2015-10-20 (162 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1564237/+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 1564237] [NEW] Acer touchpad stopped working with kernel 3.19.0-56

Public bug reported:

After Ubuntu updated the kernel to 3.19.0-56 the touchpad stopped working.
The mouse pointer never appears and touching/dragging/clicking has no effect.
I can make it work by using the GRUB menu to boot 3.19.0-49 instead.

On the older, working, kernel xinput outputs:
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ SYN1B7D:01 06CB:2991 UNKNOWN  id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ HD WebCam id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=12   [slave  keyboard (3)]
↳ Acer WMI hotkeys  id=13   [slave  keyboard (3)]

On the new, not working, kernel xinput outputs:
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ HD WebCam id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
↳ Acer WMI hotkeys  id=12   [slave  keyboard (3)]

Hardware is Acer ES1-111M-C40S laptop.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 30 21:52:31 2016
InstallationDate: Installed on 2015-10-20 (162 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Acer touchpad stopped working with kernel 3.19.0-56

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  After Ubuntu updated the kernel to 3.19.0-56 the touchpad stopped working.
  The mouse pointer never appears and touching/dragging/clicking has no effect.
  I can make it work by using the GRUB menu to boot 3.19.0-49 instead.

  On the older, working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYN1B7D:01 06CB:2991 UNKNOWNid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HD WebCam   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Acer WMI hotkeysid=13   [slave  
keyboard (3)]

  On the new, not working, kernel xinput outputs:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyb

[Kernel-packages] [Bug 1563055] Re: IBM ppc64le MAAS images booting with no network

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

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

** 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] Key type dns_resolv

[Kernel-packages] [Bug 1563055] Re: IBM Power8 PPC MAAS images booting with no network

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

[Kernel-packages] [Bug 1563055] [NEW] IBM ppc64le MAAS images booting with no network

Public bug reported:

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.

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


** Tags: blocks-hwcert-server

** Attachment added: "maas.log"
   https://bugs.launchpad.net/bugs/1563055/+attachment/4615235/+files/maas.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

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

2016-03-19 Thread Mike Gerow

Hi Joseph

I'll see if I can nab some extra hardware to try it out. Keep in mind
that I haven't found a way to reproduce this reliably yet, with our
usual setup it can take a few weeks before it happens. Basically we have
a cron job that periodically exports the state of our machines, which
includes calling lsusb. Eventually this bug happens, all future calls to
the job get stuck in D, and the machine eventually runs out of
resources, requiring it to be rebooted.

I did browse kernel sources upstream and didn't notice anything that
would appear to fix this issue, but I'm certainly no kernel-guru.

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

Title:
  khubd/usbhid deadlock(?) creates processes in state D

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (Note that the attached logs are not a machine exhibiting the issue)

  I've observed this issue specifically on Dell's PowerEdge R410 with
  its DRAC. I manage quite a few other machines with DRACs and haven't
  seen this issue so it may be limited to the R410. I've seen cases of
  this both with the precise and trusty kernel.

  Basically, what happens is that things that read any info about the
  DRAC's usbhid device will block in an uninterruptible state. A quick
  way to do this is with "cat
  /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This
  means that commands like lspci will block as well. The thing is that
  it doesn't happen every time, but once it happens the first time all
  future reads on the device will block in state D too.

  This is also associated with the following from the kernel (first from a 
precise machine):
  [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197857.716899] usb 5-2: device descriptor read/64, error -71
  [197857.944966] usb 5-2: device descriptor read/64, error -71
  [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197858.285090] usb 5-2: device descriptor read/64, error -71
  [197858.513108] usb 5-2: device descriptor read/64, error -71
  [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.145214] usb 5-2: device not accepting address 2, error -71
  [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.669322] usb 5-2: device not accepting address 2, error -71
  [197859.675357] usb 5-2: USB disconnect, device number 2
  [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
  [198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.551792] khubd   D 880803fe18a0 0   203  2 
0x
  [198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
  [198047.551809]  00013180 00013180 881003f7c800 
880804634800
  [198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

  [198047.551819] Call Trace:
  [198047.551828]  [] schedule+0x29/0x70
  [198047.551833]  [] schedule_preempt_disabled+0xe/0x10
  [198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
  [198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
  [198047.551848]  [] mutex_lock+0x23/0x37
  [198047.551852]  [] usb_disconnect+0x5a/0x210
  [198047.551857]  [] ? usb_control_msg+0xea/0x110
  [198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
  [198047.551864]  [] ? hub_port_status+0xd5/0x120
  [198047.551868]  [] hub_events+0x464/0x8c0
  [198047.551871]  [] ? __schedule+0x38e/0x700
  [198047.551875]  [] hub_thread+0x35/0x150
  [198047.551881]  [] ? __wake_up_sync+0x20/0x20
  [198047.551885]  [] ? hub_events+0x8c0/0x8c0
  [198047.551890]  [] kthread+0xc9/0xe0
  [198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551898]  [] ret_from_fork+0x58/0x90
  [198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
  [198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 
0x
  [198047.573547] Workqueue: events hid_reset [usbhid]
  [198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
  [198047.573555]  00013180 00013180 881003f94800 
8808011f
  [198047.573559]  8808011f9798 8808011f98d8 7fff 
7fff
  [198047.573564] Call Trace:
  [198047.573579]  [] schedule+0x29/0x70
  [198047.573582]  [] schedule_timeout+0x1e5/0x250
  [198047.573587]  [] ? wake_affine+0x16d/0x2d0
  [198047.573591]  [] wait_for_completion+0xa7/0x160
  [198047.573596]  [] ? try_to_wake_up+0x210/0x210
  [198047.573602]  [] flush_work+0x29/0x

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

2016-03-14 Thread Mike Gerow

Sorry, I'm not super familiar with apport (our security folks make us
disable it because they get upset for reasons I don't quite grasp).

I tried to install apport and python-apport, but no dice on actually
running apport-collect.

$ apport-collect 1557172
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 370, in 
if not app.run_argv():
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 525, in 
run_update_report
pkgs = self.crashdb.get_affected_packages(self.options.update_report)
  File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/memory.py", line 
79, in get_affected_packages
return [self.reports[id]['report']['SourcePackage']]
IndexError: list index out of range

Is there some other way for me to get the info you need?

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

Title:
  khubd/usbhid deadlock(?) creates processes in state D

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (Note that the attached logs are not a machine exhibiting the issue)

  I've observed this issue specifically on Dell's PowerEdge R410 with
  its DRAC. I manage quite a few other machines with DRACs and haven't
  seen this issue so it may be limited to the R410. I've seen cases of
  this both with the precise and trusty kernel.

  Basically, what happens is that things that read any info about the
  DRAC's usbhid device will block in an uninterruptible state. A quick
  way to do this is with "cat
  /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This
  means that commands like lspci will block as well. The thing is that
  it doesn't happen every time, but once it happens the first time all
  future reads on the device will block in state D too.

  This is also associated with the following from the kernel (first from a 
precise machine):
  [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197857.716899] usb 5-2: device descriptor read/64, error -71
  [197857.944966] usb 5-2: device descriptor read/64, error -71
  [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197858.285090] usb 5-2: device descriptor read/64, error -71
  [197858.513108] usb 5-2: device descriptor read/64, error -71
  [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.145214] usb 5-2: device not accepting address 2, error -71
  [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.669322] usb 5-2: device not accepting address 2, error -71
  [197859.675357] usb 5-2: USB disconnect, device number 2
  [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
  [198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.551792] khubd   D 880803fe18a0 0   203  2 
0x
  [198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
  [198047.551809]  00013180 00013180 881003f7c800 
880804634800
  [198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

  [198047.551819] Call Trace:
  [198047.551828]  [] schedule+0x29/0x70
  [198047.551833]  [] schedule_preempt_disabled+0xe/0x10
  [198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
  [198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
  [198047.551848]  [] mutex_lock+0x23/0x37
  [198047.551852]  [] usb_disconnect+0x5a/0x210
  [198047.551857]  [] ? usb_control_msg+0xea/0x110
  [198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
  [198047.551864]  [] ? hub_port_status+0xd5/0x120
  [198047.551868]  [] hub_events+0x464/0x8c0
  [198047.551871]  [] ? __schedule+0x38e/0x700
  [198047.551875]  [] hub_thread+0x35/0x150
  [198047.551881]  [] ? __wake_up_sync+0x20/0x20
  [198047.551885]  [] ? hub_events+0x8c0/0x8c0
  [198047.551890]  [] kthread+0xc9/0xe0
  [198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551898]  [] ret_from_fork+0x58/0x90
  [198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
  [198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 
0x
  [198047.573547] Workqueue: events hid_reset [usbhid]
  [198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
  [198047.573555]  00013180 00013180 881003f94800 
8808011f
  [198047.573559]  8808011f9798 ff

[Kernel-packages] [Bug 1557172] [NEW] khubd/usbhid deadlock(?) creates processes in state D

2016-03-14 Thread Mike Gerow

Public bug reported:

(Note that the attached logs are not a machine exhibiting the issue)

I've observed this issue specifically on Dell's PowerEdge R410 with its
DRAC. I manage quite a few other machines with DRACs and haven't seen
this issue so it may be limited to the R410. I've seen cases of this
both with the precise and trusty kernel.

Basically, what happens is that things that read any info about the
DRAC's usbhid device will block in an uninterruptible state. A quick way
to do this is with "cat
/sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This means
that commands like lspci will block as well. The thing is that it
doesn't happen every time, but once it happens the first time all future
reads on the device will block in state D too.

This is also associated with the following from the kernel (first from a 
precise machine):
[197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197857.716899] usb 5-2: device descriptor read/64, error -71
[197857.944966] usb 5-2: device descriptor read/64, error -71
[197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197858.285090] usb 5-2: device descriptor read/64, error -71
[197858.513108] usb 5-2: device descriptor read/64, error -71
[197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197859.145214] usb 5-2: device not accepting address 2, error -71
[197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197859.669322] usb 5-2: device not accepting address 2, error -71
[197859.675357] usb 5-2: USB disconnect, device number 2
[198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
[198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
[198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[198047.551792] khubd   D 880803fe18a0 0   203  2 0x
[198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
[198047.551809]  00013180 00013180 881003f7c800 
880804634800
[198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

[198047.551819] Call Trace:
[198047.551828]  [] schedule+0x29/0x70
[198047.551833]  [] schedule_preempt_disabled+0xe/0x10
[198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
[198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
[198047.551848]  [] mutex_lock+0x23/0x37
[198047.551852]  [] usb_disconnect+0x5a/0x210
[198047.551857]  [] ? usb_control_msg+0xea/0x110
[198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
[198047.551864]  [] ? hub_port_status+0xd5/0x120
[198047.551868]  [] hub_events+0x464/0x8c0
[198047.551871]  [] ? __schedule+0x38e/0x700
[198047.551875]  [] hub_thread+0x35/0x150
[198047.551881]  [] ? __wake_up_sync+0x20/0x20
[198047.551885]  [] ? hub_events+0x8c0/0x8c0
[198047.551890]  [] kthread+0xc9/0xe0
[198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
[198047.551898]  [] ret_from_fork+0x58/0x90
[198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
[198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
[198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
[198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 0x
[198047.573547] Workqueue: events hid_reset [usbhid]
[198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
[198047.573555]  00013180 00013180 881003f94800 
8808011f
[198047.573559]  8808011f9798 8808011f98d8 7fff 
7fff
[198047.573564] Call Trace:
[198047.573579]  [] schedule+0x29/0x70
[198047.573582]  [] schedule_timeout+0x1e5/0x250
[198047.573587]  [] ? wake_affine+0x16d/0x2d0
[198047.573591]  [] wait_for_completion+0xa7/0x160
[198047.573596]  [] ? try_to_wake_up+0x210/0x210
[198047.573602]  [] flush_work+0x29/0x40
[198047.573605]  [] ? start_worker+0x40/0x40
[198047.573609]  [] __cancel_work_timer+0x9c/0x1b0
[198047.573623]  [] cancel_work_sync+0x10/0x20
[198047.573632]  [] hid_cancel_delayed_stuff+0x29/0x30 
[usbhid]
[198047.573640]  [] usbhid_close+0xcc/0x110 [usbhid]
[198047.573650]  [] hidinput_close+0x22/0x30 [hid]
[198047.573659]  [] input_close_device+0x61/0x90
[198047.573663]  [] evdev_cleanup+0xbf/0xd0
[198047.573670]  [] evdev_disconnect+0x36/0x70
[198047.573674]  [] __input_unregister_device+0xc5/0x1a0
[198047.573678]  [] input_unregister_device+0x55/0x80
[198047.573687]  [] hidinput_disconnect+0x95/0xc0 [hid]
[198047.573695]  [] hid_disconnect+0x68/0x70 [hid]
[198047.573708]  [] hid_device_remove+0xd5/0xf0 [hid]
[198047.573720]  [] __device_release_driver+0x7f/0xf0
[198047.573724]  [] device_release_driver+0x2c/0x40
[198047.573728]  [] bus_remove_device+0x104/0x170
[198047.573736]  [] device_del+0x118/0x1a0
[198047.573744]  [] hid_destroy_device+0x30/0x70 [hid]
[198047.573754]  [] usbhid_di

[Kernel-packages] [Bug 1553626] Re: blank console after upgrading to 3.2.0-99

2016-03-13 Thread Mike Kupfer

I don't need a backport, so closing as requested.

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

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

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Invalid

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much
never get a working display manager. (I think it booted okay the
first time after installing the kernel, but that's it.) Usually I
just get a black display. I have also gotten

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I once tried booting in recovery mode. I noticed a message about
modprobe being terminated by signal 9, and I noticed several messages
about modprobe timeouts. But other than that the messages didn't tell
me anything that I could make sense of.

I can ssh into the system. Unfortunately, "apport-bug linux" gets
stuck (it still says "collecting problem information" after 30
minutes), so I'm filing this directly on Launchpad. I can get the
apport configuration information from the 3.2.0-98 kernel (that kernel
works just fine). I can also collect any log files, ps output, etc.
that you'd like. lightdm does seem to be running. The only
suspicious thing I see in the log files is that Xorg.0.log is missing
a bunch of text that it contains when using the -98 kernel.

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

Reinstalling the -99 kernel did not help.
---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1562 F pulseaudio
CasperVersion: 1.367
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
MachineType: ASUSTeK COMPUTER INC. 1015E
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
RelatedPackageVersions:
linux-restricted-modules-4.4.0-10-generic N/A
linux-backports-modules-4.4.0-10-generic N/A
linux-firmware1.156
Tags: xenial
Uname: Linux 4.4.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1015E.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 1015E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1015E.304:bd05/08/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: 1015E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

apport information

** Attachment added: "WifiSyslog.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594537/+files/WifiSyslog.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] Re: blank console after upgrading to 3.2.0-99

apport-collect has been run as requested. And FWIW, the live image
console worked just fine (no need to ssh in to run apport-collect).

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

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594530/+files/Lsusb.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594531/+files/ProcCpuinfo.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594529/+files/Lspci.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594532/+files/ProcInterrupts.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594535/+files/RfKill.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594536/+files/UdevDb.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594533/+files/ProcModules.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] PulseList.txt

apport information

** Attachment added: "PulseList.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594534/+files/PulseList.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594527/+files/IwConfig.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] Re: blank console after upgrading to 3.2.0-99

apport information

** Tags added: apport-collected xenial

** Description changed:

Ubuntu 12.04.5, ASUS model 1015E, x86_64

When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much never
get a working display manager. (I think it booted okay the first time
after installing the kernel, but that's it.) Usually I just get a black
display. I have also gotten

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I can ssh into the system. Unfortunately, "apport-bug linux" gets stuck
(it still says "collecting problem information" after 30 minutes), so
I'm filing this directly on Launchpad. I can get the apport
configuration information from the 3.2.0-98 kernel (that kernel works
just fine). I can also collect any log files, ps output, etc. that
you'd like. lightdm does seem to be running. The only suspicious thing
I see in the log files is that Xorg.0.log is missing a bunch of text
that it contains when using the -98 kernel.

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did not
fix anything.

Reinstalling the -99 kernel did not help.
+ ---
+ ApportVersion: 2.20-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ubuntu 1562 F pulseaudio
+ CasperVersion: 1.367
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
+ MachineType: ASUSTeK COMPUTER INC. 1015E
+ Package: linux (not installed)
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
+ ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
+ RelatedPackageVersions:
+ linux-restricted-modules-4.4.0-10-generic N/A
+ linux-backports-modules-4.4.0-10-generic N/A
+ linux-firmware1.156
+ Tags: xenial
+ Uname: Linux 4.4.0-10-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/08/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1015E.304
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: 1015E
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1015E.304:bd05/08/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.name: 1015E
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594524/+files/AlsaInfo.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

[Kernel-packages] [Bug 1553626] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594526/+files/CurrentDmesg.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"

https://bugs.launchpad.net/bugs/1553626/+attachment/4594528/+files/JournalErrors.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1553626/+attachment/4594525/+files/CRDA.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/1553626

Title:
blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 12.04.5, ASUS model 1015E, x86_64

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
not fix anything.

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

[Kernel-packages] [Bug 1553626] Re: blank console after upgrading to 3.2.0-99

2016-03-05 Thread Mike Kupfer

I booted the -98 kernel, enabled wireless in Network Manager, and then
booted the -99 kernel.  I'm afraid apport-collect still stalls, and I
still see rfkill stuck in D+ state.

So, I can manually attach files from /var/log.  Or I could try running
apport-collect with the -98 kernel running.  Let me know how to proceed.

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

Title:
  blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04.5, ASUS model 1015E, x86_64

  When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much
  never get a working display manager.  (I think it booted okay the
  first time after installing the kernel, but that's it.)  Usually I
  just get a black display.  I have also gotten

  - an almost complete login screen, except the background is wrong
  (uniform purple instead of my wallpaper), and trackpad clicks are
  ignored (but trackpad motion works)

  - stuck at the Ubuntu splash screen

  I once tried booting in recovery mode.  I noticed a message about
  modprobe being terminated by signal 9, and I noticed several messages
  about modprobe timeouts.  But other than that the messages didn't tell
  me anything that I could make sense of.

  I can ssh into the system.  Unfortunately, "apport-bug linux" gets
  stuck (it still says "collecting problem information" after 30
  minutes), so I'm filing this directly on Launchpad.  I can get the
  apport configuration information from the 3.2.0-98 kernel (that kernel
  works just fine).  I can also collect any log files, ps output, etc.
  that you'd like.  lightdm does seem to be running.  The only
  suspicious thing I see in the log files is that Xorg.0.log is missing
  a bunch of text that it contains when using the -98 kernel.

  I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
  not fix anything.

  Reinstalling the -99 kernel did not help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553626/+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 1553626] Re: blank console after upgrading to 3.2.0-99

2016-03-05 Thread Mike Kupfer

I ran "apport-collect 1553626", but it appeared to hang.  (After an
hour, it was still saying "Collecting problem information".)

I poked around a bit while it was running.  Here's some ps output in
case it's useful:

camomile$ ps -t pts/1
  PID TTY  TIME CMD
 1757 pts/100:00:00 bash
 1825 pts/100:00:00 apport-collect
 1830 pts/100:01:08 apport-gtk
 1835 pts/100:00:00 dbus-launch
 2022 pts/100:00:00 rfkill
camomile$ ps u 2022
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
kupfer2022  0.0  0.0   4156   352 pts/1D+   19:43   0:00 rfkill list

I will see if enabling wireless makes things better.

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

Title:
  blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 12.04.5, ASUS model 1015E, x86_64

  When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much
  never get a working display manager.  (I think it booted okay the
  first time after installing the kernel, but that's it.)  Usually I
  just get a black display.  I have also gotten

  - an almost complete login screen, except the background is wrong
  (uniform purple instead of my wallpaper), and trackpad clicks are
  ignored (but trackpad motion works)

  - stuck at the Ubuntu splash screen

  I once tried booting in recovery mode.  I noticed a message about
  modprobe being terminated by signal 9, and I noticed several messages
  about modprobe timeouts.  But other than that the messages didn't tell
  me anything that I could make sense of.

  I can ssh into the system.  Unfortunately, "apport-bug linux" gets
  stuck (it still says "collecting problem information" after 30
  minutes), so I'm filing this directly on Launchpad.  I can get the
  apport configuration information from the 3.2.0-98 kernel (that kernel
  works just fine).  I can also collect any log files, ps output, etc.
  that you'd like.  lightdm does seem to be running.  The only
  suspicious thing I see in the log files is that Xorg.0.log is missing
  a bunch of text that it contains when using the -98 kernel.

  I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
  not fix anything.

  Reinstalling the -99 kernel did not help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553626/+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 1553626] [NEW] blank console after upgrading to 3.2.0-99

2016-03-05 Thread Mike Kupfer

Public bug reported:

Ubuntu 12.04.5, ASUS model 1015E, x86_64

When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much never
get a working display manager.  (I think it booted okay the first time
after installing the kernel, but that's it.)  Usually I just get a black
display.  I have also gotten

- an almost complete login screen, except the background is wrong
(uniform purple instead of my wallpaper), and trackpad clicks are
ignored (but trackpad motion works)

- stuck at the Ubuntu splash screen

I once tried booting in recovery mode.  I noticed a message about
modprobe being terminated by signal 9, and I noticed several messages
about modprobe timeouts.  But other than that the messages didn't tell
me anything that I could make sense of.

I can ssh into the system.  Unfortunately, "apport-bug linux" gets stuck
(it still says "collecting problem information" after 30 minutes), so
I'm filing this directly on Launchpad.  I can get the apport
configuration information from the 3.2.0-98 kernel (that kernel works
just fine).  I can also collect any log files, ps output, etc. that
you'd like.  lightdm does seem to be running.  The only suspicious thing
I see in the log files is that Xorg.0.log is missing a bunch of text
that it contains when using the -98 kernel.

I noticed that I had an out-of-date BIOS, but upgrading the BIOS did not
fix anything.

Reinstalling the -99 kernel did not help.

** Affects: linux (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/1553626

Title:
  blank console after upgrading to 3.2.0-99

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 12.04.5, ASUS model 1015E, x86_64

  When I boot the 3.2.0-99 kernel on my ASUS netbook, I pretty much
  never get a working display manager.  (I think it booted okay the
  first time after installing the kernel, but that's it.)  Usually I
  just get a black display.  I have also gotten

  - an almost complete login screen, except the background is wrong
  (uniform purple instead of my wallpaper), and trackpad clicks are
  ignored (but trackpad motion works)

  - stuck at the Ubuntu splash screen

  I once tried booting in recovery mode.  I noticed a message about
  modprobe being terminated by signal 9, and I noticed several messages
  about modprobe timeouts.  But other than that the messages didn't tell
  me anything that I could make sense of.

  I can ssh into the system.  Unfortunately, "apport-bug linux" gets
  stuck (it still says "collecting problem information" after 30
  minutes), so I'm filing this directly on Launchpad.  I can get the
  apport configuration information from the 3.2.0-98 kernel (that kernel
  works just fine).  I can also collect any log files, ps output, etc.
  that you'd like.  lightdm does seem to be running.  The only
  suspicious thing I see in the log files is that Xorg.0.log is missing
  a bunch of text that it contains when using the -98 kernel.

  I noticed that I had an out-of-date BIOS, but upgrading the BIOS did
  not fix anything.

  Reinstalling the -99 kernel did not help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553626/+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 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

2016-02-24 Thread Mike Vazowski

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

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

Bug description:
  Hi,

  This morning I've updated my Ubuntu 15.10 to kernel 4.2.0.30 and now
  can't enter to the desktop. In fact, the laptop freezes after grub
  screen.

  If start from the recovery, from "upstart" option I get a message like
  "upstart: broken pipe". And I enter to "recovery mode" options  and
  after resume with the normal start the desktop loads but only with
  1024x768 or 800x600

  I've have to start with the previous kernel, the 4.2.0.27. Then all
  works as expected and I log to my desktop as usual.

  Thank you very much.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2638 F pulseaudio
   /dev/snd/controlC1:  albert 2638 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=3ea73c4c-4dc5-4f7f-8c97-d2f477414305
  InstallationDate: Installed on 2016-01-20 (34 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Hewlett-Packard HP G62 Notebook PC
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=e34b1243-4d35-4e1d-ab47-19304b7c369b ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/15/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 62.3D
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548867/+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 1548985] Re: After linux kernel update system won't boot

2016-02-23 Thread Mike Zane

Confirming marcin's bug report as well after it failed starting on a TPM error:
"A TPM error (6) occurred attempting to read a pcr value"
The only way for me to get access was to boot from previous base: 
4.2.0-27-generic

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

Title:
  After linux kernel update system won't boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I try updating packages listed bellow via Software Updater,
  Ubuntu gets stuck on purple screen after restart. No key combination
  seems to do anything. I can login to desktop only via recovery and
  then normal boot option. I'm using Ubuntu 15.10.

  linux-generic 
  installed version 4.2.0.16.18
  available version 4.2.0.30.33

  linux-firmware
  Installed version: 1.149
  Available version: 1.149.3

  linux-headers-generic
  Installed version: 4.2.0.16.18
  Available version: 4.2.0.30.33

  linux-image-generic
  Installed version: 4.2.0.16.18
  Available version: 4.2.0.30.33

  linux-headers-4.2.0-30
  Installed version: None
  Available version: 4.2.0-30.35

  linux-image-extra-4.2.0-30-generic
  Installed version: None
  Available version: 4.2.0-30.35

  linux-libc-dev
  Installed version: 4.2.0-16.19
  Available version: 4.2.0-30.35

  linux-headers-4.2.0-30-generic
  Installed version: None
  Available version: 4.2.0-30.35

  linux-image-4.2.0-30-generic
  Installed version: None
  Available version: 4.2.0-30.35

  I'm not sure if all of them seams to cause the problem.

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

Re: [Kernel-packages] [Bug 1536719] Re: Update bnx2x firmware for Linux 4.4 to 7.12.30.0

RE: the LOCKUP: It takes long enough to kill a zookeeper connection, which
hurts.   It has always happened, but as I've upped the load, it happens
more.  Started with 3.15.  I was able to install the very latest kernel by
force-installing the firmware package.  But the latest kernel won't let me
make a necessary kernel module because I don't have gcc 4.9, needed for
STACKPROTECT.  The latest kernel I've tried is the 3.16.

On Thu, Jan 21, 2016 at 7:29 PM, Tim Gardner 
wrote:

> Hmm, perhaps I was a bit hasty. I read comment #5 and thought networking
> was the root of your issue. At least I've fixed your bnx2x networking
> issue in Xenial. The mainline kernel will not work right wrt bnx2x
> unless you also have the Xenial linux-firmware package installed.
>
> >From your lockup trace, it looks like one CPU is wedged. Does this take
> awhile ? Do older kernels work ? When did this start happening ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1536719
>
> Title:
>   Update bnx2x firmware for Linux 4.4 to 7.12.30.0
>
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux source package in Xenial:
>   Fix Committed
>
> Bug description:
>   Ubuntu 12.04.1 LTS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536719/+subscriptions
>

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

Title:
  Update bnx2x firmware for Linux 4.4 to 7.12.30.0

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

Bug description:
  Ubuntu 12.04.1 LTS

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

Re: [Kernel-packages] [Bug 1536719] Re: Watchdog detected hard LOCKUP watchdog.c:265

I'm a bit confused by the summary change.  Is the LOCKUP issued addressed?
And pardon my ignorance, but is there any chance the fix could be applied
to the whatever is the latest kernel version that does not require a
compiler with stackprotect when making kernel modules?

On Thu, Jan 21, 2016 at 3:49 PM, Tim Gardner 
wrote:

> ** Also affects: linux (Ubuntu Xenial)
>Importance: Medium
>Status: Incomplete
>
> ** Changed in: linux (Ubuntu Xenial)
>Status: Incomplete => Fix Committed
>
> ** Changed in: linux (Ubuntu Xenial)
>  Assignee: (unassigned) => Tim Gardner (timg-tpi)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1536719
>
> Title:
> Watchdog detected hard LOCKUP watchdog.c:265
>
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux source package in Xenial:
>   Fix Committed
>
> Bug description:
>   Ubuntu 12.04.1 LTS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536719/+subscriptions
>

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

Title:
  Update bnx2x firmware for Linux 4.4 to 7.12.30.0

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

Bug description:
  Ubuntu 12.04.1 LTS

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

Re: [Kernel-packages] [Bug 1536719] Re: Watchdog detected hard LOCKUP watchdog.c:265

The issue has existed for all kernel versions that I've tried.
When I try to install from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/,  I get a warning
that the lib/firmware/bnx2x/bnx2x-e2-7.12.30.0.fw for module bnx2x is
missing.   And the NIC won't come up.
Thanks,
--Mike

On Thu, Jan 21, 2016 at 9:01 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.4 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1536719
>
> Title:
> Watchdog detected hard LOCKUP watchdog.c:265
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Ubuntu 12.04.1 LTS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536719/+subscriptions
>

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

Title:
Watchdog detected hard LOCKUP watchdog.c:265

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04.1 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536719/+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 1536719] Re: Watchdog detected hard LOCKUP watchdog.c:265

Cannot run apport-collect 1536719
because the systems can have no internet access.

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

Title:
Watchdog detected hard LOCKUP watchdog.c:265

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04.1 LTS

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

Re: [Kernel-packages] [Bug 1470703] Re: Watchdog detected hard LOCKUP

Hi Christopher,
I submitted the bug per your suggestion:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536719

Thanks,
--Mike

On Wed, Jan 20, 2016 at 1:42 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Mike Thompson, it will help immensely if you filed a new report with the
> Ubuntu repository kernel (not mainline/upstream). Given you don't have
> internet access, one may start a manual report via:
> https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
>
> Please feel free to subscribe me to it.
>
> For more on why this is helpful, please see
> https://wiki.ubuntu.com/ReportingBugs.
>
> ** Attachment removed: "kern.log.1"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470703/+attachment/4552978/+files/kern.log.1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1470703
>
> Title:
>   Watchdog detected hard LOCKUP
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I am using qemu, kvm, pci-stub and sometimes got this message in dmesg.
>   The system looks like the work, no reboots and crashes.
>   But how bad is it?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.16.0-41-generic 3.16.0-41.57~14.04.1
>   ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
>   Uname: Linux 3.16.0-41-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.11
>   Architecture: amd64
>   Date: Thu Jul  2 06:37:12 2015
>   InstallationDate: Installed on 2015-05-08 (54 days ago)
>   InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release
> amd64 (20150218.1)
>   SourcePackage: linux-lts-utopic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470703/+subscriptions
>

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

Title:
  Watchdog detected hard LOCKUP

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using qemu, kvm, pci-stub and sometimes got this message in dmesg. 
  The system looks like the work, no reboots and crashes.
  But how bad is it?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-41-generic 3.16.0-41.57~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Thu Jul  2 06:37:12 2015
  InstallationDate: Installed on 2015-05-08 (54 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470703/+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 1536719] [NEW] Watchdog detected hard LOCKUP watchdog.c:265

Public bug reported:

Ubuntu 12.04.1 LTS

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

** Attachment added: "version, lspci and kern.log entry"
   
https://bugs.launchpad.net/bugs/1536719/+attachment/4554176/+files/Archive.zip

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

Title:
Watchdog detected hard LOCKUP watchdog.c:265

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 12.04.1 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536719/+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 1470703] Re: Watchdog detected hard LOCKUP

2016-01-19 Thread Mike Thompson

I am experiencing the same problem on 3.16.0-34-generic.
I've attached the kern.log output.
The effected systems are not attached to the internet, so I could not use 
apport-collect 

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

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

Title:
  Watchdog detected hard LOCKUP

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using qemu, kvm, pci-stub and sometimes got this message in dmesg. 
  The system looks like the work, no reboots and crashes.
  But how bad is it?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-41-generic 3.16.0-41.57~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Thu Jul  2 06:37:12 2015
  InstallationDate: Installed on 2015-05-08 (54 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470703/+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 1478799] Re: bluetooth not working in 15.10

2016-01-19 Thread Mike Holmes

I tried your solution bsb, it was not the answer for me, the H800
headset microphone remains the only thing not working in my case.

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

Title:
  bluetooth not working in 15.10

Status in Linux:
  Unknown
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 15.10 Wily

  No bluetooth indicator visible.

  I can't activate bluetooth in the bluetooth system-settings.

  Bluetooth mouse not working (I can't pair it).

  syslog:
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Starting SDP server
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: DIS cannot start: GATT 
is disabled
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
deviceinfo plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
proximity plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init time 
plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init alert 
plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
thermometer plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]:  VPN: loaded 
org.freedesktop.NetworkManager.pptp
  Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]:  DNS: loaded 
plugin dnsmasq
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: 
Starting SDP server
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: DIS 
cannot start: GATT is disabled
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init deviceinfo plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init proximity plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init time plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init alert plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init thermometer plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully called 
chroot().
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully dropped 
remaining capabilities.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: No service file found 
in /etc/avahi/services.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Network interface 
enumeration completed.
  Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Avahi mDNS/DNS-SD 
Stack.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Registering HINFO 
record with values 'X86_64'/'LINUX'.
  Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Bluetooth service.

  hciconfig 
  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:15:83:15:A3:0B  ACL MTU: 672:4  SCO MTU: 48:1
DOWN 
RX bytes:445 acl:0 sco:0 events:15 errors:0
TX bytes:63 acl:0 sco:0 commands:15 errors:0

  rfkill list 
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1478799/+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 1533043] Re: AUFS can hang up; Please update to v20160111

2016-01-12 Thread Mike Atlas

For what it's worth, Dockerized containers running common open-source
applications (Cassandra, Mongo, Flynn) have stumbled hard on this - and
of course, it's not just on Ubuntu, but all Linux kernels with
296291cdd: https://bugzilla.kernel.org/show_bug.cgi?id=109971 -

Akihiro has been a champion in tracking down the cause, reproduction of
the problem, a patch, and pushing for a fix in all the right places.
Give this guy a high five or a beer if you know him in person, he's
helping a lot of people out with his efforts.

** Bug watch added: Linux Kernel Bug Tracker #109971
   http://bugzilla.kernel.org/show_bug.cgi?id=109971

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

Title:
  AUFS can hang up; Please update to v20160111

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  AUFS  can hang up (more precisely, produces unkillable processes) with some 
kernels that contain the commit 296291cdd1629c308114504b850dc343eabc278.
  - 14.04LTS:  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=b8702f3cf9c06914476fb3206039131c2c3d8450
  - 15.04: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=6b08592b8acc677d5b9bb7986343fdd6e0ad3303
  - 15.10: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/commit/?id=4d291df30fb7a94d13c6d38addf8d85d38f0111b

  Many docker users have been experiencing this issue:
  https://github.com/docker/docker/issues/18180

  
  The issue has been fixed since AUFS v20160111: 
http://permalink.gmane.org/gmane.linux.file-systems.aufs.user/5345
  So I suggest updating AUFS to v20160111.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533043/+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 1359689] Re: cryptsetup password prompt not shown

2015-12-25 Thread Mike Butash

Wow, I installed a 3.19 kernel today on 14.04, and suddenly found I
couldn't type my disk encryption password.  Then I found it was non-
trivial to actually get into the non-hidden grub menu  as holding shift
did not work apparently from my bios.

Why is this *still* an issue?  Does no one at canonical use disk
encryption?  Can we please finally add testing luks to some sort of
regression tests?

Not exactly what I wanted on my first day of christmas.

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

Title:
  cryptsetup password prompt not shown

Status in xserver-xorg-driver-radeonhd:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Triaged

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1359689/+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 1359689] Re: cryptsetup password prompt not shown

2015-12-25 Thread Mike Butash

Note: I ask about the qa for luks, as this is about the third time in
memory since 8.xx days luks has been suddenly broken with an update.  No
one that tests the kernels seems to use disk encryption or understand it
to ensure this works consistently.

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

Title:
  cryptsetup password prompt not shown

Status in xserver-xorg-driver-radeonhd:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Triaged

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1359689/+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 1451689] Re: 0cf3:3004 Bluetooth driver is not being loaded

2015-12-24 Thread Mike Ellertson

I'm on an MSI Dominator GT72 2QD, and have the wifi working by implementing the 
following bug fix, but bluetooth isn't working.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184

I'm running Ubuntu 15.10, here's my specific version:
$ uname -a
Linux  4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

$ lsusb
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 
4.0

$ dmesg | egrep 'Bluetooth|bluetooth|ath3k|BT'
[9.223764] Bluetooth: Core ver 2.20
[9.223778] Bluetooth: HCI device and connection manager initialized
[9.223781] Bluetooth: HCI socket layer initialized
[9.223783] Bluetooth: L2CAP socket layer initialized
[9.223788] Bluetooth: SCO socket layer initialized
[9.520130] usb 3-1.3: Direct firmware load for ar3k/AthrBT_0x0200.dfu 
failed with error -2
[9.520133] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
[9.520178] Bluetooth: Loading patch file failed
[9.520220] ath3k: probe of 3-1.3:1.0 failed with error -2
[9.520241] usbcore: registered new interface driver ath3k
[   42.186848] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   42.186851] Bluetooth: BNEP filters: protocol multicast
[   42.186854] Bluetooth: BNEP socket layer initialized

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

Title:
  0cf3:3004 Bluetooth driver is not being loaded

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Linux MedSpecPro 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58
  UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  
  [8.411052] usb 3-1.3: Direct firmware load for ar3k/AthrBT_0x0200.dfu 
failed with error -2
  [8.411058] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [8.411060] Bluetooth: Loading patch file failed
  [8.411066] ath3k: probe of 3-1.3:1.0 failed with error -2

  /lib/firmware/ar3k/
  -rw-r--r--  1 root root 55244 nov 24 16:42 AthrBT_0x01020001.dfu
  -rw-r--r--  1 root root 40724 nov 24 16:42 AthrBT_0x01020200.dfu
  -rw-r--r--  1 root root 19164 dec  1 16:16 AthrBT_0x01020201.dfu
  -rw-r--r--  1 root root 36828 nov 24 16:42 AthrBT_0x1102.dfu
  -rw-r--r--  1 root root 40652 nov 24 16:42 AthrBT_0x3101.dfu
  -rw-r--r--  1 root root 31500 dec  1 16:16 AthrBT_0x4102.dfu
  -rw-r--r--  1 root root  1224 nov 24 16:42 ramps_0x01020001_26.dfu
  -rw-r--r--  1 root root  1274 nov 24 16:42 ramps_0x01020200_26.dfu
  -rw-r--r--  1 root root  1204 nov 24 16:42 ramps_0x01020200_40.dfu
  -rw-r--r--  1 root root   264 dec  1 16:16 ramps_0x01020201_26.dfu
  -rw-r--r--  1 root root   264 dec  1 16:16 ramps_0x01020201_40.dfu
  -rw-r--r--  1 root root  1796 nov 24 16:42 ramps_0x1102_40.dfu
  -rw-r--r--  1 root root  1926 nov 24 16:42 ramps_0x3101_40.dfu
  -rw-r--r--  1 root root  1820 dec  1 16:16 ramps_0x4102_40.dfu

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tycho  3531 F pulseaudio
   /dev/snd/controlC0:  tycho  3531 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  5 09:06:53 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-24 (41 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: Micro-Star International Co., Ltd. GS60 2QE
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=885993d1-0564-4a6a-993a-4c02de1855ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H5IMS.10C
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.10C:bd11/07/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GS60 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-St

[Kernel-packages] [Bug 1527748] Re: lts-utopic kernel needs boot-up race condition fix.

2015-12-18 Thread Mike Waychison

Here's the fragment of Oops I have demonstrating the crash.  If I'm
understanding the versioning here, it looks like the issue may now have
been fully addressed by that patch alone?  :(

[0.104000] CR2: 8807b000 CR3: 01c13000 CR4: 001406f0
[0.104000] Stack:
[0.104000]   880796773ea0 8176bc39 
8807965d3140
[0.104000]  8807a1001b00 81098810  

[0.104000]  880796773f48 810915f2 0001 
0001
[0.104000] Call Trace:
[0.104000]  [] ? schedule+0x29/0x70
[0.104000]  [] ? SyS_setgroups+0x180/0x180
[0.104000]  [] kthread+0xd2/0xf0
[0.104000]  [] ? kthread_create_on_node+0x1c0/0x1c0
[0.104000]  [] ret_from_fork+0x58/0x90
[0.104000]  [] ? kthread_create_on_node+0x1c0/0x1c0
[0.104000] Code: 89 fa 48 0f a3 11 19 d2 31 f6 85 d2 40 0f 95 c6 ff d0 4c 
89 e7 e8 62 de 11 00 48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b 
0f 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 
[0.104000] RIP  [] smpboot_thread_fn+0x19f/0x1b0
[0.104000]  RSP 
[0.104028] ---[ end trace b59b90c026f24b92 ]---
[0.104734] [ cut here ]
[0.105486] kernel BUG at 
/build/linux-lts-utopic-p81gRk/linux-lts-utopic-3.16.0/kernel/smpboot.c:134!
[0.106799] invalid opcode:  [#2] SMP 
[0.107528] Modules linked in:
[0.108000] CPU: 0 PID: 29 Comm: ksoftirqd/1 Tainted: G  D   
3.16.0-55-generic #74~14.04.1-Ubuntu
[0.108000] Hardware name: Google Google, BIOS Google 01/01/2011
[0.108000] task: 8807966f7010 ti: 880796778000 task.ti: 
880796778000
[0.108000] RIP: 0010:[]  [] 
smpboot_thread_fn+0x19f/0x1b0
[0.108000] RSP: :88079677be88  EFLAGS: 00010202
[0.108000] RAX:  RBX: 8807966f7010 RCX: 
[0.108000] RDX: 88079677bfd8 RSI: 8807966f7010 RDI: 0001
[0.108000] RBP: 88079677bec8 R08: 880796778000 R09: 0246
[0.108000] R10: 8106b17c R11: ea001e59d800 R12: 8807a1001b20
[0.108000] R13: 81c40d20 R14: 8807966f7010 R15: 8807966f7010
[0.108000] FS:  () GS:8807bfc0() 
knlGS:
[0.108000] CS:  0010 DS:  ES:  CR0: 80050033
[0.108000] CR2: 8807b000 CR3: 01c13000 CR4: 001406f0
[0.108000] Stack:
[0.108000]   88079677bea0 8176bc39 
8807965d3140
[0.108000]  8807a1001b20 81098810  

[0.108000]  88079677bf48 810915f2 0001 
0001
[0.108000] Call Trace:
[0.108000]  [] ? schedule+0x29/0x70
[0.108000]  [] ? SyS_setgroups+0x180/0x180
[0.108000]  [] kthread+0xd2/0xf0
[0.108000]  [] ? kthread_create_on_node+0x1c0/0x1c0

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

Title:
  lts-utopic kernel needs boot-up race condition fix.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The underlying kernel bug was originally reported and fixed here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609

  The bug was fixed confirmed not present in the original trusty kernel
  and has been fixed in vivid and wily, but was not addressed in utopic
  as it has EOL.

  If my understanding is correct, while Utopic has EOL, the lts-utopic
  hwe kernel is expected to be supported until the final Trusty release
  (14.04.05) next summer.  Can we have the original kernel issue also
  addressed in lts-utopic (assuming it hasn't been already?).  We are
  seeing users running this kernel on trusty systems and they still
  appear to be affected.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527748/+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 1527748] Re: lts-utopic kernel needs boot-up race condition fix.

2015-12-18 Thread Mike Waychison

*not have

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

Title:
  lts-utopic kernel needs boot-up race condition fix.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The underlying kernel bug was originally reported and fixed here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609

  The bug was fixed confirmed not present in the original trusty kernel
  and has been fixed in vivid and wily, but was not addressed in utopic
  as it has EOL.

  If my understanding is correct, while Utopic has EOL, the lts-utopic
  hwe kernel is expected to be supported until the final Trusty release
  (14.04.05) next summer.  Can we have the original kernel issue also
  addressed in lts-utopic (assuming it hasn't been already?).  We are
  seeing users running this kernel on trusty systems and they still
  appear to be affected.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527748/+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 1527748] [NEW] lts-utopic kernel needs boot-up race condition fix.

2015-12-18 Thread Mike Waychison

Public bug reported:

The underlying kernel bug was originally reported and fixed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609

The bug was fixed confirmed not present in the original trusty kernel
and has been fixed in vivid and wily, but was not addressed in utopic as
it has EOL.

If my understanding is correct, while Utopic has EOL, the lts-utopic hwe
kernel is expected to be supported until the final Trusty release
(14.04.05) next summer.  Can we have the original kernel issue also
addressed in lts-utopic (assuming it hasn't been already?).  We are
seeing users running this kernel on trusty systems and they still appear
to be affected.

Thanks!

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


** Tags: utopic

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

Title:
  lts-utopic kernel needs boot-up race condition fix.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The underlying kernel bug was originally reported and fixed here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609

  The bug was fixed confirmed not present in the original trusty kernel
  and has been fixed in vivid and wily, but was not addressed in utopic
  as it has EOL.

  If my understanding is correct, while Utopic has EOL, the lts-utopic
  hwe kernel is expected to be supported until the final Trusty release
  (14.04.05) next summer.  Can we have the original kernel issue also
  addressed in lts-utopic (assuming it hasn't been already?).  We are
  seeing users running this kernel on trusty systems and they still
  appear to be affected.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527748/+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 1524069] Re: [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial KVM: updating Trusty guest from 3.13.0-68 t

2015-12-16 Thread Mike Pontillo

@Serge, A workaround for me is to use "hypervisor default" in  virt-
manager. I'm not sure what the equivalent is in virt-install, but maybe
using --cpu=host-model-only would be a workaround?

>From the man page:

   Expose the host CPUs configuration to the guest. This enables 
the guest to take advantage of many
   of the host CPUs features (better performance), but may cause 
issues if migrating the guest to a
   host without an identical CPU.

   --cpu host-model-only
   Expose the nearest host CPU model configuration to the guest.  
It is the best CPU which can be
   used for a guest on any of the hosts.

   Use --cpu=? to see a list of all available sub options. Complete 
details at
   

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

Title:
  [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in
  raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial
  KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel
  exception]

Status in kvm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The symptom I saw was this (note the segfault, and apt-get upgrade
  hangs after this):

  Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic
  Segmentation fault
  done
  Setting up linux-firmware (1.127.19) ...
  Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic

  In dmesg, I saw a corresponding kernel stack trace:

  [  522.649091] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  522.654031] JFS: nTxBlock = 8192, nTxLock = 65536
  [  522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE].
  [  522.672519] QNX4 filesystem 0.2.3 registered.
  [  522.677257] xor: measuring software checksum speed
  [  522.715613]prefetch64-sse: 17306.000 MB/sec
  [  522.755589]generic_sse: 16039.000 MB/sec
  [  522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec)
  [  522.823619] raid6: sse2x1   10481 MB/s
  [  522.891614] raid6: sse2x2   13303 MB/s
  [  522.959616] raid6: sse2x4   15209 MB/s
  [  522.963634] invalid opcode:  [#1] SMP 
  [  522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel 
snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer 
aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm 
soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse
  [  522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic

[Kernel-packages] [Bug 1524069] Re: [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial KVM: updating Trusty guest from 3.13.0-68 t

2015-12-09 Thread Mike Pontillo

On my Trusty VM with "[x] Copy host CPU configuration" checked in virt-
manager, running 'sudo modprobe -r raid6_pq && sudo modprobe raid6_pq'
is enough to reproduce the kernel exception in dmesg (though I didn't
see it print "Segmentation Fault", so that may be somewhat of a red
herring).

Here's /proc/cpuinfo on the guest:
http://paste.ubuntu.com/13868715/

And here's /proc/cpuinfo on the hypervisor host:
http://paste.ubuntu.com/13868744/

I have a separate issue (which I have not filed, because I haven't
triaged, and am not sure I can reproduce yet) that was blocking me from
creating a Xenial guest, but I can try again shortly.

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

Title:
  [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in
  raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial
  KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel
  exception]

Status in kvm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The symptom I saw was this (note the segfault, and apt-get upgrade
  hangs after this):

  Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic
  Segmentation fault
  done
  Setting up linux-firmware (1.127.19) ...
  Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic

  In dmesg, I saw a corresponding kernel stack trace:

  [  522.649091] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  522.654031] JFS: nTxBlock = 8192, nTxLock = 65536
  [  522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE].
  [  522.672519] QNX4 filesystem 0.2.3 registered.
  [  522.677257] xor: measuring software checksum speed
  [  522.715613]prefetch64-sse: 17306.000 MB/sec
  [  522.755589]generic_sse: 16039.000 MB/sec
  [  522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec)
  [  522.823619] raid6: sse2x1   10481 MB/s
  [  522.891614] raid6: sse2x2   13303 MB/s
  [  522.959616] raid6: sse2x4   15209 MB/s
  [  522.963634] invalid opcode:  [#1] SMP 
  [  522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel 
snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer 
aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm 
soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse
  [  522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic 
#111-Ubuntu
  [  522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 
8800

[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception

I just tried again with two logical CPUs and the core set to "Westmere"
(I think that was the default), and didn't see the bug. So this seems
related specifically to "[x] Copy host CPU configuration" being checked.
Here's the /proc/cpuinfo from the "virtual Westmere" where it works:

http://paste.ubuntu.com/13836572/

** Also affects: kvm (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/1524069

Title:
  Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes
  kernel exception

Status in kvm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The symptom I saw was this (note the segfault, and apt-get upgrade
  hangs after this):

  Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic
  Segmentation fault
  done
  Setting up linux-firmware (1.127.19) ...
  Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic

  In dmesg, I saw a corresponding kernel stack trace:

  [  522.649091] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  522.654031] JFS: nTxBlock = 8192, nTxLock = 65536
  [  522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE].
  [  522.672519] QNX4 filesystem 0.2.3 registered.
  [  522.677257] xor: measuring software checksum speed
  [  522.715613]prefetch64-sse: 17306.000 MB/sec
  [  522.755589]generic_sse: 16039.000 MB/sec
  [  522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec)
  [  522.823619] raid6: sse2x1   10481 MB/s
  [  522.891614] raid6: sse2x2   13303 MB/s
  [  522.959616] raid6: sse2x4   15209 MB/s
  [  522.963634] invalid opcode:  [#1] SMP 
  [  522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel 
snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer 
aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm 
soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse
  [  522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic 
#111-Ubuntu
  [  522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 
88005dec6000
  [  522.963759] RIP: 0010:[]  [] 
raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq]
  [  522.963767] RSP: 0018:88005dec7c40  EFLAGS: 00010246
  [  522.963771] RAX:  RBX: 88005dec7c88 RCX: 
880059363000
  [  522.963774] RDX:  RSI: 0080 RDI: 
0012
  [  522.963778] RBP: 88005dec7c70 R08:

[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception

For what it's worth, unchecking "[ ] Copy host CPU configuration" in
virt-manager and selecting "Hypervisor default" for the CPU is a
workaround. (/proc/cpuinfo reports "QEMU Virtual CPU version 2.4.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/1524069

Title:
  Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes
  kernel exception

Status in linux package in Ubuntu:
  New

Bug description:
  The symptom I saw was this (note the segfault, and apt-get upgrade
  hangs after this):

  Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic
  Segmentation fault
  done
  Setting up linux-firmware (1.127.19) ...
  Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic

  In dmesg, I saw a corresponding kernel stack trace:

  [  522.649091] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  522.654031] JFS: nTxBlock = 8192, nTxLock = 65536
  [  522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE].
  [  522.672519] QNX4 filesystem 0.2.3 registered.
  [  522.677257] xor: measuring software checksum speed
  [  522.715613]prefetch64-sse: 17306.000 MB/sec
  [  522.755589]generic_sse: 16039.000 MB/sec
  [  522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec)
  [  522.823619] raid6: sse2x1   10481 MB/s
  [  522.891614] raid6: sse2x2   13303 MB/s
  [  522.959616] raid6: sse2x4   15209 MB/s
  [  522.963634] invalid opcode:  [#1] SMP 
  [  522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel 
snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer 
aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm 
soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse
  [  522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic 
#111-Ubuntu
  [  522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 
88005dec6000
  [  522.963759] RIP: 0010:[]  [] 
raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq]
  [  522.963767] RSP: 0018:88005dec7c40  EFLAGS: 00010246
  [  522.963771] RAX:  RBX: 88005dec7c88 RCX: 
880059363000
  [  522.963774] RDX:  RSI: 0080 RDI: 
0012
  [  522.963778] RBP: 88005dec7c70 R08: 0086 R09: 
025f
  [  522.963781] R10:  R11: 88005dec79ae R12: 
1000
  [  522.963785] R13: 880043a42000 R14: 880043a43000 R15: 
0012
  [  522.963789] FS:  7

[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception

Also, the hypervisor's /proc/cpuinfo reports the following CPU
configuration (8 cores of the same):

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
stepping: 3
microcode   : 0x1e
cpu MHz : 2500.097
cache size  : 6144 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes 
xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi 
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid 
xsaveopt
bugs:
bogomips: 4988.49
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

And the hypervisor's kernel is version 4.2.0-19-generic.

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

Title:
  Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes
  kernel exception

Status in linux package in Ubuntu:
  New

Bug description:
  The symptom I saw was this (note the segfault, and apt-get upgrade
  hangs after this):

  Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic
  Segmentation fault
  done
  Setting up linux-firmware (1.127.19) ...
  Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic

  In dmesg, I saw a corresponding kernel stack trace:

  [  522.649091] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  522.654031] JFS: nTxBlock = 8192, nTxLock = 65536
  [  522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE].
  [  522.672519] QNX4 filesystem 0.2.3 registered.
  [  522.677257] xor: measuring software checksum speed
  [  522.715613]prefetch64-sse: 17306.000 MB/sec
  [  522.755589]generic_sse: 16039.000 MB/sec
  [  522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec)
  [  522.823619] raid6: sse2x1   10481 MB/s
  [  522.891614] raid6: sse2x2   13303 MB/s
  [  522.959616] raid6: sse2x4   15209 MB/s
  [  522.963634] invalid opcode:  [#1] SMP 
  [  522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel 
snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_pag

[Kernel-packages] [Bug 1524069] [NEW] Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception