date:20161220

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/onza__3.13.0-107.154__2016-12-21_07-22-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/1651197

Title:
  linux: 3.13.0-107.154 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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-107.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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651197/+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 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot

2016-12-20 Thread Alberto Salvia Novella

Since this bug renders the system broken, it should have an importance
of "critical".

** Changed in: nvidia-graphics-drivers-367 (Ubuntu)
   Importance: Undecided => Critical

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

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

Title:
  nvidia-367 with kernel 4.4.0-45-generic won't boot

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded the nvidia drivers, I could no longer boot via kernel
  4.4.0-45-generic. I can boot with kernel 4.4.0-31-generic.

  WORKAROUND: Use nouveau.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   2248 F pulseaudio
   /dev/snd/controlC0:  lost   2248 F pulseaudio
   /dev/snd/controlC1:  lost   2248 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Nov  3 12:12:55 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/onza__3.13.0-107.154__2016-12-21_06-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/1651197

Title:
  linux: 3.13.0-107.154 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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-107.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: Uploaded

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/ms10-35-mcdivittB0-kernel__3.13.0-107.154__2016-12-21_07-00-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/1651197

Title:
  linux: 3.13.0-107.154 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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-107.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: Uploaded

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/modoc__3.13.0-107.154__2016-12-21_06-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/1651197

Title:
  linux: 3.13.0-107.154 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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-107.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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651197/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-20 Thread bagl0312

Confirmed that the patch works also on dell latitude E7370 with kernel version
4.4.0-57-generic #78-Ubuntu SMP

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 3.13.0-107.154~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: 1651197
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 06:16 UTC

** Description changed:

  This bug is for tracking the 3.13.0-107.154~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: 1651197
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 21. December 2016 06:16 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-lts-trusty: 3.13.0-107.154~precise1 -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-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-107.154~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: 1651197
  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/1651204/+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 1651629] Re: [Asus X200M] Brightness keys don't work.

Sorry about that, I thought I was already on 506 for some reason.

I updated to 506, and tested with the 4.9 kernel, and the issue still
persists.

The output from the commands was:

X200MA.506
04/15/2015

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

** Tags removed: bios-outdated-506
** Tags added: latest-bios-506

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

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/secchi__4.8.0-32.34~16.04.1__2016-12-21_04-49-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1651211] Re: linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  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: 1651207
  phase: Packaging
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 06:00 UTC

** Description changed:

  This bug is for tracking the  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: 1651207
- phase: Packaging
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 21. December 2016 06:00 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  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: 1651207
  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/1651211/+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 1651207] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-120.163-generic/onza__3.2.0-120.163__2016-12-21_05-34-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/1651207

Title:
  linux: 3.2.0-120.163 -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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta 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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 3.2.0-120.163 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. December 2016 18:34 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-120.163-generic/onza__3.2.0-120.163__2016-12-21_05-10-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/1651207

Title:
  linux: 3.2.0-120.163 -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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta 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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 3.2.0-120.163 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. December 2016 18:34 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651207/+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 1651005] Re: Unidentified Trackpad Synaptics

2016-12-20 Thread Carl Mueller

Same issue also appears in Linux Mint 18.1 Mate. In all instances, the
touchpad works in the live USB boot before installation but after
installation, its as though it is not even installed.

@santi Thank you for letting me know. It's definitely frustrating as its
an essential piece of the usability of the computer!!

Are the upstream kernels shared between Ubuntu, Linux Mint, and Arch
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/1651005

Title:
  Unidentified Trackpad Synaptics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently purchased a Sager NP8152-S / Clevo 650RP6 on which I am dual 
booting.
  See http://www.clevo.com/clevo_prodetail.asp?id=958=en

  The trackpad is not detected. xinput does not display a trackpad
  device nor is the device listed in cat /proc/bus/input/devices which
  is uploaded as a file entitled devices.

  The trackpad device is a Synaptics SMBus TouchPad.

  Please let me know if I incorrectly reported this bug as it is my
  first for Ubuntu. I followed the instructions listed on
  https://wiki.ubuntu.com/DebuggingTouchpadDetection in the section
  called "In case your Touchpad doesn't work at all (No response from
  the Touchpad)".

  Thank you!

  


  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.8.0.30.39
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cmuell89   2587 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec 18 17:52:04 2016
  HibernationDevice: RESUME=UUID=a7e110fa-7d4d-4b96-8681-fb7acbb406a9
  InstallationDate: Installed on 2016-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc.
   Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=49d81fc1-d0a2-493f-9a49-c2a533f8d0a6 ro quiet splash i8042.nomux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08LS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08LS2:bd11/11/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651005/+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 1651629] Re: [Asus X200M] Brightness keys don't work.

Matthew Brooks, as per
https://www.asus.com/Notebooks/X200MA/HelpDesk_Download/ an update to
your computer's buggy, insecure, and outdated BIOS is available (506).
When you update to this following
https://help.ubuntu.com/community/BIOSUpdate how does this improve the
situation?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new report.

It is most helpful that after the BIOS is updated, if the problem is still 
reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on how this improves the 
situation.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

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

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651629/+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 1651629] Re: [Asus X200M] Brightness keys don't work.

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.9

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

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

tests ran:  18, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/secchi__4.8.0-32.34~16.04.1__2016-12-21_03-57-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1633943] Re: No Wifi Resuming After Suspend

[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/1633943

Title:
  No Wifi Resuming After Suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  After Suspending a connection there is no wifi connection established on 
Resuming.
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Ubuntu 4.4.0-43.63-generic 4.4.21

  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/controlC0:  rbrown 1614 F pulseaudio
  CurrentDesktop: LXDE
  Date: Mon Oct 17 11:36:09 2016
  HibernationDevice: RESUME=UUID=9cbaae01-5229-4cc1-974b-9dc9f6a0091e
  InstallationDate: Installed on 2016-08-19 (58 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP ENVY m6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=2ac86fb6-acc7-409b-ab21-e30be1ac8925 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18A5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 73.41
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd09/06/2012:svnHewlett-Packard:pnHPENVYm6NotebookPC:pvr088211305B1620100:rvnHewlett-Packard:rn18A5:rvr73.41:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m6 Notebook PC
  dmi.product.version: 088211305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1573062] Comment bridged from LTC Bugzilla

2016-12-20 Thread bugproxy

--- Comment From balb...@au1.ibm.com 2016-12-20 22:55 EDT---
Could the Ubuntu team check if this is still an issue with the 4.8 kernel?

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

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

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

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

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

[Kernel-packages] [Bug 1573062] Comment bridged from LTC Bugzilla

2016-12-20 Thread bugproxy

--- Comment From balb...@au1.ibm.com 2016-12-20 22:55 EDT---
Could the Ubuntu team check if this is still an issue with the 4.8 kernel?

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

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

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

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

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

[Kernel-packages] [Bug 1329510] Re: [Asus X200M] Changing Backlight not working

** Tags removed: latest-bios-500
** Tags added: bios-outdated-506

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

Title:
  [Asus X200M] Changing Backlight not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Backlight setting is not working with Lubuntu 14.04.

  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.

  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :

  Section "Device"
  Identifier "card0"
  Driver "intel"
  Option "Backlight" "intel_backlight"
  BusID "PCI:0:2:0"
  EndSection

  but special keys are not working, and there are no events in
  acpi_listen when pressing these keys.

  Update : To get special keys working (from : 
http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop)
  In the file /etc/default/grub, you'll see a line that looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  All you want to do is add two parameters to that line to make it look
  like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="

  That's it. Save the file and run sudo update-grub in a terminal.
  Reboot, and your brightness keys should start working perfectly.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume   1447 F lxpanel
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Jun 12 21:52:16 2014
  HibernationDevice: RESUME=UUID=5b0a59aa-0acf-415f-93bd-62df1b558efb
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=37551324-2550-4e13-aea9-4603fbd63807 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510/+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 1651629] Re: [Asus X200M] Brightness keys don't work.

Matthew Brooks, thank you for reporting this and helping make Ubuntu
better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** This bug is no longer a duplicate of bug 1329510
   [Asus X200M] Changing Backlight not working

** Tags added: bios-outdated-506

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

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

** Description changed:

- Same bug as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510
- Was asked to use the "ubuntu-bug linux" to post this along with the laptop 
info.
- 
  Fn + F5 or F6 is supposed to lower or raise the brightness respectively.
- By default, nothing happens when pushing the buttons. Editing the grub
+ By default, nothing happens when pushing the buttons.Editing the grub
  config to add "acpi_osi=" to the kernel command line seems to make the
  buttons get recognized, and the brightness popup displays, but the
  actual brightness doesn't change.
  
- Changing the brightness by piping a number into
- "/sys/class/backlight/intel_backlight/brightness" works fine, and the
- brightness slider that shows up in the drop-down from the Gnome status
- bar thing works fine, but the actual hardware buttons don't do anything
- even when they get recognized.
+ WORKAROUND: Pipe a number into
+ "/sys/class/backlight/intel_backlight/brightness", or use the brightness
+ slider that shows up in the drop-down from the Gnome status bar.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
-  Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp. 
-  Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
+  Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/naumann__4.8.0-32.34~16.04.1__2016-12-21_03-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] secchi (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/secchi__4.8.0-32.34~16.04.1__2016-12-21_03-41-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] secchi (amd64) - tests ran: 64, failed: 0

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-21_03-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1329510] Re: [Asus X200M] Changing Backlight not working

Alright, that's done. It's bug number 1651629
I've marked it as a duplicate of this one, and subscribed you to it.

If there's anything else I can do to help get this fixed, just let me
know.

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

Title:
  [Asus X200M] Changing Backlight not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Backlight setting is not working with Lubuntu 14.04.

  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.

  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :

  Section "Device"
  Identifier "card0"
  Driver "intel"
  Option "Backlight" "intel_backlight"
  BusID "PCI:0:2:0"
  EndSection

  but special keys are not working, and there are no events in
  acpi_listen when pressing these keys.

  Update : To get special keys working (from : 
http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop)
  In the file /etc/default/grub, you'll see a line that looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  All you want to do is add two parameters to that line to make it look
  like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="

  That's it. Save the file and run sudo update-grub in a terminal.
  Reboot, and your brightness keys should start working perfectly.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume   1447 F lxpanel
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Jun 12 21:52:16 2014
  HibernationDevice: RESUME=UUID=5b0a59aa-0acf-415f-93bd-62df1b558efb
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=37551324-2550-4e13-aea9-4603fbd63807 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510/+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 1651629] [NEW] [Asus X200M] Brightness keys don't work.

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

Public bug reported:

Same bug as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510
Was asked to use the "ubuntu-bug linux" to post this along with the laptop info.

Fn + F5 or F6 is supposed to lower or raise the brightness respectively.
By default, nothing happens when pushing the buttons. Editing the grub
config to add "acpi_osi=" to the kernel command line seems to make the
buttons get recognized, and the brightness popup displays, but the
actual brightness doesn't change.

Changing the brightness by piping a number into
"/sys/class/backlight/intel_backlight/brightness" works fine, and the
brightness slider that shows up in the drop-down from the Gnome status
bar thing works fine, but the actual hardware buttons don't do anything
even when they get recognized.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Dec 20 20:53:38 2016
HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
InstallationDate: Installed on 2016-12-21 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-32-generic N/A
 linux-backports-modules-4.8.0-32-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.502
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X200MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug yakkety

