[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 33, failed: 1

[Brad Figg]

tests ran:  33, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-18_04-06-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632844] dwalin (i386) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/dwalin__3.13.0-99.146__2016-10-18_04-43-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 18, failed: 1

[Brad Figg]

tests ran:  18, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-18_04-07-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632844] onza (i386) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-18_04-19-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] dwalin (amd64) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/dwalin__3.13.0-99.146__2016-10-18_04-23-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 5, failed: 1

[Brad Figg]

tests ran:   5, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/ms10-34-mcdivittB0-kernel__3.13.0-99.146__2016-10-18_04-24-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] onibi (i386) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onibi__3.13.0-99.146__2016-10-18_04-16-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1614209] Re: 16.04 LTS hangs on installer when running nested virtualization on 16.04 host.

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  16.04 LTS hangs on installer when running nested virtualization on
  16.04 host.

Status in linux package in Ubuntu:
  Expired

Bug description:

  Physical host running 16.04 LTS on amd64 (i7):

  Linux host 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC
  2016 x86_64 x86_64 x86_64 GNU/Linux

  On it I'm running an am64 16.04 LTS VM:

  Linux vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016
  x86_64 x86_64 x86_64 GNU/Linux

  I have nested virtualization enabled :

  vm1$ cat /sys/module/kvm_intel/parameters/nested
  Y

  When I try and install vm2 (tried both 16.04.1 i386 and amd64), the
  installer hangs on first menu, at language selection. qemu-kvm goes up
  to 100% cpu, and the hangs, have to virsh destroy/kill the KVM
  process.

  Other info on vm1:

  vm1$ cat /etc/modprobe.d/qemu-system-x86.conf:

  options kvm_intel nested=1

  
  Version of libvirt-bin & kvm:

  on host1:

  libvirt-bin:
Installed: 1.3.1-1ubuntu10.1
Candidate: 1.3.1-1ubuntu10.1
  qemu-kvm:
Installed: 1:2.5+dfsg-5ubuntu10.4
Candidate: 1:2.5+dfsg-5ubuntu10.4

  on vm1:

  libvirt-bin:
Installed: 1.3.1-1ubuntu10.1
Candidate: 1.3.1-1ubuntu10.1
  qemu-kvm:
Installed: 1:2.5+dfsg-5ubuntu10.4
Candidate: 1:2.5+dfsg-5ubuntu10.4
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 17 20:41 seq
   crw-rw 1 root audio 116, 33 Aug 17 20:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/ganeti-swap
  InstallationDate: Installed on 2016-08-16 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ganeti-root ro
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-trusty
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614209/+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 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 33, failed: 1

[Brad Figg]

tests ran:  33, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-18_03-27-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632918] s2lp4 (s390x.LPAR) - tests ran: 18, failed: 1

[Brad Figg]

tests ran:  18, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-18_03-36-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632918] kernel02 (s390x.zVM) - tests ran: 18, failed: 1

[Brad Figg]

tests ran:  18, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-18_03-36-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1633839] Re: No symbol table. Press any key to continue

[Michael]

I also upgraded in place.

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

Title:
  No symbol table. Press any key to continue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+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 1632844] onza (amd64) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-18_03-55-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] onibi (amd64) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onibi__3.13.0-99.146__2016-10-18_03-54-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1634338] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1634338

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Key  board types specific letters

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The bug gets triggered when the left shift is held down and an arrow
  key is pressed. then holding the shift outputs a number based on what
  arrow key was held. Left key produces 4, down key produces 2 and right
  key produces 6 and up key produces 8 every time shift key (left shift
  key) is pressed again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634338/+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 1634338] [NEW] Key board types specific letters

[Behnam Saeedi]

Public bug reported:

The bug gets triggered when the left shift is held down and an arrow key
is pressed. then holding the shift outputs a number based on what arrow
key was held. Left key produces 4, down key produces 2 and right key
produces 6 and up key produces 8 every time shift key (left shift key)
is pressed again.

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

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

Title:
  Key  board types specific letters

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The bug gets triggered when the left shift is held down and an arrow
  key is pressed. then holding the shift outputs a number based on what
  arrow key was held. Left key produces 4, down key produces 2 and right
  key produces 6 and up key produces 8 every time shift key (left shift
  key) is pressed again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634338/+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 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[cfz]

seems disabling the thermald.service is a walk around
i'm using
4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 x86_64 
x86_64 GNU/Linux

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-raspi2 source package in Yakkety:
  Fix Released

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1627198/+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 1634327] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  error lines on turn of or boot on, also brightness control doesnt
  work, also autoresume after opening the lid is not working staying in
  black.

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  
  Ubuntu 4.4.0-43.63-generic 4.4.21


  00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM 
Registers [8086:1904] (rev 08)
Subsystem: ASUSTeK Computer Inc. Skylake Host Bridge/DRAM Registers 
[1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 
[8086:1916] (rev 07) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c3d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

  00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 08)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 
xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP USB 3.0 xHCI 
Controller [1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP CSME HECI [1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
 

[Kernel-packages] [Bug 1634327] [NEW] error lines on turn of or boot on, also brightness control doesnt work, also autoresume after opening the lid is not working staying in black.

[Yefferson Alexander Sierra Pineda]

Public bug reported:


Ubuntu 4.4.0-43.63-generic 4.4.21


00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM 
Registers [8086:1904] (rev 08)
Subsystem: ASUSTeK Computer Inc. Skylake Host Bridge/DRAM Registers 
[1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 
[8086:1916] (rev 07) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c3d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 08)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP USB 3.0 xHCI 
Controller [1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP CSME HECI [1043:1c3d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x4, ASPM not supported, 
Exit Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

[Kernel-packages] [Bug 1634325] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Lenovo X250 failes to suspend after being docked

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo Thinkpad X250 and the ThinkPad Ultra Dock docking
  station which is connected to two Lenovo monitors via DisplayPort.
  Docking works fine but if I remove the computer from the dock and try
  to suspend, the computer locks up (screen freezes no keyboard commands
  work) and I have to hard reboot. The computer works fine after
  removing from the dock except for this suspend issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-43-generic 4.4.0-43.63
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moorepants   2278 F pulseaudio
   /dev/snd/controlC0:  moorepants   2278 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 17 18:46:24 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0001-992b-4a3e-a93f-f6ace66eec1d
  InstallationDate: Installed on 2015-11-14 (339 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=180cbbee-84f0-4f5d-8f67-ab39fe37099a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (178 days ago)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634325/+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 1634325] [NEW] Lenovo X250 failes to suspend after being docked

[Jason Moore]

Public bug reported:

I have a Lenovo Thinkpad X250 and the ThinkPad Ultra Dock docking
station which is connected to two Lenovo monitors via DisplayPort.
Docking works fine but if I remove the computer from the dock and try to
suspend, the computer locks up (screen freezes no keyboard commands
work) and I have to hard reboot. The computer works fine after removing
from the dock except for this suspend issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-43-generic 4.4.0-43.63
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  moorepants   2278 F pulseaudio
 /dev/snd/controlC0:  moorepants   2278 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 17 18:46:24 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0001-992b-4a3e-a93f-f6ace66eec1d
InstallationDate: Installed on 2015-11-14 (339 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20CMCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=180cbbee-84f0-4f5d-8f67-ab39fe37099a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-43-generic N/A
 linux-backports-modules-4.4.0-43-generic  N/A
 linux-firmware1.157.4
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-22 (178 days ago)
dmi.bios.date: 06/19/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET36W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CMCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CMCTO1WW
dmi.product.version: ThinkPad X250
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  Lenovo X250 failes to suspend after being docked

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X250 and the ThinkPad Ultra Dock docking
  station which is connected to two Lenovo monitors via DisplayPort.
  Docking works fine but if I remove the computer from the dock and try
  to suspend, the computer locks up (screen freezes no keyboard commands
  work) and I have to hard reboot. The computer works fine after
  removing from the dock except for this suspend issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-43-generic 4.4.0-43.63
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moorepants   2278 F pulseaudio
   /dev/snd/controlC0:  moorepants   2278 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 17 18:46:24 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0001-992b-4a3e-a93f-f6ace66eec1d
  InstallationDate: Installed on 2015-11-14 (339 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=180cbbee-84f0-4f5d-8f67-ab39fe37099a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (178 days ago)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1634315] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  usb mouse pointer not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB mouse pointer not working when I ugraded my system from 16.04 to
  16.10, however if I type following two commands in terminal one after
  other, it works for that session but stops at restart, repeat the
  procedure it works command are sudo rmmod usbhid ... sudo modprobe
  usbhid, please help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunil  2104 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 18 06:19:57 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cb35bda9-ebc7-42a2-acf0-a49a5cbf5c36
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-09-25 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: FUJITSU LIFEBOOK LH532
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=0467030c-3a59-4a54-a99e-4d7d9e9459e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   06:20:14.226: The udisks-daemon is running (name-owner :1.113).
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (2 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNBB1E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd04/12/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634315/+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 1634315] [NEW] usb mouse pointer not working

[Sunil Salkar]

Public bug reported:

USB mouse pointer not working when I ugraded my system from 16.04 to
16.10, however if I type following two commands in terminal one after
other, it works for that session but stops at restart, repeat the
procedure it works command are sudo rmmod usbhid ... sudo modprobe
usbhid, please help

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-22-generic 4.8.0-22.24
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sunil  2104 F pulseaudio
CurrentDesktop: Unity
Date: Tue Oct 18 06:19:57 2016
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=cb35bda9-ebc7-42a2-acf0-a49a5cbf5c36
HotplugNewDevices:
 
HotplugNewMounts:
 
InstallationDate: Installed on 2016-09-25 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: FUJITSU LIFEBOOK LH532
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=0467030c-3a59-4a54-a99e-4d7d9e9459e7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic  N/A
 linux-firmware1.161
SourcePackage: linux
Symptom: storage
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 06:20:14.226: The udisks-daemon is running (name-owner :1.113).
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (2 days ago)
dmi.bios.date: 04/12/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.08
dmi.board.name: FJNBB1E
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd04/12/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK LH532
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-bug yakkety

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

Title:
  usb mouse pointer not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB mouse pointer not working when I ugraded my system from 16.04 to
  16.10, however if I type following two commands in terminal one after
  other, it works for that session but stops at restart, repeat the
  procedure it works command are sudo rmmod usbhid ... sudo modprobe
  usbhid, please help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunil  2104 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 18 06:19:57 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cb35bda9-ebc7-42a2-acf0-a49a5cbf5c36
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-09-25 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: FUJITSU LIFEBOOK LH532
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=0467030c-3a59-4a54-a99e-4d7d9e9459e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   06:20:14.226: The udisks-daemon is running (name-owner :1.113).
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (2 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNBB1E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd04/12/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634315/+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 1632801] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-112.154/onza__3.2.0-112.154__2016-10-17_23-17-00/results-index.html

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

Title:
  linux: 3.2.0-112.154 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-112.154 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632801/+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 1634271] Re: arm64: kprobes disabled

[dann frazier]

** Description changed:

  [Impact]
- kprobes are not available on arm64, a useful debug feature available on all 
other supported Ubuntu architectures. I failed to catch this when I reviewed 
the yakkety config because I was just looking for regressions vs. enabling new 
features (arm64/kprobes is new in 4.8).
+ kprobes is currently enabled for all Ubuntu architectures except arm64. This 
excludes a useful debug feature, which is required by certain userspace 
provided by Ubuntu, such as perf's probe command. I failed to notice this in my 
yakkety config review because it is a new feature in v4.8.
  
  [Test Case]
- sudo perf probe schedule
- sudo perf record -e probe:schedule -aR sleep 1
+ = Failure case =
+ ubuntu@arm64:~$ sudo perf probe schedule
+ kprobe_events file does not exist - please rebuild kernel with 
CONFIG_KPROBE_EVENTS.
+   Error: Failed to add events.
+ 
+ = Success case =
+ ubuntu@arm64:~$ sudo perf probe schedule
+ Added new event:
+   probe:schedule   (on schedule)
+ 
+ You can now use it in all perf tools, such as:
+ 
+ perf record -e probe:schedule -aR sleep 1
+ 
+ ubuntu@arm64:~$ sudo perf record -e probe:schedule -aR sleep 1
+ [ perf record: Woken up 1 times to write data ]
+ [ perf record: Captured and wrote 0.185 MB perf.data (61 samples) ]
  
  [Regression Risk]
  The proposed fix enables a config for an already-upstream feature, so 
regressions will have upstream support. The config change mostly results in 
building new code vs. modifying existing code. The notable exception is that 
arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - 
but only in the case that this newly enabled feature is being used (if 
kprobe_running()).

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

Title:
  arm64: kprobes disabled

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  kprobes is currently enabled for all Ubuntu architectures except arm64. This 
excludes a useful debug feature, which is required by certain userspace 
provided by Ubuntu, such as perf's probe command. I failed to notice this in my 
yakkety config review because it is a new feature in v4.8.

  [Test Case]
  = Failure case =
  ubuntu@arm64:~$ sudo perf probe schedule
  kprobe_events file does not exist - please rebuild kernel with 
CONFIG_KPROBE_EVENTS.
Error: Failed to add events.

  = Success case =
  ubuntu@arm64:~$ sudo perf probe schedule
  Added new event:
probe:schedule   (on schedule)

  You can now use it in all perf tools, such as:

  perf record -e probe:schedule -aR sleep 1

  ubuntu@arm64:~$ sudo perf record -e probe:schedule -aR sleep 1
  [ perf record: Woken up 1 times to write data ]
  [ perf record: Captured and wrote 0.185 MB perf.data (61 samples) ]

  [Regression Risk]
  The proposed fix enables a config for an already-upstream feature, so 
regressions will have upstream support. The config change mostly results in 
building new code vs. modifying existing code. The notable exception is that 
arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - 
but only in the case that this newly enabled feature is being used (if 
kprobe_running()).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634271/+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 1632801] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-112.154/onza__3.2.0-112.154__2016-10-17_22-56-00/results-index.html

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

Title:
  linux: 3.2.0-112.154 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-112.154 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632801/+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 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: iptables (Ubuntu)
   Status: New => Confirmed

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1556419/+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 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[Jared Fernandez]

** Tags added: yakkety

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1556419/+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 1626437] Re: black screen after log in (desktop does not load)

[hasimir no]

Hi. I found out how i can reproduce the error: bei deleting the .log files
from /var/log/. So there is still the question why these files disappear
accidentally from time to time...

Am 03.10.2016 10:35 nachm. schrieb "Joseph Salisbury" <
joseph.salisb...@canonical.com>:

> 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.8 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.8
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1626437
>
> Title:
>   black screen after log in (desktop does not load)
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   system: linux mint 18 cinnamon 3.0.7+sarah 64-bit kernel version:
>   4.4.0.38, hw: intel core i5-3337u, 8gb ram, 120 gb flash drive, radeon
>   hd 7500m/7600m
>
>   the screen remains black after i log in to my account. this does not
> happen every time i log in but often. the linux is installed on an
> encrypted flash drive.
>   ---
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  homer  1657 F pulseaudio
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Ubuntu 16.04
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=74d5cb60-486b-47e5-a0fc-2b8aa637d00d
>   InstallationDate: Installed on 2016-08-16 (36 days ago)
>   InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
>   MachineType: Dell Inc. Inspiron 5521
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=de_DE.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic
> root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-38-generic N/A
>linux-backports-modules-4.4.0-38-generic  N/A
>linux-firmware1.157.1
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: yes
> Hard blocked: yes
>   Tags:  sarah sarah
>   Uname: Linux 4.4.0-38-generic x86_64
>   UnreportableReason: Der Bericht gehört zu einem nicht installierten
> Paket.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: False
>   dmi.bios.date: 07/31/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A14
>   dmi.board.name: 0CH6TM
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A14
>   dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:
> pnInspiron5521:pvrA14:rvnDellInc.:rn0CH6TM:rvrA00:cvnDellInc.:ct8:cvrA14:
>   dmi.product.name: Inspiron 5521
>   dmi.product.version: A14
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1626437/+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/1626437

Title:
  black screen after log in (desktop does not load)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  system: linux mint 18 cinnamon 3.0.7+sarah 64-bit kernel version:
  4.4.0.38, hw: intel core i5-3337u, 8gb ram, 120 gb flash drive, radeon
  hd 7500m/7600m

  the screen remains black after i log in to my account. this does not happen 
every time i log in but often. the linux is installed on an encrypted flash 
drive.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  homer  1657 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=74d5cb60-486b-47e5-a0fc-2b8aa637d00d
  InstallationDate: Installed on 2016-08-16 (36 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: Dell Inc. Inspiron 5521
  Package: linux (not installed)
  ProcEnviron:
   

[Kernel-packages] [Bug 1632844] onza (i386) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-17_21-39-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] onibi (i386) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onibi__3.13.0-99.146__2016-10-17_21-02-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1633839] Re: No symbol table. Press any key to continue

[Alex N.]

** Description changed:

- Ubuntu 16.10. shows "No symbol table. Press any key to continue" after
- Kernel boot and before login screen. After pressing a key the boot
- process continues and login screen appears.
+ Ubuntu 16.10. shows "error: no symbol table. Press any key to
+ continue..." after Kernel boot and before login screen. After pressing a
+ key or waiting a few seconds, the boot process continues and login
+ screen appears.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

Title:
  No symbol table. Press any key to continue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+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 1634271] [NEW] arm64: kprobes disabled