** This bug has been marked a duplicate of bug 1329510
   [Asus X200M] Changing Backlight not working

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

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  New

Bug description:
  Same bug as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510
  Was asked to use the "ubuntu-bug linux" to post this along with the laptop 
info.

  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the buttons.
  Editing the grub config to add "acpi_osi=" to the kernel command line
  seems to make the buttons get recognized, and the brightness popup
  displays, but the actual brightness doesn't change.

  Changing the brightness by piping a number into
  "/sys/class/backlight/intel_backlight/brightness" works fine, and the
  brightness slider that shows up in the drop-down from the Gnome status
  bar thing works fine, but the actual hardware buttons don't do
  anything even when they get recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation

[Kernel-packages] [Bug 1642044] secchi (amd64) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-21_02-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] naumann (amd64) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/naumann__4.9.0-11.12__2016-12-21_02-41-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1650752] Re: Thinkpad Yoga 13 fails to suspend after update to 4.8.0.30.39

kaeru, please execute the following command only once, as it will automatically 
gather debugging information, in a terminal:
apport-collect 1650752

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Thinkpad Yoga 13 fails to suspend after update to  4.8.0.30.39

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It suspends then automatically resumes a few seconds later. Latest
  kernel update brings back screen auto-rotate feature, but also breaks
  suspend. Not sure if this is related. Previous few kernel releases had
  auto-rotate feature disabled, but suspend worked properly and did not
  resume from suspend automatically.

  [  737.222140] PM: Syncing filesystems ... done.
  [  737.233688] PM: Preparing system for sleep (mem)
  [  737.234034] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  737.236194] Double checking all user space processes after OOM killer 
disable... (elapsed 0.000 seconds) 
  [  737.236333] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) 
done.
  [  737.237252] PM: Suspending system (mem)
  [  737.237283] Suspending console(s) (use no_console_suspend to debug)
  [  737.404190] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  737.406041] sd 0:0:0:0: [sda] Stopping disk
  [  738.065297] PM: suspend of devices complete after 827.881 msecs
  [  738.085132] PM: late suspend of devices complete after 19.829 msecs
  [  738.086363] xhci_hcd :00:14.0: System wakeup enabled by ACPI
  [  738.105461] PM: noirq suspend of devices complete after 20.326 msecs
  [  738.105897] ACPI: Preparing to enter system sleep state S3
  [  738.361104] ACPI : EC: EC stopped
  [  738.361105] PM: Saving platform NVS memory
  [  738.361121] Disabling non-boot CPUs ...
  [  738.361598] Broke affinity for irq 23
  [  738.361604] Broke affinity for irq 40
  [  738.361611] Broke affinity for irq 43
  [  738.363673] smpboot: CPU 1 is now offline
  [  738.386513] Broke affinity for irq 23
  [  738.386519] Broke affinity for irq 40
  [  738.386525] Broke affinity for irq 43
  [  738.386533] Broke affinity for irq 59
  [  738.387594] smpboot: CPU 2 is now offline
  [  738.418497] Broke affinity for irq 1
  [  738.418508] Broke affinity for irq 9
  [  738.418513] Broke affinity for irq 12
  [  738.418520] Broke affinity for irq 23
  [  738.418523] Broke affinity for irq 40
  [  738.418526] Broke affinity for irq 42
  [  738.418528] Broke affinity for irq 43
  [  738.418534] Broke affinity for irq 59
  [  738.419573] smpboot: CPU 3 is now offline
  [  738.440159] ACPI: Low-level resume complete
  [  738.440235] ACPI : EC: EC started
  [  738.440236] PM: Restoring platform NVS memory
  [  738.440625] Enabling non-boot CPUs ...
  [  738.463840] x86: Booting SMP configuration:
  [  738.463841] smpboot: Booting Node 0 Processor 1 APIC 0x1
  [  738.466739]  cache: parent cpu1 should not be sleeping
  [  738.466961] CPU1 is up
  [  738.487864] smpboot: Booting Node 0 Processor 2 APIC 0x2
  [  738.490555]  cache: parent cpu2 should not be sleeping
  [  738.490870] CPU2 is up
  [  738.535883] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  738.538658]  cache: parent cpu3 should not be sleeping
  [  738.539378] CPU3 is up
  [  738.549959] ACPI: Waking up from system sleep state S3
  [  739.483697] xhci_hcd :00:14.0: System wakeup disabled by ACPI
  [  739.483772] PM: noirq resume of devices complete after 32.141 msecs
  [  739.484169] PM: early resume of devices complete after 0.371 msecs
  [  739.487691] rtc_cmos 00:01: System wakeup disabled by ACPI
  [  739.488427] sd 0:0:0:0: [sda] Starting disk
  [  739.531853] xhci_hcd :00:14.0: port 4 resume PLC timeout
  [  739.547494] xhci_hcd :00:14.0: port 3 resume PLC timeout
  [  739.635640] usb 1-1.7: reset full-speed USB device number 3 using ehci-pci
  [  739.783794] usb 2-4: reset full-speed USB device number 2 using xhci_hcd
  [  739.802392] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  739.802641] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  739.802643] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  739.802723] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  739.802888] ata1.00: supports DRM functions and may not be fully accessible
  [  739.803249] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  739.803251] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  739.803272] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  739.803357] ata1.00: supports DRM functions and may not be fully accessible
  [  739.803421] ata1.00: configured

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-20 Thread Kyle Vedder

I just received the patch and my touchpad now works as expected.

This is for my Dell Latitude E5470, which, before this update, had the
generic mouse drivers which did not recognize it as a touchpad.

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1622322] Re: Realtek 8153-based ethernet adapter doesn't work

zwpwjwtz, please ask your questions via Launchpad (not via personal
emails). This allows others to help also.

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

Title:
  Realtek 8153-based ethernet adapter doesn't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  Similar to Bug #1586195.

  Realtek 8153-based ethernet adapter doesn't work. No entry for the
  adapter appears in ifconfig.

  Adding "0bda:8152" to tlp blacklist（/etc/default/tlp) or triggering
  usb_modeswitch (by ejecting /dev/sr0) does not work either.

  
  dnesg output:
  
  [ 15.229468] usb 3-1.1: new SuperSpeed USB device number 4 using xhci_hcd
  [ 15.249257] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=8153
  [ 15.249260] usb 3-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [ 15.249262] usb 3-1.1: Product: USB 10/100/1000 LAN
  [ 15.249264] usb 3-1.1: Manufacturer: Realtek
  [ 15.249265] usb 3-1.1: SerialNumber: 
  [ 15.329605] usb 3-1.1: reset SuperSpeed USB device number 4 using xhci_hcd
  [ 15.372202] r8152 3-1.1:1.0 eth0: v1.08.2
  [ 16.413210] r8152 3-1.1:1.0 enx00e04c680bfb: renamed from eth0
  [ 16.454622] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680bfb: link is not ready
  [ 17.032871] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680bfb: link is not ready
  [ 17.038222] usb 3-1.1: Disable of device-initiated U1 failed.
  [ 17.038257] usb 3-1.1: Failed to set U2 timeout to 0x0,error code -71
  [ 17.042065] usb 3-1.1: Set SEL for device-initiated U1 failed.
  [ 17.045682] usb 3-1.1: Set SEL for device-initiated U2 failed.
  [ 17.045690] usb 3-1.1: usb_reset_and_verify_device Failed to disable LPM
 .
  [ 17.046906] usb 3-1.1: USB disconnect, device number 4
  [ 17.713462] usb 3-1.1: new SuperSpeed USB device number 5 using xhci_hcd
  [ 17.730139] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=8153
  [ 17.730147] usb 3-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [ 17.730151] usb 3-1.1: Product: USB 10/100/1000 LAN
  [ 17.730155] usb 3-1.1: Manufacturer: Realtek
  [ 17.730158] usb 3-1.1: SerialNumber: 
  [ 22.732882] usb 3-1.1: Disable of device-initiated U1 failed.
  [ 22.739551] usb 3-1.1: Disable of device-initiated U2 failed.
  [ 23.053009] usb 3-1.1: reset SuperSpeed USB device number 5 using xhci_hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1825 F pulseaudio
   /dev/snd/controlC1:  user   1825 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 11 19:01:59 2016
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 930X2K/931X2K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=711b7dd0-0467-4bb6-85b4-bca68124c2cb ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06AEU.084.151026.MK
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930X2K-K07CN
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8656A04-C01-G001-S0001+10.0.10586
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06AEU.084.151026.MK:bd10/26/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn930X2K/931X2K:pvrP06AEU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930X2K-K07CN:rvrSGL8656A04-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 930X2K/931X2K
  dmi.product.version: P06AEU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622322/+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 1329510] Re: [Asus X200M] Changing Backlight not working

Matthew Brooks, it will help immensely if you filed a new report with the 
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  [Asus X200M] Changing Backlight not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Backlight setting is not working with Lubuntu 14.04.

  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.

  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :

  Section "Device"
  Identifier "card0"
  Driver "intel"
  Option "Backlight" "intel_backlight"
  BusID "PCI:0:2:0"
  EndSection

  but special keys are not working, and there are no events in
  acpi_listen when pressing these keys.

  Update : To get special keys working (from : 
http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop)
  In the file /etc/default/grub, you'll see a line that looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  All you want to do is add two parameters to that line to make it look
  like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="

  That's it. Save the file and run sudo update-grub in a terminal.
  Reboot, and your brightness keys should start working perfectly.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume   1447 F lxpanel
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Jun 12 21:52:16 2014
  HibernationDevice: RESUME=UUID=5b0a59aa-0acf-415f-93bd-62df1b558efb
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=37551324-2550-4e13-aea9-4603fbd63807 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510/+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 1611536] Re: Fan on full speed without noapic or nolapic on HP 6715s

Carl Englund, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/comments/13
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  Fan on full speed without noapic or nolapic on HP 6715s

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Without adding noapic or nolapic to boot parameters the fan will run
  on full speed, the system is sluggish (can almost see windows
  redrawing on screen). On some kernel versions tested, rebooting also
  fails.

  The parameter(s) were not required in Trusty. I also tested some
  Mainline kernels and discovered 3.19.8 and 4.0.9 works without the
  parameters. At least 4.1.29 and onward requires noapic or nolapic for
  this machine to work properly but I have yet to investigate the
  versions between 4.0.9 and 4.1.29.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diskdoc2700 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Aug 10 01:15:07 2016
  HibernationDevice: RESUME=UUID=522810df-638a-412b-9aab-791e2e2bc545
  InstallationDate: Installed on 2016-06-07 (63 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Compaq 6715s (RU655ET#AK8)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=3a37ee65-4c02-4a95-b814-f4538a4a308d ro quiet splash noapic 
acpi_force_32bit_fadt_addr vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YTT Ver. F.20
  dmi.board.name: 30C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2D
  dmi.chassis.asset.tag: CNU7201T8J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YTTVer.F.20:bd12/01/2011:svnHewlett-Packard:pnHPCompaq6715s(RU655ET#AK8):pvrF.20:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6715s (RU655ET#AK8)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

turoyo dee, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31

[Kernel-packages] [Bug 1329510] Re: [Asus X200M] Changing Backlight not working

The issue still exists in 16.10. Fresh install, made just a few hours
ago.

The workarounds don't even make the brightness keys work. The system
shows the brightness popup, which responds to the brightness keys, but
the actual brightness doesn't change.

Changing brightness by piping a number into
/sys/class/backlight/intel_backlight/brightness still works though, but
it'd be really nice to get the actual keys working.

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

Title:
  [Asus X200M] Changing Backlight not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Backlight setting is not working with Lubuntu 14.04.

  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.

  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :

  Section "Device"
  Identifier "card0"
  Driver "intel"
  Option "Backlight" "intel_backlight"
  BusID "PCI:0:2:0"
  EndSection

  but special keys are not working, and there are no events in
  acpi_listen when pressing these keys.

  Update : To get special keys working (from : 
http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop)
  In the file /etc/default/grub, you'll see a line that looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  All you want to do is add two parameters to that line to make it look
  like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="

  That's it. Save the file and run sudo update-grub in a terminal.
  Reboot, and your brightness keys should start working perfectly.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume   1447 F lxpanel
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Jun 12 21:52:16 2014
  HibernationDevice: RESUME=UUID=5b0a59aa-0acf-415f-93bd-62df1b558efb
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=37551324-2550-4e13-aea9-4603fbd63807 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Title:
  Ubuntu can try to boot from unbootable partition if UUID conflicts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't think this is as specific to AWS/EC2 as it might initially
  appear, but here goes:

  To reproduce:

  * Create AWS EC2 instance using official Ubuntu 14.04 AMI
  * Use AWS EBS snapshot to clone root EBS volume to new EBS volume
  * Mount it from EC2 console
  * e2label to ensure label unique
  * fdisk to ensure partition not bootable
  * vi /etc/fstab to ensure mounted in appropriate place
  * forget to use tunefs -U to change the partition UUID
  * reboot a few times, perhaps upgrading kernel between reboots

  Expected behaviour:

  * Warnings during or after boot process that two partitions have the same UUID
  * Consistently booting from the partition labelled cloudimg-rootfs despite 
the UUID conflict
  * Consistently booting from the partition with the boot flag set despite the 
UUID conflict

  Actual behaviour:

  * No apparent warnings during or after boot process that two partitions have 
the same UUID
  * First few boots turned out fine
  * Around a month later, after a kernel upgrade from 3.13.0-92 or 105 to 106, 
started consistently booting from non-bootable partition labelled var-lib

  Console log output on problem:

  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top 
... done.
  Begin: Running /scripts/local-premount ... done.
  [2.518466] EXT4-fs (xvdf1): mounted filesystem with ordered data 
mode. Opts: (null)
  Begin: Running /scripts/local-bottom ... done.
  done.
  Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev 
failed: No such file or directory
  done.
  mount: mounting /sys on /root/sys failed: No such file or directory
  mount: mounting /proc on /root/proc failed: No such file or directory
  Target filesystem doesn't have requested /sbin/init.
  No init found. Try passing init= bootarg.

  Ops remediation of affected hosts:

  * Remount secondary EBS volume to spare host
  * tunefs /dev/xvdf1 -U `uuidgen`
  * Remount it back to the host with the outage

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-106-generic 3.13.0-106.153
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 21 01:06 seq
   crw-rw 1 root audio 116, 33 Dec 21 01:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 21 01:57:13 2016
  Ec2AMI: ami-ba3e14d9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2c
  Ec2InstanceType: c4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=63e1d5b9-1fa6-4ff3-b8d6-7a63b4b18e59 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd11/11/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651622/+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 1650752] Re: Thinkpad Yoga 13 fails to suspend after update to 4.8.0.30.39

2016-12-20 Thread kaeru

Linux nightwing 4.8.15-040815-generic #201612151231 SMP Thu Dec 15 17:33:37
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Mainline kernel does not fix this problem. Suspect that it's not kernel
problem, but recent change enabling auto-rotate feature triggering some
sort of input triggers resume.

On Wed, 21 Dec 2016 at 02:01 Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> ** Tags added: needs-apport-collect needs-upstream-testing
>
> ** Tags added: regression-update
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1650752
>
> Title:
>   Thinkpad Yoga 13 fails to suspend after update to  4.8.0.30.39
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650752/+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/1650752

Title:
  Thinkpad Yoga 13 fails to suspend after update to  4.8.0.30.39

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It suspends then automatically resumes a few seconds later. Latest
  kernel update brings back screen auto-rotate feature, but also breaks
  suspend. Not sure if this is related. Previous few kernel releases had
  auto-rotate feature disabled, but suspend worked properly and did not
  resume from suspend automatically.

  [  737.222140] PM: Syncing filesystems ... done.
  [  737.233688] PM: Preparing system for sleep (mem)
  [  737.234034] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  737.236194] Double checking all user space processes after OOM killer 
disable... (elapsed 0.000 seconds) 
  [  737.236333] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) 
done.
  [  737.237252] PM: Suspending system (mem)
  [  737.237283] Suspending console(s) (use no_console_suspend to debug)
  [  737.404190] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  737.406041] sd 0:0:0:0: [sda] Stopping disk
  [  738.065297] PM: suspend of devices complete after 827.881 msecs
  [  738.085132] PM: late suspend of devices complete after 19.829 msecs
  [  738.086363] xhci_hcd :00:14.0: System wakeup enabled by ACPI
  [  738.105461] PM: noirq suspend of devices complete after 20.326 msecs
  [  738.105897] ACPI: Preparing to enter system sleep state S3
  [  738.361104] ACPI : EC: EC stopped
  [  738.361105] PM: Saving platform NVS memory
  [  738.361121] Disabling non-boot CPUs ...
  [  738.361598] Broke affinity for irq 23
  [  738.361604] Broke affinity for irq 40
  [  738.361611] Broke affinity for irq 43
  [  738.363673] smpboot: CPU 1 is now offline
  [  738.386513] Broke affinity for irq 23
  [  738.386519] Broke affinity for irq 40
  [  738.386525] Broke affinity for irq 43
  [  738.386533] Broke affinity for irq 59
  [  738.387594] smpboot: CPU 2 is now offline
  [  738.418497] Broke affinity for irq 1
  [  738.418508] Broke affinity for irq 9
  [  738.418513] Broke affinity for irq 12
  [  738.418520] Broke affinity for irq 23
  [  738.418523] Broke affinity for irq 40
  [  738.418526] Broke affinity for irq 42
  [  738.418528] Broke affinity for irq 43
  [  738.418534] Broke affinity for irq 59
  [  738.419573] smpboot: CPU 3 is now offline
  [  738.440159] ACPI: Low-level resume complete
  [  738.440235] ACPI : EC: EC started
  [  738.440236] PM: Restoring platform NVS memory
  [  738.440625] Enabling non-boot CPUs ...
  [  738.463840] x86: Booting SMP configuration:
  [  738.463841] smpboot: Booting Node 0 Processor 1 APIC 0x1
  [  738.466739]  cache: parent cpu1 should not be sleeping
  [  738.466961] CPU1 is up
  [  738.487864] smpboot: Booting Node 0 Processor 2 APIC 0x2
  [  738.490555]  cache: parent cpu2 should not be sleeping
  [  738.490870] CPU2 is up
  [  738.535883] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  738.538658]  cache: parent cpu3 should not be sleeping
  [  738.539378] CPU3 is up
  [  738.549959] ACPI: Waking up from system sleep state S3
  [  739.483697] xhci_hcd :00:14.0: System wakeup disabled by ACPI
  [  739.483772] PM: noirq resume of devices complete after 32.141 msecs
  [  739.484169] PM: early resume of devices complete after 0.371 msecs
  [  739.487691] rtc_cmos 00:01: System wakeup disabled by ACPI
  [  739.488427] sd 0:0:0:0: [sda] Starting disk
  [  739.531853] xhci_hcd :00:14.0: port 4 resume PLC timeout
  [  739.547494] xhci_hcd :00:14.0: port 3 resume PLC timeout
  [  739.635640] usb 1-1.7: reset full-speed USB device number 3 using ehci-pci
  [  739.783794] usb 2-4: reset full-speed USB device number 2 using xhci_hcd
  [  739.802392] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  739.802641] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  739.802643] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  739.802723] ata1.00: ACPI cmd

[Kernel-packages] [Bug 1642044] naumann (amd64) - tests ran: 141, failed: 0

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/naumann__4.9.0-11.12__2016-12-21_01-49-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] secchi (amd64) - tests ran: 141, failed: 0

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-21_01-46-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1651622] Re: Ubuntu can try to boot from unbootable partition if UUID conflicts

2016-12-20 Thread Garth Kidd

What I think is going on: looking up the boot partition by label or
bootable flag; finding its UUID, then trying to mount it by the UUID, at
which point it's possible to get the wrong 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/1651622

Title:
  Ubuntu can try to boot from unbootable partition if UUID conflicts

Status in linux package in Ubuntu:
  New

Bug description:
  I don't think this is as specific to AWS/EC2 as it might initially
  appear, but here goes:

  To reproduce:

  * Create AWS EC2 instance using official Ubuntu 14.04 AMI
  * Use AWS EBS snapshot to clone root EBS volume to new EBS volume
  * Mount it from EC2 console
  * e2label to ensure label unique
  * fdisk to ensure partition not bootable
  * vi /etc/fstab to ensure mounted in appropriate place
  * forget to use tunefs -U to change the partition UUID
  * reboot a few times, perhaps upgrading kernel between reboots

  Expected behaviour:

  * Warnings during or after boot process that two partitions have the same UUID
  * Consistently booting from the partition labelled cloudimg-rootfs despite 
the UUID conflict
  * Consistently booting from the partition with the boot flag set despite the 
UUID conflict

  Actual behaviour:

  * No apparent warnings during or after boot process that two partitions have 
the same UUID
  * First few boots turned out fine
  * Around a month later, after a kernel upgrade from 3.13.0-92 or 105 to 106, 
started consistently booting from non-bootable partition labelled var-lib

  Console log output on problem:

  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top 
... done.
  Begin: Running /scripts/local-premount ... done.
  [2.518466] EXT4-fs (xvdf1): mounted filesystem with ordered data 
mode. Opts: (null)
  Begin: Running /scripts/local-bottom ... done.
  done.
  Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev 
failed: No such file or directory
  done.
  mount: mounting /sys on /root/sys failed: No such file or directory
  mount: mounting /proc on /root/proc failed: No such file or directory
  Target filesystem doesn't have requested /sbin/init.
  No init found. Try passing init= bootarg.

  Ops remediation of affected hosts:

  * Remount secondary EBS volume to spare host
  * tunefs /dev/xvdf1 -U `uuidgen`
  * Remount it back to the host with the outage

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-106-generic 3.13.0-106.153
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 21 01:06 seq
   crw-rw 1 root audio 116, 33 Dec 21 01:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 21 01:57:13 2016
  Ec2AMI: ami-ba3e14d9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2c
  Ec2InstanceType: c4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=63e1d5b9-1fa6-4ff3-b8d6-7a63b4b18e59 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd11/11/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651622/+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 1651622] [NEW] Ubuntu can try to boot from unbootable partition if UUID conflicts

2016-12-20 Thread Garth Kidd

Public bug reported:

I don't think this is as specific to AWS/EC2 as it might initially
appear, but here goes:

To reproduce:

* Create AWS EC2 instance using official Ubuntu 14.04 AMI
* Use AWS EBS snapshot to clone root EBS volume to new EBS volume
* Mount it from EC2 console
* e2label to ensure label unique
* fdisk to ensure partition not bootable
* vi /etc/fstab to ensure mounted in appropriate place
* forget to use tunefs -U to change the partition UUID
* reboot a few times, perhaps upgrading kernel between reboots

Expected behaviour:

* Warnings during or after boot process that two partitions have the same UUID
* Consistently booting from the partition labelled cloudimg-rootfs despite the 
UUID conflict
* Consistently booting from the partition with the boot flag set despite the 
UUID conflict

Actual behaviour:

* No apparent warnings during or after boot process that two partitions have 
the same UUID
* First few boots turned out fine
* Around a month later, after a kernel upgrade from 3.13.0-92 or 105 to 106, 
started consistently booting from non-bootable partition labelled var-lib

Console log output on problem:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
Begin: Running /scripts/local-premount ... done.
[2.518466] EXT4-fs (xvdf1): mounted filesystem with ordered data mode. 
Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev 
failed: No such file or directory
done.
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.

Ops remediation of affected hosts:

* Remount secondary EBS volume to spare host
* tunefs /dev/xvdf1 -U `uuidgen`
* Remount it back to the host with the outage

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-106-generic 3.13.0-106.153
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Dec 21 01:06 seq
 crw-rw 1 root audio 116, 33 Dec 21 01:06 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Dec 21 01:57:13 2016
Ec2AMI: ami-ba3e14d9
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: ap-southeast-2c
Ec2InstanceType: c4.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
MachineType: Xen HVM domU
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=63e1d5b9-1fa6-4ff3-b8d6-7a63b4b18e59 ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-106-generic N/A
 linux-backports-modules-3.13.0-106-generic  N/A
 linux-firmware  N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2016
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd11/11/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen

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


** Tags: amd64 apport-bug ec2-images trusty

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

Title:
  Ubuntu can try to boot from unbootable partition if UUID conflicts

Status in linux package in Ubuntu:
  New

Bug description:
  I don't think this is as specific to AWS/EC2 as it might initially
  appear, but here goes:

  To reproduce:

  * Create AWS EC2 instance using official Ubuntu 14.04 AMI
  * Use AWS EBS snapshot to clone root EBS volume to new EBS volume
  * Mount it from EC2 console
  * e2label to ensure label unique
  * fdisk to ensure partition not bootable
  * vi /etc/fstab to ensure mounted in appropriate place
  * forget to use tunefs -U to change the partition UUID
  * reboot a few times, perhaps upgrading kernel between reboots

  Expected behaviour:

  * Warnings during or after boot process that two partitions have the same

[Kernel-packages] [Bug 1651534] Re: linux: 3.19.0-79.87 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => 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/1651534

Title:
  linux: 3.19.0-79.87 -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:
  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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 3.19.0-79.87 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

  kernel-stable-phase-changed:Tuesday, 20. December 2016 17:45 UTC
  kernel-stable-phase:Packaging

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651534/+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

2016-12-20 Thread Sabin Iacob

in my case I have to do rmmod btusb; modprobe btusb


it looks to me like every new release of Ubuntu manages to break Bluetooth 
audio in some way that is new and creative and ever-increasingly difficult to 
automate away: 
 * 14.10 and before - volume wouldn't be restored, sink wouldn't switch; solved 
by having a script listen to dbus for a headphone connection event and tell 
pulseaudio to set the default sink and restore volume
 * 15.04 - no sound unless I disconnected and reconnected again; put that in a 
script
 * 15.10 - needed to connect manually, but at least the rest worked; solved by 
having a script look if the phones are connected, do a l2ping to see if they 
are available and connect; occasionally I'd have to rmmod btusb; modprobe btusb
 * 16.04 - this issue; I only managed to upgrade yesterday, I still haven't 
found a pattern to this madness


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

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

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-21_00-32-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] naumann (amd64) - tests ran: 19, failed: 0

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/naumann__4.9.0-11.12__2016-12-21_00-32-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1647826] Update Released

2016-12-20 Thread Chris Halse Rogers

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

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

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+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 1646197] Re: Update initrds after installing linux-firmware

This bug was fixed in the package linux-firmware - 1.161.1

---
linux-firmware (1.161.1) yakkety; urgency=medium

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

  * Intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode

 -- Seth Forshee   Tue, 06 Dec 2016 14:42:47
-0600

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

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

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Precise:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Released

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1646197/+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 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

This bug was fixed in the package linux-firmware - 1.161.1

---
linux-firmware (1.161.1) yakkety; urgency=medium

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

  * Intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode

 -- Seth Forshee   Tue, 06 Dec 2016 14:42:47
-0600

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

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

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

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

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+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 1642709] Re: Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

This bug was fixed in the package linux-firmware - 1.127.23

---
linux-firmware (1.127.23) trusty; urgency=medium

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

  * Add i915/skl_guc_ver6.bin to linux-firmware in Trusty (LP: #1642709)
- linux-firmware/i915: Major GuC release for Skylake - ver 6.1

 -- Seth Forshee   Thu, 01 Dec 2016 15:36:41
-0600

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

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

Title:
  Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Released

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

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

2016-12-20 Thread Chris Halse Rogers

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Released

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1642709/+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 1646197] Re: Update initrds after installing linux-firmware

This bug was fixed in the package linux-firmware - 1.127.23

---
linux-firmware (1.127.23) trusty; urgency=medium

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

  * Add i915/skl_guc_ver6.bin to linux-firmware in Trusty (LP: #1642709)
- linux-firmware/i915: Major GuC release for Skylake - ver 6.1

 -- Seth Forshee   Thu, 01 Dec 2016 15:36:41
-0600

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

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

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Precise:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Released

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1646197/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2016-12-20 Thread Jimmy Pan

@lpturoyo,

Do you need to install Nvidia drivers and does it mean you cannot update
any packages? Also after installing the new kernel, does it only has
shutdown problem or it also has boot problem.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31

[Kernel-packages] [Bug 1642114] Re: ThinkPad T460 hotkeys stop working in Ubuntu 16.04

2016-12-20 Thread Alex Hung

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

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

Title:
  ThinkPad T460 hotkeys stop working in Ubuntu 16.04

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

Bug description:
  Hotkeys of ThinkPad T460 no longer works in Ubuntu 16.04, and dmesg
  shows an thinkpad_acpi: unknown version of the HKEY interface: 0x200.

  Commit 0118c2d3eac0545d4095877e5a015b5dc763b3c2 is required to support
  HKEY interface 0x200

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1642114/+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 1642044] secchi (amd64) - tests ran: 36, failed: 0

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-20_22-37-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] naumann (amd64) - tests ran: 36, failed: 0

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/naumann__4.9.0-11.12__2016-12-20_22-37-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1651598] Missing required logs.

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

apport-collect 1651598

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

Title:
  Last update (to 4.8.0-32.34) freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During last update/upgrade, process freeze on executing
  /etc/kernel/postinst.d/dkms 4.8.0-32-generic
  /boot/vmlinuz-4.8.0-32-generic. After an hour, I interrupt it and run
  sudo apt update && sudo apt upgrade again, but still with out any
  effects. (Of course I remove locks and run sudo dpkg --configure -a
  before). Even reboot don't change anything.

  I have x64 Ubuntu 16.10 with kernel 4.8.0-30-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651598/+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 1651598] Re: Last update (to 4.8.0-32.34) freeze

2016-12-20 Thread Bozydar

** Description changed:

  During last update/upgrade, process freeze on executing
  /etc/kernel/postinst.d/dkms 4.8.0-32-generic
  /boot/vmlinuz-4.8.0-32-generic. After an hour, I interrupt it and run
  sudo apt update && sudo apt upgrade again, but still with out any
  effects. (Of course I remove locks and run sudo dpkg --configure -a
  before). Even reboot don't change anything.
+ 
+ I have x64 Ubuntu 16.10 with kernel 4.8.0-30-generic.

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

Title:
  Last update (to 4.8.0-32.34) freeze

Status in linux package in Ubuntu:
  New

Bug description:
  During last update/upgrade, process freeze on executing
  /etc/kernel/postinst.d/dkms 4.8.0-32-generic
  /boot/vmlinuz-4.8.0-32-generic. After an hour, I interrupt it and run
  sudo apt update && sudo apt upgrade again, but still with out any
  effects. (Of course I remove locks and run sudo dpkg --configure -a
  before). Even reboot don't change anything.

  I have x64 Ubuntu 16.10 with kernel 4.8.0-30-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651598/+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 1651598] [NEW] Last update (to 4.8.0-32.34) freeze

2016-12-20 Thread Bozydar

Public bug reported:

During last update/upgrade, process freeze on executing
/etc/kernel/postinst.d/dkms 4.8.0-32-generic
/boot/vmlinuz-4.8.0-32-generic. After an hour, I interrupt it and run
sudo apt update && sudo apt upgrade again, but still with out any
effects. (Of course I remove locks and run sudo dpkg --configure -a
before). Even reboot don't change anything.

I have x64 Ubuntu 16.10 with kernel 4.8.0-30-generic.

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

** Attachment added: "Screenshot from terminal (result of command: sudo apt
update && sudo apt upgrade -y)"

https://bugs.launchpad.net/bugs/1651598/+attachment/4794477/+files/Screen_2016-12-21_00-02-24.png

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

Title:
Last update (to 4.8.0-32.34) freeze

Status in linux package in Ubuntu:
New

Bug description:
During last update/upgrade, process freeze on executing
/etc/kernel/postinst.d/dkms 4.8.0-32-generic
/boot/vmlinuz-4.8.0-32-generic. After an hour, I interrupt it and run
sudo apt update && sudo apt upgrade again, but still with out any
effects. (Of course I remove locks and run sudo dpkg --configure -a
before). Even reboot don't change anything.

I have x64 Ubuntu 16.10 with kernel 4.8.0-30-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651598/+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 1651124] Re: Please merge dkms 2.3-1 from Debian testing (main)

2016-12-20 Thread Mathew Hodson

** Changed in: dkms (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
   Please merge dkms 2.3-1 from Debian testing  (main)

Status in dkms package in Ubuntu:
  New

Bug description:
  dkms upstream has become back to life in recent months, and merged
  many patches from downstream communities, thus merging with the new
  release is worthy to get old bug fixed and new features incorporated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1651124/+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 1642044] naumann (amd64) - tests ran: 7, failed: 3

tests ran:   7, failed: 3;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/naumann__4.9.0-11.12__2016-12-20_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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1642044] secchi (amd64) - tests ran: 7, failed: 4

tests ran:   7, failed: 4;
  
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-20_18-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.9.0-6.7 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/1642044/+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 1651211] Re: linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

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

** Description changed:

  This bug is for tracking the  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: 1651207
  phase: Packaging

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

Title:
  linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  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: 1651207
  phase: Packaging

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-58.79-lowlatency/onza__4.4.0-58.79__2016-12-20_21-33-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/1651402

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651402/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-12-20 Thread Mohamed A.

I updated to 4.9.0 kernel. Bug still persisting.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1651207] Re: linux: 3.2.0-120.163 -proposed tracker

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

** Description changed:

  This bug is for tracking the 3.2.0-120.163 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
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. December 2016 18:34 UTC
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

Title:
  linux: 3.2.0-120.163 -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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta 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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 3.2.0-120.163 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. December 2016 18:34 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651207/+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 1651207] Re: linux: 3.2.0-120.163 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: Confirmed => 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/1651207

Title:
  linux: 3.2.0-120.163 -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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta 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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 3.2.0-120.163 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 19. December 2016 18:34 UTC

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651207/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2016-12-20 Thread turoyo dee