[dann frazier]

Public bug reported:

[Impact]
kprobes are not available on arm64, a useful debug feature available on all 
other supported Ubuntu architectures. I failed to catch this when I reviewed 
the yakkety config because I was just looking for regressions vs. enabling new 
features (arm64/kprobes is new in 4.8).

[Test Case]
sudo perf probe schedule
sudo perf record -e probe:schedule -aR sleep 1

[Regression Risk]
The proposed fix enables a config for an already-upstream feature, so 
regressions will have upstream support. The config change mostly results in 
building new code vs. modifying existing code. The notable exception is that 
arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - 
but only in the case that this newly enabled feature is being used (if 
kprobe_running()).

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: dann frazier (dannf)
 Status: In Progress

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

Title:
  arm64: kprobes disabled

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  kprobes are not available on arm64, a useful debug feature available on all 
other supported Ubuntu architectures. I failed to catch this when I reviewed 
the yakkety config because I was just looking for regressions vs. enabling new 
features (arm64/kprobes is new in 4.8).

  [Test Case]
  sudo perf probe schedule
  sudo perf record -e probe:schedule -aR sleep 1

  [Regression Risk]
  The proposed fix enables a config for an already-upstream feature, so 
regressions will have upstream support. The config change mostly results in 
building new code vs. modifying existing code. The notable exception is that 
arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - 
but only in the case that this newly enabled feature is being used (if 
kprobe_running()).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634271/+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 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

[vmc]

*** This bug is a duplicate of bug 1629714 ***
https://bugs.launchpad.net/bugs/1629714

** This bug has been marked a duplicate of bug 1629714
   scsi host6: runtime PM trying to activate child device host6 but parent 
(3-1:1.0) is not active

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

Title:
  scsi host6: runtime PM trying to activate child device host6 but
  parent (3-3:1.0) is not active

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [  420.107609] scsi host6: runtime PM trying to activate child device
  host6 but parent (3-3:1.0) is not active

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-19-lowlatency 4.8.0-19.21
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2728 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2728 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  6 13:16:46 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (438 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-19-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-19-lowlatency N/A
   linux-backports-modules-4.8.0-19-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631058/+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 1632844] onza (amd64) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-17_20-23-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10

[Joseph Salisbury]

I built a test kernel with the following commit, that is now in v4.9-rc1:
a9f61ca Drivers: hv: avoid vfree() on crash


Can you test this kernel and see if it resolves this bug?  It can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1400319/yakkety/

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

Title:
  [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04,
  and 15.10

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  While testing the final build of 14.10 32bit we found that kernel
  panic cannot be activated for an installation on a Hyper-V VM.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 R2
  VM: Ubuntu 14.10 32bit

  Kdump is enabled in the config file at /etc/default/kdump-tools

  Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m
  | 384M-:256M

  VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this
  in combination with the values for crashkernel.

  Trying to start the kdump service:
  root@ubuntu1410i386:~# /etc/init.d/kdump-tools start
  Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
  locate_hole failed
  * failed to load kdump kernel
  ---

  root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded
  0

  
  If the conversion from hex to dec is right, the mentioned memory mapping of 
0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then 
related to the RAM allocation nor the crashkernel value used.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6
  InstallationDate: Installed on 2014-10-31 (37 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release i386 
(20141022.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on 
eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3)
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 
10.184.232.100
   Dec  8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal 
in 13914 seconds.
   Dec  8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main 
process ended, respawning
  _MarkForUpload: True
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1400319/+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 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor

[Ron]

Unfortunately I am experiencing the same issue. Dell Latitude with a
docking station, 2 monitors connected by DP, 1 VGA, running kernel 4.8.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/1553503

Title:
  multi monitors - black flashes or black screen when the mouse cursor
  leaves a monitor

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

Bug description:
  When the mouse cursor leaves one of the screens, there is either :
  - no problem
  - the screen becomes black just below the position of the cursor and 
instantly comes back to normal.
  - the screen becomes entirely black with some random colored pixels 
flickering on the far left of the screen. I have to move the cursor to the 
black screen, otherwise it stays black.

  It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta.
  I have tested with other distributions (Debian Jessie and Fedora) and 
everything is fine.

  Hardware : Intel Ironlake (Thinkpad X201) with an external monitor
  plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar  5 13:17:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  MachineType: LENOVO 3680KD3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3680KD3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3680KD3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sat Mar  5 13:03:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2202 
   vendor BOE
  xserver.version: 2:1.17.3-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1553503/+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 1632849] Re: linux-lts-trusty: 3.13.0-99.146~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.13.0-99.146~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
  phase: Uploaded
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 17. October 2016 20:46 UTC

** Description changed:

  This bug is for tracking the 3.13.0-99.146~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
  phase: Uploaded
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 17. October 2016 20:46 UTC

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

Title:
  linux-lts-trusty: 3.13.0-99.146~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632849/+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 1632844] onibi (amd64) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onibi__3.13.0-99.146__2016-10-17_19-47-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] modoc (ppc64el) - tests ran: 19, failed: 6

[Brad Figg]

tests ran:  19, failed: 6;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/modoc__3.13.0-99.146__2016-10-17_19-08-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] onza (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-17_18-48-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

[Joseph Salisbury]

According to comment #139, this looks like a hardware bug.  @Andrew,
your suggesting of opening a new bug is probably best, so the different
issues experienced by folks can be uniquely reviewed.

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

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

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  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.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+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 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

[Joseph Salisbury]

Do any prior kernels boot, that would tell us if it is a kernel bug or
not.  Maybe try a Trusty kernel:

https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa/+build/11004661

Or maybe even the mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/

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

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

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

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

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

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633391/+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 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

[Joseph Salisbury]

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

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

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

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

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632902/+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 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[Joseph Salisbury]

It looks like our bisect when wrong if that kernel with the reverts
doesn't fix the bug.  I'll review what kernels were reported good vs bad
and see where we could have gone wrong.

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  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-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+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 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[NetBit73]

the same:
update-initramfs: Generating /boot/initrd.img-4.8.1-ext73-48.1-ivybridge
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xen/+bug/1611124/+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 1632844] onibi (i386) - tests ran: 3, failed: 1

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onibi__3.13.0-99.146__2016-10-17_17-55-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

[Seth Forshee]

Unfortunately there was a delay getting new kernels out to -proposed,
but 4.4.0-44.64 has been built in the canonical-kernel-team PPA and does
have the fix. This kernel should be migrated to -proposed soon, but you
can download it directly from the PPA too (I don't recommend subscribing
to that PPA however).

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+packages

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

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

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  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.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1632849] Re: linux-lts-trusty: 3.13.0-99.146~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux-lts-trusty: 3.13.0-99.146~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632849/+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 1634214] Re: kernel panic on resume from suspend with 4.4.0 kernels

[Jeremy A. Cribb]

I cannot boot into 4.4 kernels without them panicking, so I cannot run
apport-collect command.


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