@penalvch , I have to ask why the issue is closed, since this was reported for 
16.04 LTS.
and the recommended solution requires kernel 4.9, which is not even scheduled 
for next point release [16.04.2 - 4.8].

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  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.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/onza__4.4.0-58.79__2016-12-20_20-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/1651402

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651402/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2016-12-20 Thread turoyo dee

@seccanj , I have experienced this same issue and was able to solve with
the same steps.


 - install 16.04.1

 - get intel-microcode from "unity" -> "additional drivers"

 - blacklist nouveau

 - $ update init-ramfs -u


this resolves boot and shutdown lockup.

however, I've accidentally updated the kernel twice after resolving it
with these steps.

and in both cases, even after uninstalling the new kernel [ even latest 
4.4.0-53]
the issue returns randomly on boot and even once on shutdown


[I'm using Dell 7559 6700HQ]
* also using acpi_osi="!Windows 2015" does not resolve this

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [

[Kernel-packages] [Bug 1651402] modoc (ppc64el) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/modoc__4.4.0-58.79__2016-12-20_20-20-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/1651402

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/onza__4.4.0-58.79__2016-12-20_20-10-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/1651402

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651402/+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 1642739] Re: Kernel panic on shutdown

2016-12-20 Thread Joseph Salisbury

That is good news.  That means Yakkety will get that revert when it
receives the 4.8.15 upstream updates.


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

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

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

Title:
  Kernel panic on shutdown

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

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642739/+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 1651402] Re: linux: 4.4.0-58.79 -proposed tracker

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp6g001__4.4.0-57.78__2016-12-20_19-47-00/results-index.html

** 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) => Luis Henriques 
(henrix)

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

** Description changed:

  This bug is for tracking the 4.4.0-58.79 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
+ kernel-stable-phase-changed:Tuesday, 20. December 2016 19:46 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.4.0-58.79 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: Uploaded
- kernel-stable-phase-changed:Tuesday, 20. December 2016 19:46 UTC
- kernel-stable-phase:Uploaded

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

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651402/+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 1650918] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!

2016-12-20 Thread Cristian Aravena Romero

Joseph Salisbury,

Please, create kernel (Ubuntu 4.9.0-11.12-generic 4.9.0) + patch :
https://bugzilla.kernel.org/show_bug.cgi?id=111291#c9
https://osdn.net/users/ysato/pf/linux_sh/scm/commits/b50bde4e476dede4a28e9c8fdcd134da2f34ef2e


Laurent Pinchart 2016-09-30 10:45:38 UTC
This is a known issue, caused by

commit b50bde4e476dede4a28e9c8fdcd134da2f34ef2e
Author: Mauro Carvalho Chehab 
Date:   Thu May 7 22:12:38 2015 -0300

[media] v4l2-subdev: use MEDIA_ENT_T_UNKNOWN for new subdevs

Instead of abusing MEDIA_ENT_T_V4L2_SUBDEV, initialize
new subdev entities as MEDIA_ENT_T_UNKNOWN.

Acked-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab 

that added a warning to media controller core code without updating
drivers to comply with the new requirements.

The warning is harmless, drivers will eventually be updated.

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

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

Title:
  uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not
  initialized!

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [5.889135] uvcvideo: Found UVC 1.00 device WebCam SC-13HDL12131N 
(2232:1035)
  [5.913016] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
  [5.913028] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was 
not initialized!
  [5.913032] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2073 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2073 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Dec 18 13:37:57 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (511 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.9.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago)
  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/linux/+bug/1650918/+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 1651402] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp3__4.4.0-57.78__2016-12-20_19-49-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/1651402

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-20_19-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/1651402

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651402/+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 1611536] Re: Fan on full speed without noapic or nolapic on HP 6715s

2016-12-20 Thread Carl Englund

I scrapped the two 6715s I had and can no longer test them.

/ Carl

Den 20 dec 2016 18:25 skrev "Christopher M. Penalver" <
christopher.m.penal...@gmail.com>:

> Carl Englund, please see
> https://community.ubuntu.com/contribute/support/irc/ .
>
> In addition to the bisect, to keep this relevant to upstream, one would
> want to periodically check for, and test the latest mainline kernel (now
> 4.9) as it is released.
>
> Could you please advise?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1611536
>
> Title:
>   Fan on full speed without noapic or nolapic on HP 6715s
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1611536/+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/1611536

Title:
  Fan on full speed without noapic or nolapic on HP 6715s

Status in linux package in Ubuntu:
  Expired

Bug description:
  Without adding noapic or nolapic to boot parameters the fan will run
  on full speed, the system is sluggish (can almost see windows
  redrawing on screen). On some kernel versions tested, rebooting also
  fails.

  The parameter(s) were not required in Trusty. I also tested some
  Mainline kernels and discovered 3.19.8 and 4.0.9 works without the
  parameters. At least 4.1.29 and onward requires noapic or nolapic for
  this machine to work properly but I have yet to investigate the
  versions between 4.0.9 and 4.1.29.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diskdoc2700 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Aug 10 01:15:07 2016
  HibernationDevice: RESUME=UUID=522810df-638a-412b-9aab-791e2e2bc545
  InstallationDate: Installed on 2016-06-07 (63 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Compaq 6715s (RU655ET#AK8)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=3a37ee65-4c02-4a95-b814-f4538a4a308d ro quiet splash noapic 
acpi_force_32bit_fadt_addr vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YTT Ver. F.20
  dmi.board.name: 30C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2D
  dmi.chassis.asset.tag: CNU7201T8J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YTTVer.F.20:bd12/01/2011:svnHewlett-Packard:pnHPCompaq6715s(RU655ET#AK8):pvrF.20:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6715s (RU655ET#AK8)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/+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 1625116] Re: RT3290 not working

2016-12-20 Thread Joseph Salisbury

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 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.9


** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1625116

Title:
  RT3290 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My WiFi RT3290 does not work on Ubuntu. Neither I remember it working
  on any previous version. I don't have good knowledge of command line
  or linux. But I am using ubuntu as my primary OS. Currently I am using
  usb wifi adapter to connect to internet. I have followed almost every
  guide available on internet like downloading driver from mediatek
  website or someone's dropbox folder and then compiling or changing
  linux kernels. I don't know why still I can't make it work. I want
  this device to work out of box for next ubuntu version. Let me know if
  you need any further information about collecting logs of my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  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
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 19 15:45:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-07 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlxaca2131a2daf  proto static  metric 600 
   169.254.0.0/16 dev wlxaca2131a2daf  scope link  metric 1000 
   192.168.0.0/24 dev wlxaca2131a2daf  proto kernel  scope link  src 
192.168.0.109  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH   

   wlxaca2131a2daf  wifi  connected
/org/freedesktop/NetworkManager/Devices/2  UnitedNepal  
ff526f85-e18b-4713-ae67-f3fbfa290c4b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp1s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/0  --   --  
  -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625116/+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 1651435] Re: BTRFS error: could not find root 8

2016-12-20 Thread Joseph Salisbury

Please change the status back to "Confirmed" if the bug happens again.

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

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

** Tags added: kernel-da-key

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

Title:
  BTRFS error: could not find root 8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a KVM guest system which was running for some time now (142
  days uptime).

  Today, I logged in for the first time since months, and got an error
  message in syslog (and console):

  kernel: BTRFS error (device vda2): could not find root 8

  The error happened together with my login (in respect to the date of
  the log entry).

  The system was running with kernel 4.4.0-31-generic when the problem
  occured.

  When googling around, I found some similar results, but nowhere is
  mentioned that this got fixed somehow.

  So far, I could not find anything harmful (I did not reboot yet,
  however).

  I updated the kernel now, eventually that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Dec 20 13:00 seq
   crw-rw+ 1 root audio 116, 33 Dec 20 13:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Dec 20 13:40:44 2016
  HibernationDevice: RESUME=UUID=419693f3-cd92-4870-a16a-7bede16d9b8a
  InstallationDate: Installed on 2016-06-20 (182 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=ebfbbec2-f4df-4e40-92a5-3db6b57eb8f5 ro rootflags=subvol=@
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20140531_083030-gandalf
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20140531_083030-gandalf:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.1:cvnQEMU:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651435/+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 1649358] Re: linux: 4.8.0-32.34 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the 4.8.0-32.34 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
+ kernel-stable-phase-changed:Tuesday, 20. December 2016 19:34 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.8.0-32.34 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Tuesday, 20. December 2016 19:34 UTC
- kernel-stable-phase: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/1649358

Title:
  linux: 4.8.0-32.34 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-32.34 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1649358/+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 1650607] Re: Xenial update to v4.4.38 stable release

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

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

Title:
  Xenial update to v4.4.38 stable release

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

Bug description:
  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.38 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.38 stable release shall be
  applied:

  virtio-net: add a missing synchronize_net()
  net: check dead netns for peernet2id_alloc()
  ip6_tunnel: disable caching when the traffic class is inherited
  net: sky2: Fix shutdown crash
  af_unix: conditionally use freezable blocking calls in read
  rtnetlink: fix FDB size computation
  l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind()
  net: dsa: bcm_sf2: Ensure we re-negotiate EEE during after link change
  net, sched: respect rcu grace period on cls destruction
  net/sched: pedit: make sure that offset is valid
  netlink: Call cb->done from a worker thread
  netlink: Do not schedule work from sk_destruct
  net/dccp: fix use-after-free in dccp_invalid_packet
  net: bcmgenet: Utilize correct struct device for all DMA operations
  sh_eth: remove unchecked interrupts for RZ/A1
  geneve: avoid use-after-free of skb->data
  net: ping: check minimum size on ICMP header length
  sparc32: Fix inverted invalid_frame_pointer checks on sigreturns
  sparc64: Fix find_node warning if numa node cannot be found
  sparc64: fix compile warning section mismatch in find_node()
  constify iov_iter_count() and iter_is_iovec()
  Don't feed anything but regular iovec's to blk_rq_map_user_iov
  ipv6: Set skb->protocol properly for local output
  ipv4: Set skb->protocol properly for local output
  esp4: Fix integrity verification when ESN are used
  esp6: Fix integrity verification when ESN are used
  Linux 4.4.38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650607/+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 1650607] Re: Xenial update to v4.4.38 stable release

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

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

Title:
  Xenial update to v4.4.38 stable release

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

Bug description:
  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.38 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.38 stable release shall be
  applied:

  virtio-net: add a missing synchronize_net()
  net: check dead netns for peernet2id_alloc()
  ip6_tunnel: disable caching when the traffic class is inherited
  net: sky2: Fix shutdown crash
  af_unix: conditionally use freezable blocking calls in read
  rtnetlink: fix FDB size computation
  l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind()
  net: dsa: bcm_sf2: Ensure we re-negotiate EEE during after link change
  net, sched: respect rcu grace period on cls destruction
  net/sched: pedit: make sure that offset is valid
  netlink: Call cb->done from a worker thread
  netlink: Do not schedule work from sk_destruct
  net/dccp: fix use-after-free in dccp_invalid_packet
  net: bcmgenet: Utilize correct struct device for all DMA operations
  sh_eth: remove unchecked interrupts for RZ/A1
  geneve: avoid use-after-free of skb->data
  net: ping: check minimum size on ICMP header length
  sparc32: Fix inverted invalid_frame_pointer checks on sigreturns
  sparc64: Fix find_node warning if numa node cannot be found
  sparc64: fix compile warning section mismatch in find_node()
  constify iov_iter_count() and iter_is_iovec()
  Don't feed anything but regular iovec's to blk_rq_map_user_iov
  ipv6: Set skb->protocol properly for local output
  ipv4: Set skb->protocol properly for local output
  esp4: Fix integrity verification when ESN are used
  esp6: Fix integrity verification when ESN are used
  Linux 4.4.38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650607/+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 1650609] Re: Xenial update to v4.4.39 stable release

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

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

Title:
  Xenial update to v4.4.39 stable release

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

Bug description:
  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.39 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.39 stable release shall be
  applied:

  powerpc/eeh: Fix deadlock when PE frozen state can't be cleared
  parisc: Purge TLB before setting PTE
  parisc: Remove unnecessary TLB purges from flush_dcache_page_asm and 
flush_icache_page_asm
  parisc: Fix TLB related boot crash on SMP machines
  zram: restrict add/remove attributes to root only
  locking/rtmutex: Prevent dequeue vs. unlock race
  locking/rtmutex: Use READ_ONCE() in rt_mutex_owner()
  perf/x86: Fix full width counter, counter overflow
  crypto: mcryptd - Check mcryptd algorithm compatibility
  can: raw: raw_setsockopt: limit number of can_filter that can be set
  can: peak: fix bad memory access and free sequence
  arm64: futex.h: Add missing PAN toggling
  m68k: Fix ndelay() macro
  batman-adv: Check for alloc errors when preparing TT local data
  hotplug: Make register and unregister notifier API symmetric
  crypto: rsa - Add Makefile dependencies to fix parallel builds
  Linux 4.4.39

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650609/+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 1650609] Re: Xenial update to v4.4.39 stable release

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

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

Title:
  Xenial update to v4.4.39 stable release

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

Bug description:
  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.39 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.39 stable release shall be
  applied:

  powerpc/eeh: Fix deadlock when PE frozen state can't be cleared
  parisc: Purge TLB before setting PTE
  parisc: Remove unnecessary TLB purges from flush_dcache_page_asm and 
flush_icache_page_asm
  parisc: Fix TLB related boot crash on SMP machines
  zram: restrict add/remove attributes to root only
  locking/rtmutex: Prevent dequeue vs. unlock race
  locking/rtmutex: Use READ_ONCE() in rt_mutex_owner()
  perf/x86: Fix full width counter, counter overflow
  crypto: mcryptd - Check mcryptd algorithm compatibility
  can: raw: raw_setsockopt: limit number of can_filter that can be set
  can: peak: fix bad memory access and free sequence
  arm64: futex.h: Add missing PAN toggling
  m68k: Fix ndelay() macro
  batman-adv: Check for alloc errors when preparing TT local data
  hotplug: Make register and unregister notifier API symmetric
  crypto: rsa - Add Makefile dependencies to fix parallel builds
  Linux 4.4.39

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650609/+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 1650750] Re: bluetooth connection keeps getting turned off after update

jerrylamos, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650750/comments/4
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

Title:
  bluetooth connection keeps getting turned off after update

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Turn bluetooth connection on with mouse selection and linux keeps turning it 
off.
  Anker A7721 keyboard running fine before update today and fine on other 
ubuntu partitions.
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
  Linux Lenovo2 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  model name: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
  model name: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Dec 17 07:54:58 2016
  InstallationDate: Installed on 2016-11-23 (23 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161123)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=0047f86e-07a4-4c9d-bed1-2fb8d196b8b3 ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650750/+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 1643341] Re: Unexpected shutdown

Sam_, to clarify, you did, or did not test Zesty within the last day?

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

Title:
  Unexpected shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This happens twice in between a short time, 2-5 minutes, after the computer 
was turned on and Ubuntu desktop has started.
  It never happens a third time.
  From Ubuntu desktop, the cooler starts to run, a shutdown dialog with four 
options appears and computer turns off.
  I turn it on again and watch the same procedure happen again.
  I turn it on the third time, all is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68 and 4.4.0-49.70
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zootie 1897 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov 20 17:19:01 2016
  HibernationDevice: RESUME=UUID=6a848b08-24f4-499b-8281-8ba10097226d
  InstallationDate: Installed on 2016-11-02 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160823)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 5986:055c Acer, Inc
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=31f6cc2f-d9df-473c-be2d-fd1abf719500 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RB
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/16/2015:svnNotebook:pnW65_W67RB:pvrNotApplicable:rvnNotebook:rnW65_W67RB:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65_W67RB
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643341/+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 1637709] Re: Lenovo Ideapad 100 webcam always on

2016-12-20 Thread Michael Devenish

I was having the same issue with my Lenovo ideapad 100 (also model 15IBD
80 QQ) running Ubuntu-mate 16.04 LTS. However, when trying to get an
image to display in Cheese, I found there was no display until I clicked
preferences and changed the photo and video resolution both to 320x240.
Then the webcam displayed an image but was very slow. After closing
Cheese, the problem with the webcam led always being on has gone away.
It's on briefly when booting up, then goes off once I've logged on and
the desktop is loaded. I've re-booted several times now and the webcam
led is off, unless an application requires it. I don't think I'd updated
the kernel at the same time, but I might be 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/1637709

Title:
  Lenovo Ideapad 100 webcam always on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovo Ideapad 100 model 15IBD 80 QQ
  The webcam led it stays always on from when i start the pc, it stops only, it 
seems, when i open some software that has a working with it in some way...like  
software or even google chrome (i think thanks to hangouts)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1361 F pulseaudio
   /dev/snd/controlC1:  ale1361 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=39a50866-e309-4acc-b70f-19f745ab0c9e
  InstallationDate: Installed on 2016-10-22 (6 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80QQ
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=86cd71e4-1562-488f-afa6-290f354d4f7a ro
  ProcVersionSignature: Ubuntu 4.4.0-45.66-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-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN61WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 5B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN61WW:bd08/12/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
  dmi.product.name: 80QQ
  dmi.product.version: Lenovo ideapad 100-15IBD
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637709/+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 1651211] Re: linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

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

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

Title:
  linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  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: 1651207
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1651211/+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 1647717] Re: linux-ti-omap4: 3.2.0-1497.124 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  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: 1647713
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 20. December 2016 19:02 UTC

** Description changed:

  This bug is for tracking the  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: 1647713
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Tuesday, 20. December 2016 19:02 UTC

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

Title:
  linux-ti-omap4: 3.2.0-1497.124 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released

Bug description:
  This bug is for tracking the  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: 1647713
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the 4.4.0-57.78 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
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 20. December 2016 19:16 UTC

** Description changed:

  This bug is for tracking the 4.4.0-57.78 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Tuesday, 20. December 2016 19:16 UTC

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-57.78 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648867/+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 1643639] Re: Yakkety update to 4.8.10 stable release

This bug was fixed in the package linux - 4.8.0-32.34