Title:
  kernel panic on resume from suspend with 4.4.0 kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop repeatedly kernel panics after a botched "return from
  suspend" in my Samsung 900X laptop using (K)ubuntu 16.04.

  Booting into 4.2.0-38-generic kernel seems to work fine.

  Up until this point 4.2 and four different 4.4 kernels functioned
  properly 90% of the time. Even then, roughly one-in-ten 'resumes from
  suspend' would panic, usually with blinking caps-lock LED. Cold-
  shutdown and restart would bring the system back up with little to no
  issue. This time was different, not sure why.

  Going through DebuggingKernelSuspend
  (https://wiki.ubuntu.com/DebuggingKernelSuspend)

  DID THIS: Shutting the lid of your laptop, which is set to suspend on close.
  DID THIS: Pressed the power button
  GOT THIS: kernel panic-- no blinking caps lock, just a single unblinking 
half-cursor at the top-left of the screen

  
  cat's of appropriate files are attached. If more is needed I am more than 
happy to oblige.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634214/+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 1632844] onza (amd64) - tests ran: 30, failed: 1

[Brad Figg]

tests ran:  30, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-17_17-51-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1634214] Re: kernel panic on resume from suspend with 4.4.0 kernels

[Jeremy A. Cribb]

Attached the lsmod info as requested.


** Attachment added: "lsmod.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634214/+attachment/4762626/+files/lsmod.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/1634214

Title:
  kernel panic on resume from suspend with 4.4.0 kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop repeatedly kernel panics after a botched "return from
  suspend" in my Samsung 900X laptop using (K)ubuntu 16.04.

  Booting into 4.2.0-38-generic kernel seems to work fine.

  Up until this point 4.2 and four different 4.4 kernels functioned
  properly 90% of the time. Even then, roughly one-in-ten 'resumes from
  suspend' would panic, usually with blinking caps-lock LED. Cold-
  shutdown and restart would bring the system back up with little to no
  issue. This time was different, not sure why.

  Going through DebuggingKernelSuspend
  (https://wiki.ubuntu.com/DebuggingKernelSuspend)

  DID THIS: Shutting the lid of your laptop, which is set to suspend on close.
  DID THIS: Pressed the power button
  GOT THIS: kernel panic-- no blinking caps lock, just a single unblinking 
half-cursor at the top-left of the screen

  
  cat's of appropriate files are attached. If more is needed I am more than 
happy to oblige.

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1634214

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  kernel panic on resume from suspend with 4.4.0 kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop repeatedly kernel panics after a botched "return from
  suspend" in my Samsung 900X laptop using (K)ubuntu 16.04.

  Booting into 4.2.0-38-generic kernel seems to work fine.

  Up until this point 4.2 and four different 4.4 kernels functioned
  properly 90% of the time. Even then, roughly one-in-ten 'resumes from
  suspend' would panic, usually with blinking caps-lock LED. Cold-
  shutdown and restart would bring the system back up with little to no
  issue. This time was different, not sure why.

  Going through DebuggingKernelSuspend
  (https://wiki.ubuntu.com/DebuggingKernelSuspend)

  DID THIS: Shutting the lid of your laptop, which is set to suspend on close.
  DID THIS: Pressed the power button
  GOT THIS: kernel panic-- no blinking caps lock, just a single unblinking 
half-cursor at the top-left of the screen

  
  cat's of appropriate files are attached. If more is needed I am more than 
happy to oblige.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634214/+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 1634214] [NEW] kernel panic on resume from suspend with 4.4.0 kernels

[Jeremy A. Cribb]

Public bug reported:

My laptop repeatedly kernel panics after a botched "return from suspend"
in my Samsung 900X laptop using (K)ubuntu 16.04.

Booting into 4.2.0-38-generic kernel seems to work fine.

Up until this point 4.2 and four different 4.4 kernels functioned
properly 90% of the time. Even then, roughly one-in-ten 'resumes from
suspend' would panic, usually with blinking caps-lock LED. Cold-shutdown
and restart would bring the system back up with little to no issue. This
time was different, not sure why.

Going through DebuggingKernelSuspend
(https://wiki.ubuntu.com/DebuggingKernelSuspend)

DID THIS: Shutting the lid of your laptop, which is set to suspend on close.
DID THIS: Pressed the power button
GOT THIS: kernel panic-- no blinking caps lock, just a single unblinking 
half-cursor at the top-left of the screen


cat's of appropriate files are attached. If more is needed I am more than happy 
to oblige.

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

** Attachment added: "suspend-bug.log"
   
https://bugs.launchpad.net/bugs/1634214/+attachment/4762625/+files/suspend-bug.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/1634214

Title:
  kernel panic on resume from suspend with 4.4.0 kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop repeatedly kernel panics after a botched "return from
  suspend" in my Samsung 900X laptop using (K)ubuntu 16.04.

  Booting into 4.2.0-38-generic kernel seems to work fine.

  Up until this point 4.2 and four different 4.4 kernels functioned
  properly 90% of the time. Even then, roughly one-in-ten 'resumes from
  suspend' would panic, usually with blinking caps-lock LED. Cold-
  shutdown and restart would bring the system back up with little to no
  issue. This time was different, not sure why.

  Going through DebuggingKernelSuspend
  (https://wiki.ubuntu.com/DebuggingKernelSuspend)

  DID THIS: Shutting the lid of your laptop, which is set to suspend on close.
  DID THIS: Pressed the power button
  GOT THIS: kernel panic-- no blinking caps lock, just a single unblinking 
half-cursor at the top-left of the screen

  
  cat's of appropriate files are attached. If more is needed I am more than 
happy to oblige.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634214/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[poet_imp]

The problem persists in 16.10. I was soo hoping that this would be
resolved by the upgrade. Ubuntu 16.10 is showing version 5.41 as the
latest available. Might someone be willing to package 5.42, if that
fixes this?

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

[scott mowerson]

I am not running the low latency kernel, just generic kernel. I was 
successfully using both AMD CPU (proprietary driver) AND the NVIDIA proprietary 
driver.
I tried tweaking the UEFI settings, but made things worse. So I switched the 
settings back.

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

Title:
  scsi host6: runtime PM trying to activate child device host6 but
  parent (3-3:1.0) is not active

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [  420.107609] scsi host6: runtime PM trying to activate child device
  host6 but parent (3-3:1.0) is not active

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-19-lowlatency 4.8.0-19.21
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2728 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2728 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  6 13:16:46 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (438 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-19-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-19-lowlatency N/A
   linux-backports-modules-4.8.0-19-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631058/+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 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

[scott mowerson]

I have this problem as well. Was already running 16.10 Development branch 
successfully, I think that when 16.10 was released that the next sudo apt 
update / upgrade changed something. I started getting errors that updates 
needed to be applied, but some lock file was read-only; then whole screen 
dimmed and keyboard and mouse was unable to do anything (I could still move 
mouse pointer around screen but unable to click anything). After 15 minutes I 
noticed that the time display was frozen (15 mins late) and attempted a reboot. 
I was running KDE Plasma Desktop. But I also had gnome installed. Now I am 
unable to boot into the sign in screen. Boot process freezing during 
initialization of Ubuntu 1st error I get is: 
[ 2.859598] SCSI host8: runtime PM trying to activate child device host8 but 
parent (12-1:1.0) is not active
[ 36.308445] ata8.00: exception Emask 0x52 SAct 0x0 SErr 0x action 0xe 
frozen

Sorry, I can't transcribe any more manually, but rest of messages are
ata8.00 and ata7.00 errors.

Final line before computer gives up is:
[ 36.450198] ata7.00: status: { DRDY }

Then it is stuck on the blinking cursor.

Tried to reboot into recovery, same thing happened.

Once it is stuck, I have to push reset button, or power PC off completely.
Upon reboot, same thing happened, except when I used UEFI to boot from another 
disk, but that's FreeBSD ZFS Boot, that I am no longer use (don't have password 
for any more).

At this point I'm not sure what could possibly recover my data from the
Ubuntu partition.

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

Title:
  scsi host6: runtime PM trying to activate child device host6 but
  parent (3-3:1.0) is not active

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [  420.107609] scsi host6: runtime PM trying to activate child device
  host6 but parent (3-3:1.0) is not active

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-19-lowlatency 4.8.0-19.21
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2728 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2728 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  6 13:16:46 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (438 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-19-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-19-lowlatency N/A
   linux-backports-modules-4.8.0-19-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631058/+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 1632844] onibi (amd64) - tests ran: 30, failed: 2

[Brad Figg]

tests ran:  30, failed: 2;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onibi__3.13.0-99.146__2016-10-17_16-38-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] modoc (ppc64el) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/modoc__3.13.0-99.146__2016-10-17_16-56-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632844] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-17_17-29-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632252] Re: linux autopkgtest kills sshd in testbed

[Colin Ian King]

So the linux kernel regression test
./linux/tools/testing/selftests/breakpoints/step_after_suspend_test is
being run and does not return.  However, running this in a clean
instance it does pass.  It basically sets the RTC to wake in 5 seconds
and does a suspend and the RTC wakealarm wakes it up.  Perhaps the 5
second RTC wakealarm is too short when the system is a bit loaded and it
takes more than 5 seconds to get to sleep, hence the wakealarm has
already fired and does not wake it up when in deep sleep.

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

Title:
  linux autopkgtest kills sshd in testbed

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

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, 

[Kernel-packages] [Bug 1632844] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/onza__3.13.0-99.146__2016-10-17_17-07-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1634132] Re: using hugepages/hugepagesz causes kexec'd kernel to OOM

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  In Progress
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+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 1632252] Re: linux autopkgtest kills sshd in testbed

[Colin Ian King]

OK, so S3 sleep works OK in the VM, going to debug step_after_susp
/sys/power/state

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

Title:
  linux autopkgtest kills sshd in testbed

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

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, 
file-rss:3184kB, shmem-rss:0kB
  [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, 
file-rss:5436kB, shmem-rss:4kB
  [ 3638.641735] Out of memory: Kill process 900 (systemd) score 0 or sacrifice 
child
  [ 3638.643448] Killed process 901 ((sd-pam)) total-vm:10360kB, 
anon-rss:1300kB, file-rss:48kB, 

[Kernel-packages] [Bug 1632918] onza (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-17_15-30-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

[Robert Euhus]

I really don't understand what's going on here. It's been another 6 days
now. There has been another (broken) kernel update for xenial (4.4.0-43)
which did not include this fix, and which also did not go through
-proposed. Instead xenial-proposed is still at at 4.4.0-41, which is
broken as well.

Two "stable" kernel updates with a known regression and a simple fix.

How is this possible?

And how does this fit with xenial being an LTS-Release?

This really ain't funny any more!

For now I have build the packages with the fix applied for amd64 and
I'll try to keep up with new broken kernels. In case anybody else needs
them:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 89C9B5AE
sudo apt-add-repository -u 'http://ubuntu.repo.uni-hannover.de/ubuntu xenial 
pub'
Or get the key from here: 
http://ubuntu.repo.uni-hannover.de/ubuntu/luh-deb-repo.gpg.key

Regards, Robert

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

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

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  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.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 

[Kernel-packages] [Bug 1632918] onibi (i386) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/onibi__4.8.0-25.27__2016-10-17_15-08-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632849] Re: linux-lts-trusty: 3.13.0-99.146~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Description changed:

  This bug is for tracking the 3.13.0-99.146~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 17. October 2016 16:05 UTC

** Description changed:

  This bug is for tracking the 3.13.0-99.146~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 17. October 2016 16:05 UTC
+ phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-99.146~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632844
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632849/+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 1632844] modoc (ppc64el) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/modoc__3.13.0-99.146__2016-10-17_16-05-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 792085] Re: Automatic remount of safely removed usb 3.0 drive

[Alberto Salvia Novella]

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

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

** Changed in: nautilus (Ubuntu)
   Importance: Low => Medium

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

Title:
  Automatic remount of safely removed usb 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 1632918] modoc (ppc64el) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_15-27-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1633579] Re: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

[Alberto Salvia Novella]

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  n/a; just doing regular apt update && apt upgrade

  /boot is 86% with 68M free

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu14
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-43-generic (x86_64)
   Fri Oct 14 14:19:06 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-43-generic
  Date: Fri Oct 14 14:19:10 2016
  InstallationDate: Installed on 2016-05-23 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 0.6.5.6-0ubuntu14
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1633579/+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 1634005] Re: linux treats first partition on sdcard as much bigger than it really is?

[Chris Cheney]

I'm closing this bug as after rebooting onto current linux
4.4.0-43-generic the problem went away.

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

Title:
  linux treats first partition on sdcard as much bigger than it really
  is?

Status in linux package in Ubuntu:
  Invalid

Bug description:
  For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
  partition of my sdcard as 16GB regardless of what fdisk says it should
  be. dd sees the other partitions as the correct size.

  Also if I run mkfs.vfat on the first partition it is treated as a fuse
  filesystem when mounted, it seems very strange. The whole card has
  been zeroed out so it shouldn't be an issue of some other weird data
  on the card. Pulling and reinserting the card after partitioning makes
  no difference. I have also included the fdisk bootsector dump at the
  end of this message.

  Running linux 4.4.0-38.57 amd64

  ---

  ii  linux-headers-4.4.0-38   4.4.0-38.57  
  all  Header files related to Linux kernel version 4.4.0
  ii  linux-headers-4.4.0-38-generic   4.4.0-38.57  
  amd64Linux kernel headers for version 4.4.0 on 64 bit x86 
SMP
  ii  linux-image-4.4.0-38-generic 4.4.0-38.57  
  amd64Linux kernel image for version 4.4.0 on 64 bit x86 
SMP
  ii  linux-image-extra-4.4.0-38-generic   4.4.0-38.57  
  amd64Linux kernel extra modules for version 4.4.0 on 64 
bit x86 SMP
  ii  linux-signed-image-4.4.0-38-generic  4.4.0-38.57  
  amd64Signed kernel image generic
  ii  linux-tools-4.4.0-38 4.4.0-38.57  
  amd64Linux kernel version specific tools for version 
4.4.0-38
  ii  linux-tools-4.4.0-38-generic 4.4.0-38.57  
  amd64Linux kernel version specific tools for version 
4.4.0-38

  ---

  # fdisk -l /dev/sdd
  Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  # fdisk /dev/sdd

  Welcome to fdisk (util-linux 2.27.1).
  Changes will remain in memory only, until you decide to write them.
  Be careful before using the write command.

  Device does not contain a recognized partition table.
  Created a new DOS disklabel with disk identifier 0x57ca34c2.

  Command (m for help): n
  Partition type
     p   primary (0 primary, 0 extended, 4 free)
     e   extended (container for logical partitions)
  Select (default p): p
  Partition number (1-4, default 1): 1
  First sector (2048-62521343, default 2048):
  Last sector, +sectors or +size{K,M,G,T,P} (2048-62521343, default 62521343): 
+512MiB

  Created a new partition 1 of type 'Linux' and of size 512 MiB.

  Command (m for help): p
  Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x57ca34c2

  Device Boot Start End Sectors  Size Id Type
  /dev/sdd12048 1050623 1048576  512M 83 Linux

  Command (m for help): n
  Partition type
     p   primary (1 primary, 0 extended, 3 free)
     e   extended (container for logical partitions)
  Select (default p): p
  Partition number (2-4, default 2):
  First sector (1050624-62521343, default 1050624):
  Last sector, +sectors or +size{K,M,G,T,P} (1050624-62521343, default 
62521343): +512MiB

  Created a new partition 2 of type 'Linux' and of size 512 MiB.

  Command (m for help): n
  Partition type
     p   primary (2 primary, 0 extended, 2 free)
     e   extended (container for logical partitions)
  Select (default p): p
  Partition number (3,4, default 3):
  First sector (2099200-62521343, default 2099200):
  Last sector, +sectors or +size{K,M,G,T,P} (2099200-62521343, default 
62521343): +1024MiB

  Created a new partition 3 of type 'Linux' and of size 1 GiB.

  Command (m for help): n
  Partition type
     p   primary (3 primary, 0 extended, 1 free)
     e   extended (container for logical partitions)
  Select (default e): p

  Selected partition 4
  First sector (4196352-62521343, default 4196352):
  Last sector, +sectors or +size{K,M,G,T,P} (4196352-62521343, default 
62521343):

  Created a new partition 4 of type 'Linux' and of size 27.8 GiB.

  Command (m for help): print
  Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O 