---
linux (4.8.0-32.34) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1649358

  * Vulnerability picked up from 4.8.10 stable kernel (LP: #1648662)
- net: handle no dst on skb in icmp6_send

linux (4.8.0-31.33) yakkety; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648034

  * Update hio driver to 2.1.0.28 (LP: #1646643)
- SAUCE: hio: update to Huawei ES3000_V2 (2.1.0.28)

  * Yakkety update to v4.8.11 stable release (LP: #1645421)
- x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems
- KVM: x86: fix missed SRCU usage in kvm_lapic_set_vapic_addr
- KVM: Disable irq while unregistering user notifier
- arm64: KVM: pmu: Fix AArch32 cycle counter access
- KVM: arm64: Fix the issues when guest PMCCFILTR is configured
- ftrace: Ignore FTRACE_FL_DISABLED while walking dyn_ftrace records
- ftrace: Add more checks for FTRACE_FL_DISABLED in processing ip records
- genirq: Use irq type from irqdata instead of irqdesc
- fuse: fix fuse_write_end() if zero bytes were copied
- IB/rdmavt: rdmavt can handle non aligned page maps
- IB/hfi1: Fix rnr_timer addition
- mfd: intel-lpss: Do not put device in reset state on suspend
- mfd: stmpe: Fix RESET regression on STMPE2401
- can: bcm: fix warning in bcm_connect/proc_register
- gpio: do not double-check direction on sleeping chips
- ALSA: usb-audio: Fix use-after-free of usb_device at disconnect
- ALSA: hda - add a new condition to check if it is thinkpad
- ALSA: hda - Fix mic regression by ASRock mobo fixup
- i2c: mux: fix up dependencies
- i2c: i2c-mux-pca954x: fix deselect enabling for device-tree
- Disable the __builtin_return_address() warning globally after all
- kbuild: add -fno-PIE
- scripts/has-stack-protector: add -fno-PIE
- x86/kexec: add -fno-PIE
- kbuild: Steal gcc's pie from the very beginning
- ext4: sanity check the block and cluster size at mount time
- ARM: dts: imx53-qsb: Fix regulator constraints
- crypto: caam - do not register AES-XTS mode on LP units
- powerpc/64: Fix setting of AIL in hypervisor mode
- drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)
- drm/i915: Refresh that status of MST capable connectors in ->detect()
- drm/i915: Assume non-DP++ port if dvo_port is HDMI and there's no AUX ch
  specified in the VBT
- virtio-net: drop legacy features in virtio 1 mode
- clk: mmp: pxa910: fix return value check in pxa910_clk_init()
- clk: mmp: pxa168: fix return value check in pxa168_clk_init()
- clk: mmp: mmp2: fix return value check in mmp2_clk_init()
- clk: imx: fix integer overflow in AV PLL round rate
- rtc: omap: Fix selecting external osc
- iwlwifi: pcie: fix SPLC structure parsing
- iwlwifi: pcie: mark command queue lock with separate lockdep class
- iwlwifi: mvm: fix netdetect starting/stopping for unified images
- iwlwifi: mvm: fix d3_test with unified D0/D3 images
- iwlwifi: mvm: wake the wait queue when the RX sync counter is zero
- mfd: core: Fix device reference leak in mfd_clone_cell
- sunrpc: svc_age_temp_xprts_now should not call setsockopt non-tcp 
transports
- uwb: fix device reference leaks
- PM / sleep: fix device reference leak in test_suspend
- PM / sleep: don't suspend parent when async child suspend_{noirq, late}
  fails
- perf hists: Fix column length on --hierarchy
- IB/rxe: Update qp state for user query
- IB/rxe: Fix kernel panic in UDP tunnel with GRO and RX checksum
- IB/rxe: Fix handling of erroneous WR
- IB/rxe: Clear queue buffer when modifying QP to reset
- IB/mlx4: Check gid_index return value
- IB/mlx4: Fix create CQ error flow
- IB/mlx5: Validate requested RQT size
- IB/mlx5: Use cache line size to select CQE stride
- IB/mlx5: Fix memory leak in query device
- IB/mlx5: Fix fatal error dispatching
- IB/mlx5: Fix NULL pointer dereference on debug print
- IB/core: Avoid unsigned int overflow in sg_alloc_table
- IB/hfi1: Remove incorrect IS_ERR check
- IB/uverbs: Fix leak of XRC target QPs
- IB/cm: Mark stale CM id's whenever the mad agent was unregistered
- netfilter: nft_dynset: fix element timeout for HZ != 1000
- gpio: pca953x: Move memcpy into mutex lock for set multiple
- gpio: pca953x: Fix corruption of other gpios in set_multiple.
- Linux 4.8.11

  * Upstream stable 4.4.34 and 4.8.10 regression (LP: #1645278)
- flow_dissect: call init_default_flow_dissectors() earlier

  * Fix Kernel Crashing under IBM Virtual Scsi Driver (LP: #1642299)
- SAUCE: ibmvscsis: Rearrange functions for future patches
- SAUCE: ibmvscsis: Synchronize cmds at tpg_enable_store time
- SAUCE: ibmvscsis: Synchronize cmds at remove time
- SAUCE: ibmvscsis: Clean up properly if

[Kernel-packages] [Bug 1642258] Re: ST Micro lps22hb pressure sensor support

This bug was fixed in the package linux - 4.4.0-57.78

---
linux (4.4.0-57.78) xenial; urgency=low

  * Release Tracking Bug
- LP: #1648867

  * Miscellaneous Ubuntu changes
- SAUCE: Do not build the xr-usb-serial driver for s390

linux (4.4.0-56.77) xenial; urgency=low

  * Release Tracking Bug
- LP: #1648867

  * Release Tracking Bug
- LP: #1648579

  * CONFIG_NR_CPUS=256 is too low (LP: #1579205)
- [Config] Increase the NR_CPUS to 512 for amd64 to support systems with a
  large number of cores.

  * NVMe drives in Amazon AWS instance fail to initialize (LP: #1648449)
- SAUCE: (no-up) NVMe: only setup MSIX once

linux (4.4.0-55.76) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648503

  * NVMe driver accidentally reverted to use GSI instead of MSIX (LP: #1647887)
- (fix) NVMe: restore code to always use MSI/MSI-x interrupts

linux (4.4.0-54.75) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648017

  * Update hio driver to 2.1.0.28 (LP: #1646643)
- SAUCE: hio: update to Huawei ES3000_V2 (2.1.0.28)

  * linux: Enable live patching for all supported architectures (LP: #1633577)
- [Config] CONFIG_LIVEPATCH=y for s390x

  * Botched backport breaks level triggered EOIs in QEMU guests with --machine
kernel_irqchip=split (LP: #1644394)
- kvm/irqchip: kvm_arch_irq_routing_update renaming split

  * Xenial update to v4.4.35 stable release (LP: #1645453)
- x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems
- KVM: x86: fix missed SRCU usage in kvm_lapic_set_vapic_addr
- KVM: Disable irq while unregistering user notifier
- fuse: fix fuse_write_end() if zero bytes were copied
- mfd: intel-lpss: Do not put device in reset state on suspend
- can: bcm: fix warning in bcm_connect/proc_register
- i2c: mux: fix up dependencies
- kbuild: add -fno-PIE
- scripts/has-stack-protector: add -fno-PIE
- x86/kexec: add -fno-PIE
- kbuild: Steal gcc's pie from the very beginning
- ext4: sanity check the block and cluster size at mount time
- crypto: caam - do not register AES-XTS mode on LP units
- drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)
- clk: mmp: pxa910: fix return value check in pxa910_clk_init()
- clk: mmp: pxa168: fix return value check in pxa168_clk_init()
- clk: mmp: mmp2: fix return value check in mmp2_clk_init()
- rtc: omap: Fix selecting external osc
- iwlwifi: pcie: fix SPLC structure parsing
- mfd: core: Fix device reference leak in mfd_clone_cell
- uwb: fix device reference leaks
- PM / sleep: fix device reference leak in test_suspend
- PM / sleep: don't suspend parent when async child suspend_{noirq, late}
  fails
- IB/mlx4: Check gid_index return value
- IB/mlx4: Fix create CQ error flow
- IB/mlx5: Use cache line size to select CQE stride
- IB/mlx5: Fix fatal error dispatching
- IB/core: Avoid unsigned int overflow in sg_alloc_table
- IB/uverbs: Fix leak of XRC target QPs
- IB/cm: Mark stale CM id's whenever the mad agent was unregistered
- netfilter: nft_dynset: fix element timeout for HZ != 1000
- Linux 4.4.35

  * Upstream stable 4.4.34 and 4.8.10 regression (LP: #1645278)
- flow_dissect: call init_default_flow_dissectors() earlier

  * AD5593R configurable multi-channel converter support (LP: #1644726)
- iio: dac: Add support for the AD5592R/AD5593R ADCs/DACs
- iio: dac: ad5592r: Off by one bug in ad5592r_alloc_channels()
- [Config] CONFIG_AD5592R/AD5593R=m

  * ST Micro lps22hb pressure sensor support (LP: #1642258)
- iio:st_pressure:initial lps22hb sensor support
- iio:st_pressure: align storagebits on power of 2
- iio:st_pressure: document sampling gains
- iio:st_pressure:lps22hb: temperature support

  * Fix Kernel Crashing under IBM Virtual Scsi Driver (LP: #1642299)
- SAUCE: ibmvscsis: Rearrange functions for future patches
- SAUCE: ibmvscsis: Synchronize cmds at tpg_enable_store time
- SAUCE: ibmvscsis: Synchronize cmds at remove time
- SAUCE: ibmvscsis: Clean up properly if target_submit_cmd/tmr fails
- SAUCE: ibmvscsis: Return correct partition name/# to client
- SAUCE: ibmvscsis: Issues from Dan Carpenter/Smatch

  * System stalls when creating device node on booting (LP: #1643797)
- sched/fair: Fix new task's load avg removed from source CPU in
  wake_up_new_task()

  * nvme: improve performance for virtual Google NVMe devices (LP: #1637565)
- blk-mq: add blk_mq_alloc_request_hctx
- nvme.h: add NVMe over Fabrics definitions
- [Config] CONFIG_NVME_VENDOR_EXT_GOOGLE=y
- SAUCE: nvme: improve performance for virtual NVMe devices

  * Move some kernel modules to the main kernel package (LP: #1642228)
- [Config] Move some powerpc kernel modules to the main kernel package

  * sched: Match-all classifier is missing in xenial (LP: #1642514)
-

[Kernel-packages] [Bug 1640109] Re: hv_set_ifconfig script parsing fails for certain configuration

This bug was fixed in the package linux - 4.8.0-32.34

---
linux (4.8.0-32.34) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1649358

  * Vulnerability picked up from 4.8.10 stable kernel (LP: #1648662)
- net: handle no dst on skb in icmp6_send

linux (4.8.0-31.33) yakkety; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648034

  * Update hio driver to 2.1.0.28 (LP: #1646643)
- SAUCE: hio: update to Huawei ES3000_V2 (2.1.0.28)

  * Yakkety update to v4.8.11 stable release (LP: #1645421)
- x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems
- KVM: x86: fix missed SRCU usage in kvm_lapic_set_vapic_addr
- KVM: Disable irq while unregistering user notifier
- arm64: KVM: pmu: Fix AArch32 cycle counter access
- KVM: arm64: Fix the issues when guest PMCCFILTR is configured
- ftrace: Ignore FTRACE_FL_DISABLED while walking dyn_ftrace records
- ftrace: Add more checks for FTRACE_FL_DISABLED in processing ip records
- genirq: Use irq type from irqdata instead of irqdesc
- fuse: fix fuse_write_end() if zero bytes were copied
- IB/rdmavt: rdmavt can handle non aligned page maps
- IB/hfi1: Fix rnr_timer addition
- mfd: intel-lpss: Do not put device in reset state on suspend
- mfd: stmpe: Fix RESET regression on STMPE2401
- can: bcm: fix warning in bcm_connect/proc_register
- gpio: do not double-check direction on sleeping chips
- ALSA: usb-audio: Fix use-after-free of usb_device at disconnect
- ALSA: hda - add a new condition to check if it is thinkpad
- ALSA: hda - Fix mic regression by ASRock mobo fixup
- i2c: mux: fix up dependencies
- i2c: i2c-mux-pca954x: fix deselect enabling for device-tree
- Disable the __builtin_return_address() warning globally after all
- kbuild: add -fno-PIE
- scripts/has-stack-protector: add -fno-PIE
- x86/kexec: add -fno-PIE
- kbuild: Steal gcc's pie from the very beginning
- ext4: sanity check the block and cluster size at mount time
- ARM: dts: imx53-qsb: Fix regulator constraints
- crypto: caam - do not register AES-XTS mode on LP units
- powerpc/64: Fix setting of AIL in hypervisor mode
- drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)
- drm/i915: Refresh that status of MST capable connectors in ->detect()
- drm/i915: Assume non-DP++ port if dvo_port is HDMI and there's no AUX ch
  specified in the VBT
- virtio-net: drop legacy features in virtio 1 mode
- clk: mmp: pxa910: fix return value check in pxa910_clk_init()
- clk: mmp: pxa168: fix return value check in pxa168_clk_init()
- clk: mmp: mmp2: fix return value check in mmp2_clk_init()
- clk: imx: fix integer overflow in AV PLL round rate
- rtc: omap: Fix selecting external osc
- iwlwifi: pcie: fix SPLC structure parsing
- iwlwifi: pcie: mark command queue lock with separate lockdep class
- iwlwifi: mvm: fix netdetect starting/stopping for unified images
- iwlwifi: mvm: fix d3_test with unified D0/D3 images
- iwlwifi: mvm: wake the wait queue when the RX sync counter is zero
- mfd: core: Fix device reference leak in mfd_clone_cell
- sunrpc: svc_age_temp_xprts_now should not call setsockopt non-tcp 
transports
- uwb: fix device reference leaks
- PM / sleep: fix device reference leak in test_suspend
- PM / sleep: don't suspend parent when async child suspend_{noirq, late}
  fails
- perf hists: Fix column length on --hierarchy
- IB/rxe: Update qp state for user query
- IB/rxe: Fix kernel panic in UDP tunnel with GRO and RX checksum
- IB/rxe: Fix handling of erroneous WR
- IB/rxe: Clear queue buffer when modifying QP to reset
- IB/mlx4: Check gid_index return value
- IB/mlx4: Fix create CQ error flow
- IB/mlx5: Validate requested RQT size
- IB/mlx5: Use cache line size to select CQE stride
- IB/mlx5: Fix memory leak in query device
- IB/mlx5: Fix fatal error dispatching
- IB/mlx5: Fix NULL pointer dereference on debug print
- IB/core: Avoid unsigned int overflow in sg_alloc_table
- IB/hfi1: Remove incorrect IS_ERR check
- IB/uverbs: Fix leak of XRC target QPs
- IB/cm: Mark stale CM id's whenever the mad agent was unregistered
- netfilter: nft_dynset: fix element timeout for HZ != 1000
- gpio: pca953x: Move memcpy into mutex lock for set multiple
- gpio: pca953x: Fix corruption of other gpios in set_multiple.
- Linux 4.8.11

  * Upstream stable 4.4.34 and 4.8.10 regression (LP: #1645278)
- flow_dissect: call init_default_flow_dissectors() earlier

  * Fix Kernel Crashing under IBM Virtual Scsi Driver (LP: #1642299)
- SAUCE: ibmvscsis: Rearrange functions for future patches
- SAUCE: ibmvscsis: Synchronize cmds at tpg_enable_store time
- SAUCE: ibmvscsis: Synchronize cmds at remove time
- SAUCE: ibmvscsis: Clean up properly if

[Kernel-packages] [Bug 1640109] Re: hv_set_ifconfig script parsing fails for certain configuration

This bug was fixed in the package linux - 4.4.0-57.78

---
linux (4.4.0-57.78) xenial; urgency=low

  * Release Tracking Bug
- LP: #1648867

  * Miscellaneous Ubuntu changes
- SAUCE: Do not build the xr-usb-serial driver for s390

linux (4.4.0-56.77) xenial; urgency=low

  * Release Tracking Bug
- LP: #1648867

  * Release Tracking Bug
- LP: #1648579

  * CONFIG_NR_CPUS=256 is too low (LP: #1579205)
- [Config] Increase the NR_CPUS to 512 for amd64 to support systems with a
  large number of cores.

  * NVMe drives in Amazon AWS instance fail to initialize (LP: #1648449)
- SAUCE: (no-up) NVMe: only setup MSIX once

linux (4.4.0-55.76) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648503

  * NVMe driver accidentally reverted to use GSI instead of MSIX (LP: #1647887)
- (fix) NVMe: restore code to always use MSI/MSI-x interrupts

linux (4.4.0-54.75) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648017

  * Update hio driver to 2.1.0.28 (LP: #1646643)
- SAUCE: hio: update to Huawei ES3000_V2 (2.1.0.28)

  * linux: Enable live patching for all supported architectures (LP: #1633577)
- [Config] CONFIG_LIVEPATCH=y for s390x

  * Botched backport breaks level triggered EOIs in QEMU guests with --machine
kernel_irqchip=split (LP: #1644394)
- kvm/irqchip: kvm_arch_irq_routing_update renaming split

  * Xenial update to v4.4.35 stable release (LP: #1645453)
- x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems
- KVM: x86: fix missed SRCU usage in kvm_lapic_set_vapic_addr
- KVM: Disable irq while unregistering user notifier
- fuse: fix fuse_write_end() if zero bytes were copied
- mfd: intel-lpss: Do not put device in reset state on suspend
- can: bcm: fix warning in bcm_connect/proc_register
- i2c: mux: fix up dependencies
- kbuild: add -fno-PIE
- scripts/has-stack-protector: add -fno-PIE
- x86/kexec: add -fno-PIE
- kbuild: Steal gcc's pie from the very beginning
- ext4: sanity check the block and cluster size at mount time
- crypto: caam - do not register AES-XTS mode on LP units
- drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)
- clk: mmp: pxa910: fix return value check in pxa910_clk_init()
- clk: mmp: pxa168: fix return value check in pxa168_clk_init()
- clk: mmp: mmp2: fix return value check in mmp2_clk_init()
- rtc: omap: Fix selecting external osc
- iwlwifi: pcie: fix SPLC structure parsing
- mfd: core: Fix device reference leak in mfd_clone_cell
- uwb: fix device reference leaks
- PM / sleep: fix device reference leak in test_suspend
- PM / sleep: don't suspend parent when async child suspend_{noirq, late}
  fails
- IB/mlx4: Check gid_index return value
- IB/mlx4: Fix create CQ error flow
- IB/mlx5: Use cache line size to select CQE stride
- IB/mlx5: Fix fatal error dispatching
- IB/core: Avoid unsigned int overflow in sg_alloc_table
- IB/uverbs: Fix leak of XRC target QPs
- IB/cm: Mark stale CM id's whenever the mad agent was unregistered
- netfilter: nft_dynset: fix element timeout for HZ != 1000
- Linux 4.4.35

  * Upstream stable 4.4.34 and 4.8.10 regression (LP: #1645278)
- flow_dissect: call init_default_flow_dissectors() earlier

  * AD5593R configurable multi-channel converter support (LP: #1644726)
- iio: dac: Add support for the AD5592R/AD5593R ADCs/DACs
- iio: dac: ad5592r: Off by one bug in ad5592r_alloc_channels()
- [Config] CONFIG_AD5592R/AD5593R=m

  * ST Micro lps22hb pressure sensor support (LP: #1642258)
- iio:st_pressure:initial lps22hb sensor support
- iio:st_pressure: align storagebits on power of 2
- iio:st_pressure: document sampling gains
- iio:st_pressure:lps22hb: temperature support

  * Fix Kernel Crashing under IBM Virtual Scsi Driver (LP: #1642299)
- SAUCE: ibmvscsis: Rearrange functions for future patches
- SAUCE: ibmvscsis: Synchronize cmds at tpg_enable_store time
- SAUCE: ibmvscsis: Synchronize cmds at remove time
- SAUCE: ibmvscsis: Clean up properly if target_submit_cmd/tmr fails
- SAUCE: ibmvscsis: Return correct partition name/# to client
- SAUCE: ibmvscsis: Issues from Dan Carpenter/Smatch

  * System stalls when creating device node on booting (LP: #1643797)
- sched/fair: Fix new task's load avg removed from source CPU in
  wake_up_new_task()

  * nvme: improve performance for virtual Google NVMe devices (LP: #1637565)
- blk-mq: add blk_mq_alloc_request_hctx
- nvme.h: add NVMe over Fabrics definitions
- [Config] CONFIG_NVME_VENDOR_EXT_GOOGLE=y
- SAUCE: nvme: improve performance for virtual NVMe devices

  * Move some kernel modules to the main kernel package (LP: #1642228)
- [Config] Move some powerpc kernel modules to the main kernel package

  * sched: Match-all classifier is missing in xenial (LP: #1642514)
-

[Kernel-packages] [Bug 1651402] Re: linux: 4.4.0-58.79 -proposed tracker

** 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) => Luis Henriques 
(henrix)

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

Title:
  linux: 4.4.0-58.79 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-58.79 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/1651402/+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 1650750] Re: bluetooth connection keeps getting turned off after update

2016-12-20 Thread jerrylamos

This bug goes away with Zesty Zappos kernel.  
Zesty fixed Xenial's bios problem.
Problem solved I'll use Zesty waiting to see if an update to Zesty brings the 
problem 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/1650750

Title:
  bluetooth connection keeps getting turned off after update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Turn bluetooth connection on with mouse selection and linux keeps turning it 
off.
  Anker A7721 keyboard running fine before update today and fine on other 
ubuntu partitions.
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
  Linux Lenovo2 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  model name: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
  model name: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Dec 17 07:54:58 2016
  InstallationDate: Installed on 2016-11-23 (23 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161123)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=0047f86e-07a4-4c9d-bed1-2fb8d196b8b3 ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650750/+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 1579205] Re: CONFIG_NR_CPUS=256 is too low

This bug was fixed in the package linux - 4.4.0-57.78

---
linux (4.4.0-57.78) xenial; urgency=low

  * Release Tracking Bug
- LP: #1648867

  * Miscellaneous Ubuntu changes
- SAUCE: Do not build the xr-usb-serial driver for s390

linux (4.4.0-56.77) xenial; urgency=low

  * Release Tracking Bug
- LP: #1648867

  * Release Tracking Bug
- LP: #1648579

  * CONFIG_NR_CPUS=256 is too low (LP: #1579205)
- [Config] Increase the NR_CPUS to 512 for amd64 to support systems with a
  large number of cores.

  * NVMe drives in Amazon AWS instance fail to initialize (LP: #1648449)
- SAUCE: (no-up) NVMe: only setup MSIX once

linux (4.4.0-55.76) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648503

  * NVMe driver accidentally reverted to use GSI instead of MSIX (LP: #1647887)
- (fix) NVMe: restore code to always use MSI/MSI-x interrupts

linux (4.4.0-54.75) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1648017

  * Update hio driver to 2.1.0.28 (LP: #1646643)
- SAUCE: hio: update to Huawei ES3000_V2 (2.1.0.28)

  * linux: Enable live patching for all supported architectures (LP: #1633577)
- [Config] CONFIG_LIVEPATCH=y for s390x

  * Botched backport breaks level triggered EOIs in QEMU guests with --machine
kernel_irqchip=split (LP: #1644394)
- kvm/irqchip: kvm_arch_irq_routing_update renaming split

  * Xenial update to v4.4.35 stable release (LP: #1645453)
- x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems
- KVM: x86: fix missed SRCU usage in kvm_lapic_set_vapic_addr
- KVM: Disable irq while unregistering user notifier
- fuse: fix fuse_write_end() if zero bytes were copied
- mfd: intel-lpss: Do not put device in reset state on suspend
- can: bcm: fix warning in bcm_connect/proc_register
- i2c: mux: fix up dependencies
- kbuild: add -fno-PIE
- scripts/has-stack-protector: add -fno-PIE
- x86/kexec: add -fno-PIE
- kbuild: Steal gcc's pie from the very beginning
- ext4: sanity check the block and cluster size at mount time
- crypto: caam - do not register AES-XTS mode on LP units
- drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)
- clk: mmp: pxa910: fix return value check in pxa910_clk_init()
- clk: mmp: pxa168: fix return value check in pxa168_clk_init()
- clk: mmp: mmp2: fix return value check in mmp2_clk_init()
- rtc: omap: Fix selecting external osc
- iwlwifi: pcie: fix SPLC structure parsing
- mfd: core: Fix device reference leak in mfd_clone_cell
- uwb: fix device reference leaks
- PM / sleep: fix device reference leak in test_suspend
- PM / sleep: don't suspend parent when async child suspend_{noirq, late}
  fails
- IB/mlx4: Check gid_index return value
- IB/mlx4: Fix create CQ error flow
- IB/mlx5: Use cache line size to select CQE stride
- IB/mlx5: Fix fatal error dispatching
- IB/core: Avoid unsigned int overflow in sg_alloc_table
- IB/uverbs: Fix leak of XRC target QPs
- IB/cm: Mark stale CM id's whenever the mad agent was unregistered
- netfilter: nft_dynset: fix element timeout for HZ != 1000
- Linux 4.4.35

  * Upstream stable 4.4.34 and 4.8.10 regression (LP: #1645278)
- flow_dissect: call init_default_flow_dissectors() earlier

  * AD5593R configurable multi-channel converter support (LP: #1644726)
- iio: dac: Add support for the AD5592R/AD5593R ADCs/DACs
- iio: dac: ad5592r: Off by one bug in ad5592r_alloc_channels()
- [Config] CONFIG_AD5592R/AD5593R=m

  * ST Micro lps22hb pressure sensor support (LP: #1642258)
- iio:st_pressure:initial lps22hb sensor support
- iio:st_pressure: align storagebits on power of 2
- iio:st_pressure: document sampling gains
- iio:st_pressure:lps22hb: temperature support

  * Fix Kernel Crashing under IBM Virtual Scsi Driver (LP: #1642299)
- SAUCE: ibmvscsis: Rearrange functions for future patches
- SAUCE: ibmvscsis: Synchronize cmds at tpg_enable_store time
- SAUCE: ibmvscsis: Synchronize cmds at remove time
- SAUCE: ibmvscsis: Clean up properly if target_submit_cmd/tmr fails
- SAUCE: ibmvscsis: Return correct partition name/# to client
- SAUCE: ibmvscsis: Issues from Dan Carpenter/Smatch

  * System stalls when creating device node on booting (LP: #1643797)
- sched/fair: Fix new task's load avg removed from source CPU in
  wake_up_new_task()

  * nvme: improve performance for virtual Google NVMe devices (LP: #1637565)
- blk-mq: add blk_mq_alloc_request_hctx
- nvme.h: add NVMe over Fabrics definitions
- [Config] CONFIG_NVME_VENDOR_EXT_GOOGLE=y
- SAUCE: nvme: improve performance for virtual NVMe devices

  * Move some kernel modules to the main kernel package (LP: #1642228)
- [Config] Move some powerpc kernel modules to the main kernel package

  * sched: Match-all classifier is missing in xenial (LP: #1642514)
-

[Kernel-packages] [Bug 1579205] Re: CONFIG_NR_CPUS=256 is too low