[Kernel-packages] [Bug 1633058] Re: ghash-clmulni-intel module fails to load

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-October/080398.html
https://lists.ubuntu.com/archives/kernel-team/2016-October/080397.html

** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  ghash-clmulni-intel module fails to load

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The module ghash-clmulni-intel always fails to load with "Invalid
  argument":

  $ sudo modprobe ghash-clmulni-intel
  modprobe: ERROR: could not insert 'ghash_clmulni_intel': Invalid argument

  That was caused by the commit 8996eafdc ("crypto: ahash - ensure
  statesize is non-zero"), that added a requirement that all ahash
  algorithms now need to implement import() and export() and define a
  non zero statesize.

  The fix is composed by two commits:

  3a020a7 crypto: ghash-clmulni - Fix load failure
  1a07834 crypto: cryptd - Assign statesize properly

  Xenial and Trusty are affected and Yakkety already included the
  solution above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633058/+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 1632252] Re: linux autopkgtest kills sshd in testbed

[Colin Ian King]

..and the last things to be exec'd are:

16:01:15 exit   1165  00.037 ./breakpoint_test
16:01:15 exit   1164  00.043 /bin/sh -c for TEST in breakpoint_test 
step_after_suspend_test; do (./$TEST && echo "selftests: $TEST [PASS]") || echo 
"selftests: $TEST [FAIL]"; done;
16:01:15 exit   1166  00.036 ./breakpoint_test
Time Event  PID  Info  Duration Process
16:01:15 fork   1163 parent  /bin/sh -c for TEST in breakpoint_test 
step_after_suspend_test; do (./$TEST && echo "selftests: $TEST [PASS]") || echo 
"selftests: $TEST [FAIL]"; done;
16:01:15 fork   1167 child   /bin/sh -c for TEST in breakpoint_test 
step_after_suspend_test; do (./$TEST && echo "selftests: $TEST [PASS]") || echo 
"selftests: $TEST [FAIL]"; done;
16:01:15 fork   1167 parent  /bin/sh -c for TEST in breakpoint_test 
step_after_suspend_test; do (./$TEST && echo "selftests: $TEST [PASS]") || echo 
"selftests: $TEST [FAIL]"; done;
16:01:15 fork   1168 child   /bin/sh -c for TEST in breakpoint_test 
step_after_suspend_test; do (./$TEST && echo "selftests: $TEST [PASS]") || echo 
"selftests: $TEST [FAIL]"; done;
16:01:15 exec   1168 ./step_after_suspend_test
16:01:21 fork333 parent  /lib/systemd/systemd-udevd
16:01:21 fork   1169 child   /lib/systemd/systemd-udevd
16:01:21 fork   1169 parent  /lib/systemd/systemd-udevd
16:01:21 fork   1170 child   /lib/systemd/systemd-udevd
16:01:21 fork333 parent  /lib/systemd/systemd-udevd
16:01:21 fork   1171 child   /lib/systemd/systemd-udevd


So, I'm basically ssh'ing to the running qemu instance and running on three 
terminals:

dmesg -w, forkstat and fnotifystat to see what happens before it gets
stuck

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

Title:
  linux autopkgtest kills sshd in testbed

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

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 

[Kernel-packages] [Bug 1634034] Re: kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

Title:
  kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
  exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  During guest/isolated container execution following kernel bug got
  triggered:

  [  249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch 
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456 
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio 
scsi_transport_fc
  [  249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted 
4.4.0-42-generic #62-Ubuntu
  [  249.792560] task: edf44c90 ti: 7be68000 task.ti: 
7be68000
  [  249.792562] User PSW : 070520018000 03ff9e683730
  [  249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
 User GPRS: f000 0001 0001 
0002
  [  249.792566]03ff9e789420  0948 
03ffc7c7d480
  [  249.792568] 0948  
fc00
  [  249.792569]03ff9e789000  03ff9e6845e6 
03ff7f5297b0
  [  249.792577] User Code: 03ff9e683720: ec32000100d9aghik   %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
   #03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
   >03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
  [  249.792602] Last Breaking-Event-Address:
  [  249.792604]  [<03ff9e68355e>] 0x3ff9e68355e
  [  249.792605]  
  [  249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops

  
  #===

  
  #=== Steps to Reproduce 
  #===
  1. Use the KVM kernel module with qemu

  By applying following upstream patch this bug was not triggered again:

  commit f045402984404ddc11016358411e445192919047
  Author: David Hildenbrand 
  Date:   Thu Jul 7 10:44:10 2016 +0200

  s390/mm: fix gmap tlb flush issues

  __tlb_flush_asce() should never be used if multiple asce belong to
  a mm.

  As this function changes mm logic determining if local or global tlb
  flushes will be neded, we might end up flushing only the gmap asce on all
  CPUs and a follow up mm asce flushes will only flush on the local CPU,
  although that asce ran on multiple CPUs.

  The missing tlb flushes will provoke strange faults in user space and even
  low address protections in user space, crashing the kernel.

  Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
  Cc: sta...@vger.kernel.org # 3.15+
  Reported-by: Sascha Silbe 
  Acked-by: Martin Schwidefsky 
  Signed-off-by: David Hildenbrand 
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1634034/+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 1634034] Re: kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops

[Tim Gardner]

git describe --contains f045402984404ddc11016358411e445192919047
v4.8-rc1~167^2~10

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

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

Title:
  kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
  exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  During guest/isolated container execution following kernel bug got
  triggered:

  [  249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch 
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456 
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio 
scsi_transport_fc
  [  249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted 
4.4.0-42-generic #62-Ubuntu
  [  249.792560] task: edf44c90 ti: 7be68000 task.ti: 
7be68000
  [  249.792562] User PSW : 070520018000 03ff9e683730
  [  249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
 User GPRS: f000 0001 0001 
0002
  [  249.792566]03ff9e789420  0948 
03ffc7c7d480
  [  249.792568] 0948  
fc00
  [  249.792569]03ff9e789000  03ff9e6845e6 
03ff7f5297b0
  [  249.792577] User Code: 03ff9e683720: ec32000100d9aghik   %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
   #03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
   >03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
  [  249.792602] Last Breaking-Event-Address:
  [  249.792604]  [<03ff9e68355e>] 0x3ff9e68355e
  [  249.792605]  
  [  249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops

  
  #===

  
  #=== Steps to Reproduce 
  #===
  1. Use the KVM kernel module with qemu

  By applying following upstream patch this bug was not triggered again:

  commit f045402984404ddc11016358411e445192919047
  Author: David Hildenbrand 
  Date:   Thu Jul 7 10:44:10 2016 +0200

  s390/mm: fix gmap tlb flush issues

  __tlb_flush_asce() should never be used if multiple asce belong to
  a mm.

  As this function changes mm logic determining if local or global tlb
  flushes will be neded, we might end up flushing only the gmap asce on all
  CPUs and a follow up mm asce flushes will only flush on the local CPU,
  although that asce ran on multiple CPUs.

  The missing tlb flushes will provoke strange faults in user space and even
  low address protections in user space, crashing the kernel.

  Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
  Cc: sta...@vger.kernel.org # 3.15+
  Reported-by: Sascha Silbe 
  Acked-by: Martin Schwidefsky 
  Signed-off-by: David Hildenbrand 
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1634034/+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 1634034] Re: kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-October/080396.html

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

Title:
  kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
  exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  During guest/isolated container execution following kernel bug got
  triggered:

  [  249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch 
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456 
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio 
scsi_transport_fc
  [  249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted 
4.4.0-42-generic #62-Ubuntu
  [  249.792560] task: edf44c90 ti: 7be68000 task.ti: 
7be68000
  [  249.792562] User PSW : 070520018000 03ff9e683730
  [  249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
 User GPRS: f000 0001 0001 
0002
  [  249.792566]03ff9e789420  0948 
03ffc7c7d480
  [  249.792568] 0948  
fc00
  [  249.792569]03ff9e789000  03ff9e6845e6 
03ff7f5297b0
  [  249.792577] User Code: 03ff9e683720: ec32000100d9aghik   %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
   #03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
   >03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
  [  249.792602] Last Breaking-Event-Address:
  [  249.792604]  [<03ff9e68355e>] 0x3ff9e68355e
  [  249.792605]  
  [  249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops

  
  #===

  
  #=== Steps to Reproduce 
  #===
  1. Use the KVM kernel module with qemu

  By applying following upstream patch this bug was not triggered again:

  commit f045402984404ddc11016358411e445192919047
  Author: David Hildenbrand 
  Date:   Thu Jul 7 10:44:10 2016 +0200

  s390/mm: fix gmap tlb flush issues

  __tlb_flush_asce() should never be used if multiple asce belong to
  a mm.

  As this function changes mm logic determining if local or global tlb
  flushes will be neded, we might end up flushing only the gmap asce on all
  CPUs and a follow up mm asce flushes will only flush on the local CPU,
  although that asce ran on multiple CPUs.

  The missing tlb flushes will provoke strange faults in user space and even
  low address protections in user space, crashing the kernel.

  Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
  Cc: sta...@vger.kernel.org # 3.15+
  Reported-by: Sascha Silbe 
  Acked-by: Martin Schwidefsky 
  Signed-off-by: David Hildenbrand 
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1634034/+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 1632252] Re: linux autopkgtest kills sshd in testbed

[Colin Ian King]

I'm not able to reproduce the issues you are seeing, however I do see:

16:01:15 DEBUG| [stdout] Test read watchpoint 3 with len: 8 local: 1 global: 1 
[Ok]
16:01:15 DEBUG| [stdout] Test icebp [Ok]
16:01:15 DEBUG| [stdout] Test int 3 trap [Ok]
16:01:15 DEBUG| [stdout] selftests: breakpoint_test [PASS]

and one of the last processes to be exec'd is: step_after_susp
/sys/power/state

and klog is showing:

[ 3387.159435] PM: Syncing filesystems ... done.
[ 3393.174633] PM: Preparing system for sleep (mem)

and then it does not wake up from suspend.

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

Title:
  linux autopkgtest kills sshd in testbed

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

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed 

[Kernel-packages] [Bug 1634132] Re: using hugepages/hugepagesz causes kexec'd kernel to OOM

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Chris J Arges (arges)
   Status: In Progress

** Changed in: makedumpfile (Ubuntu Z-series)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Z-series)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Z-series)
   Status: New => Confirmed

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

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  In Progress
Status in makedumpfile source package in z-series:
  Confirmed

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+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 1632918] modoc (ppc64el) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_14-51-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1448942] Re: Juniper Network Connect Tun

[Alex Shkop]

This turned out to be an issue in juniper client. Newer version works
find

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

Title:
  Juniper Network Connect Tun

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

Bug description:
  Hi,

  i'm using Juniper Network Connect. 
  With kernel Version "3.19.0-15-generic" it stops working.

  I the logfile of Network connect i saw:

  "IP Packet too small 0"

  I found a solution which also has implemented in Fedora:

  http://www.unixgr.com/juniper-ncsvc-and-linux-3-19/
  and fix: 
  https://bugzilla.kernel.org/show_bug.cgi?id=90901
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mschroen   2784 F pulseaudio
   /dev/snd/controlC1:  mschroen   2784 F pulseaudio
   /dev/snd/controlC0:  mschroen   2784 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=cd8793fc-8985-4125-99f8-aff20e7ef69f
  InstallationDate: Installed on 2013-10-07 (566 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: LENOVO 20AY001DGE
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash 
kopt=root=/dev/mapper/vgubuntu-root vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J3ET32WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AY001DGE
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ3ET32WW(1.09):bd07/23/2013:svnLENOVO:pn20AY001DGE:pvrThinkPadS3-S440:rvnLENOVO:rn20AY001DGE:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AY001DGE
  dmi.product.version: ThinkPad S3-S440
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448942/+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 1634034] Re: kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops

[Tim Gardner]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Tim Gardner 
(timg-tpi)

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

Title:
  kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
  exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  During guest/isolated container execution following kernel bug got
  triggered:

  [  249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch 
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456 
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio 
scsi_transport_fc
  [  249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted 
4.4.0-42-generic #62-Ubuntu
  [  249.792560] task: edf44c90 ti: 7be68000 task.ti: 
7be68000
  [  249.792562] User PSW : 070520018000 03ff9e683730
  [  249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
 User GPRS: f000 0001 0001 
0002
  [  249.792566]03ff9e789420  0948 
03ffc7c7d480
  [  249.792568] 0948  
fc00
  [  249.792569]03ff9e789000  03ff9e6845e6 
03ff7f5297b0
  [  249.792577] User Code: 03ff9e683720: ec32000100d9aghik   %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
   #03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
   >03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
  [  249.792602] Last Breaking-Event-Address:
  [  249.792604]  [<03ff9e68355e>] 0x3ff9e68355e
  [  249.792605]  
  [  249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops

  
  #===

  
  #=== Steps to Reproduce 
  #===
  1. Use the KVM kernel module with qemu

  By applying following upstream patch this bug was not triggered again:

  commit f045402984404ddc11016358411e445192919047
  Author: David Hildenbrand 
  Date:   Thu Jul 7 10:44:10 2016 +0200

  s390/mm: fix gmap tlb flush issues

  __tlb_flush_asce() should never be used if multiple asce belong to
  a mm.

  As this function changes mm logic determining if local or global tlb
  flushes will be neded, we might end up flushing only the gmap asce on all
  CPUs and a follow up mm asce flushes will only flush on the local CPU,
  although that asce ran on multiple CPUs.

  The missing tlb flushes will provoke strange faults in user space and even
  low address protections in user space, crashing the kernel.

  Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
  Cc: sta...@vger.kernel.org # 3.15+
  Reported-by: Sascha Silbe 
  Acked-by: Martin Schwidefsky 
  Signed-off-by: David Hildenbrand 
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1634034/+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 1634050] Re: Please enable CONFIG_VFIO_NOIOMMU

[Tim Gardner]

** Also affects: linux (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** Also affects: dpdk (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Z-series)
   Status: New => In Progress

** Changed in: linux (Ubuntu Z-series)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Please enable CONFIG_VFIO_NOIOMMU

Status in dpdk package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in dpdk source package in z-series:
  New
Status in linux source package in z-series:
  In Progress

Bug description:
  Hi,
  for certain cases a user might want to use VFIO in NO IOMMU mode.
  This only enables it to be an option, it doesn't change things unless 
"enable_unsafe_noiommu_mode" is set. See this reference: 
https://patchwork.kernel.org/patch/7906971/ for more details.

  This is used for some setups of DPDK see this http://dpdk-
  guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu

  Usually the reason to pick vfio over uio is the isolation. But there
  are some cases where vfio is required for extra features but can't
  work unless NO-IOMMU mode is used.

  I watched the topic a while checking if there is some major "oh crap
  what have we done" but there was none. An since by only enabling it in
  the kernel it shouldn't change a lot I wanted to ask if you could
  enable this config in the kernel for Z*.

  Technically it would be nice to get it in Yakkety as well, but I think
  we should be fine only working forward and enabling it in the Z
  release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+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 1632918] modoc (ppc64el) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_13-42-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

With the QEMU runner this gets further, but it fails for me with

14:33:01 DEBUG| Running 'git clone 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety 
linux'
14:33:01 ERROR| [stderr] Cloning into 'linux'...
autopkgtest [16:02:54]: ERROR: timed out on command "..." (kind: test)
autopkgtest [16:02:54]: test ubuntu-regression-suite: ---]
Exception in thread copyin:
OSError: [Errno 28] No space left on device

Which bears the questions:

 (1) why is this timing out -- shouldn't failures like this cause an
immediate exit? ISTM that the test suite is very prone to just hanging
when anything goes wrong; can this be robustified somehow?

 (2) Is it really necessary to clone the entire kernel for the test?
This will both take ages (it is running through a proxy in the infra!)
and also take lots of disk space. If this just needs a few files, can
you get them individually instead? If this needs to compile some
helper/test binaries, can this happen during package build and you ship
them in linux-source, linux-tools-XX, or maybe the -dbgsym package?

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

Title:
  linux autopkgtest kills sshd in testbed

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

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, 

[Kernel-packages] [Bug 1632918] onza (i386) - tests ran: 3, failed: 1

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-17_12-06-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1633414] Re: linux: 4.4.0-44.64 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux: 4.4.0-44.64 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-44.64 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1633414/+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 1633690] Re: byt-max98090 not working on linux-image-4.8.0-22-generic on baytrail hardware

[Tim Gardner]

I'm betting it is related to commit
cfffcc66a89ab6d9961b2cde6cdab2ba056451ad ('ASoC: Intel: Load the atom
DPCM driver only')

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

Title:
  byt-max98090 not working on linux-image-4.8.0-22-generic  on baytrail
  hardware

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After a recent 'do-release-upgrade' upgrade from Xenial's linux-
  image-4.4.0-42-generic kernel to Yakkety's linux-
  image-4.8.0-22-generic, I lost my audio output. Some investigation
  showed that the hardware was not being detected at all, and further
  investigation revealed the following:

  Excerpt from dmesg:

  intel_sst_acpi 80860F28:00: No matching machine driver found

  
  After a bit of poking around I suspect that this is a kernel build 
configuration issue and probably not actual code that is the root of this 
issue. On a hunch I installed linux-image-4.7.2-galliumos from the galliumos 
repo and got my sound working again, which to me confirms that this is a kernel 
issue and not a userland issue. I was not using galliumos kernels before and 
had my audio working properly in Xenial.

  Please let me know if you can hunt this down with the provided
  information or if you need me to boot the bad kernel again and give
  you more stuff to work with.

  Thanks

  HARDWARE INFO:

  00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series SoC Transaction Register [8086:0f00] (rev 0e)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC 
Transaction Register [8086:0f31]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation Atom Processor 
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 0e) (prog-if 30 
[XHCI])
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron 
N2000 Series USB xHCI [8086:0f35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <512ns, L1 <1us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF 
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0300c  Data: 41e2
Capabilities: [90] Subsystem: Intel Corporation Atom Processor E3800 
Series PCI Express Root Port 1 [8086:0f48]

[Kernel-packages] [Bug 1634153] [NEW] Xenial update to v4.4.25 stable release

[Tim Gardner]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.4.25 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.25 stable release shall be
applied:

timekeeping: Fix __ktime_get_fast_ns() regression
ALSA: ali5451: Fix out-of-bound position reporting
ALSA: usb-audio: Extend DragonFly dB scale quirk to cover other variants
ALSA: usb-line6: use the same declaration as definition in header for MIDI 
manufacturer ID
mfd: rtsx_usb: Avoid setting ucr->current_sg.status
mfd: atmel-hlcdc: Do not sleep in atomic context
mfd: 88pm80x: Double shifting bug in suspend/resume
mfd: wm8350-i2c: Make sure the i2c regmap functions are compiled
KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2 register
KVM: MIPS: Drop other CPU ASIDs on guest MMU changes
KVM: PPC: BookE: Fix a sanity check
x86/boot: Fix kdump, cleanup aborted E820_PRAM max_pfn manipulation
x86/irq: Prevent force migration of irqs which are not in the vector domain
x86/dumpstack: Fix x86_32 kernel_stack_pointer() previous stack access
ARM: dts: mvebu: armada-390: add missing compatibility string and bracket
ARM: dts: MSM8064 remove flags from SPMI/MPP IRQs
ARM: cpuidle: Fix error return code
ima: use file_dentry()
tpm: fix a race condition in tpm2_unseal_trusted()
tpm_crb: fix crb_req_canceled behavior
Linux 4.4.25

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.4.25 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.4.25 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.4.25 stable release shall be
+ applied:
  
-The following patches from the v4.4.25 stable release shall be
- applied:
+ timekeeping: Fix __ktime_get_fast_ns() regression
+ ALSA: ali5451: Fix out-of-bound position reporting
+ ALSA: usb-audio: Extend DragonFly dB scale quirk to cover other variants
+ ALSA: usb-line6: use the same declaration as definition in header for MIDI 
manufacturer ID
+ mfd: rtsx_usb: Avoid setting ucr->current_sg.status
+ mfd: atmel-hlcdc: Do not sleep in atomic context
+ mfd: 88pm80x: Double shifting bug in suspend/resume
+ mfd: wm8350-i2c: Make sure the i2c regmap functions are compiled
+ KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2 register
+ KVM: MIPS: Drop other CPU ASIDs on guest MMU changes
+ KVM: PPC: BookE: Fix a sanity check
+ x86/boot: Fix kdump, cleanup aborted E820_PRAM max_pfn manipulation
+ x86/irq: Prevent force migration of irqs which are not in the vector domain
+ x86/dumpstack: Fix x86_32 kernel_stack_pointer() previous stack access
+ ARM: dts: mvebu: armada-390: add missing compatibility string and bracket
+ ARM: dts: MSM8064 remove flags from SPMI/MPP IRQs
+ ARM: cpuidle: Fix error return code
+ ima: use file_dentry()
+ tpm: fix a race condition in tpm2_unseal_trusted()
+ tpm_crb: fix crb_req_canceled behavior
+ Linux 4.4.25

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

Title:
  Xenial update to v4.4.25 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree 

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Colin Ian King]

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  linux autopkgtest kills sshd in testbed

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

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, 
file-rss:3184kB, shmem-rss:0kB
  [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, 
file-rss:5436kB, shmem-rss:4kB
  [ 3638.641735] Out of memory: Kill process 900 (systemd) score 0 or sacrifice 
child
  [ 3638.643448] Killed process 901 ((sd-pam)) total-vm:10360kB, 
anon-rss:1300kB, 

[Kernel-packages] [Bug 1632844] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/ms10-34-mcdivittB0-kernel__3.13.0-99.146__2016-10-17_13-07-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Grief]

@timg-tpi: Got it! Thanks for the explanation. As I said, I've compiled
the kernel on my own, so don't worry :) But looks like a lack of testing
before the release

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-raspi2 source package in Yakkety:
  Fix Released

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1627198/+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 1632918] onibi (i386) - tests ran: 3, failed: 1

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/onibi__4.8.0-25.27__2016-10-17_11-47-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1402763] Re: Multicast traffic not propating correctly over linux bridge

[Anastasia]

** Changed in: juju-core
   Status: Triaged => Won't Fix

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

Title:
  Multicast traffic not propating correctly over linux bridge

Status in juju-core:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There's a lot of supposition in the title of this bug but its
  currently my best guess.

  In this deployment, I have a number of services running in LXC
  containers across multiple physical hosts; each service is clustered
  across three units, all on separate physical hosts, using corosync and
  pacemaker; when using multicast to support cluster communication, I
  occasionally see a container drop out of the cluster and use its
  isolation response (to shutdown all managed services); when using
  unicast I've not yet see this same problem.

  LXC containers are bridged to the main physical network using a linux
  bridge:

eth0 <-> juju-br0 <-> vethXXX <-> | vethXXX |

  All MTU's are standard (1500).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 15 17:20:08 2014
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 17 10:16 seq
   crw-rw 1 root audio 116, 33 Dec 17 10:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R610
  Package: lxc 1.0.6-0ubuntu0.1
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro
  ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images trusty uec-images apparmor
  Uname: Linux 3.13.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo 
video
  _MarkForUpload: True
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dmi.bios.date: 08/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.0.7
  dmi.board.name: 0F0XJ6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr6.0.7:bd08/18/2011:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0F0XJ6:rvrA11:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R610
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1402763/+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 1632844] dwalin (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-99.146/dwalin__3.13.0-99.146__2016-10-17_12-36-00/results-index.html

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

Title:
  linux: 3.13.0-99.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-99.146 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1634132] Re: using hugepages/hugepagesz causes kexec'd kernel to OOM

[Chris J Arges]

** Patch added: "lp1634132-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+attachment/4762494/+files/lp1634132-yakkety.debdiff

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

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+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 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Tim Gardner]

Grief - mainline only gets built when upstream Linux changes, hence the
reason for this stale config which we've since changed in the distro
kernel. I've requested a mainline rebuild which should complete
presently.

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-raspi2 source package in Yakkety:
  Fix Released

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1627198/+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 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_13-01-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632918] modoc (ppc64el) - tests ran: 19, failed: 6

[Brad Figg]

tests ran:  19, failed: 6;
  
http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_12-44-00/results-index.html

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

Title:
  linux: 4.8.0-25.27 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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