[Kernel-packages] [Bug 1555919] Re: linux-armadaxp: 3.2.0-1664.88 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1664.88 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-Prepare-package-start:Friday, 11. March 2016 04:04 UTC
  kernel-stable-master-bug:1555809
  kernel-stable-Promote-to-proposed-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Certification-testing-end:Saturday, 12. March 2016 03:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Prepare-package-end:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 12. March 2016 05:01 UTC
- kernel-stable-phase:Verification & Testing
- kernel-stable-phase-changed:Saturday, 12. March 2016 15:30 UTC
  kernel-stable-Verification-testing-start:Saturday, 12. March 2016 15:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Saturday, 12. March 2016 15:31 UTC
+ kernel-stable-phase:CopyToUpdates
+ kernel-stable-phase-changed:Tuesday, 15. March 2016 05:00 UTC
+ kernel-stable-Promote-to-updates-start:Tuesday, 15. March 2016 05:00 UTC
+ kernel-stable-Regression-testing-end:Tuesday, 15. March 2016 05:00 UTC

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

Title:
  linux-armadaxp: 3.2.0-1664.88 -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:
  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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

Bug description:
  This bug is for tracking the 3.2.0-1664.88 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-Prepare-package-start:Friday, 11. March 2016 04:04 UTC
  kernel-stable-master-bug:1555809
  kernel-stable-Promote-to-proposed-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Certification-testing-end:Saturday, 12. March 2016 03:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Prepare-package-end:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-Verification-testing-start:Saturday, 12. March 2016 15:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Saturday, 12. March 2016 15:31 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Tuesday, 15. March 2016 05:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 15. March 2016 05:00 UTC
  kernel-stable-Regression-testing-end:Tuesday, 15. March 2016 05:00 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1555919/+subscriptions

-- 
Mailing list: https://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 1555919] Re: linux-armadaxp: 3.2.0-1664.88 -proposed tracker

[Ike Panhc]

** Tags added: qa-testing-passed

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

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

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

Title:
  linux-armadaxp: 3.2.0-1664.88 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

Bug description:
  This bug is for tracking the 3.2.0-1664.88 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-Prepare-package-start:Friday, 11. March 2016 04:04 UTC
  kernel-stable-master-bug:1555809
  kernel-stable-Promote-to-proposed-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Certification-testing-end:Saturday, 12. March 2016 03:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Prepare-package-end:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Saturday, 12. March 2016 15:30 UTC
  kernel-stable-Verification-testing-start:Saturday, 12. March 2016 15:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Saturday, 12. March 2016 15:31 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1555919/+subscriptions

-- 
Mailing list: https://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 1557298] [NEW] [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

[Yung Shen]

Public bug reported:

Failed to pair low energy(bluetooth smart, 4.0 or 4.1) devices
correctly.

1. bluetooth smart mouse is being listed as "all type" in bluetooth-
wizard, however it is able to be paired and use, even repair(i'm
mentioning this because in some circumstance low energy device can be
only paired once, bug #1515179)

2. bluetooth smart keyboard is unable to use after bluetooth-wizard says
"OK". Also the passcode input is also not acting interactively like when
pairing with bluetooth 3.0 keyboard.

Above scenario also being verified with bluetoothctl and blueman.

-
More details about versions:

Environment:
xenial daily (20160307)
bluez 5.37-0ubuntu5
gnome-bluetooth 3.18.2-1ubuntu2
blueman  2.0.3-1ubuntu1
bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)

Tested devices:
Designer Mouse, bluetooth smart (pairable, work, re-pair work)
Designer Keyboard, bluetooth smart (paired, not working)
BT3.0 keyboard, bluetooth classic (pair and work)
BT3.0 mouse, bluetooth classic (pair and work)

-
In control environment with the same hardware system and devices:
trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel)
bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5)

It works with all above devices but can only be pairing through
bluetoothctl, since the older bluetooth-wizard does not understand bluez
5.x. Everything seems works fine, although there are a lot more error
messages, but since this bug is more about xenial, please let me know if
we need more information about this, I'm able to reproduce this trusty
scenario in anytime.

-
Additional note:
A little clarification, since I'm not sure how far the Bluetooth SIG is going 
to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the 
versioning, I decided to just use what ever I saw on the product box.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 15 11:40:12 2016
InstallationDate: Installed on 2016-03-14 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E5550
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0141B2
dmi.board.vendor: Dell Inc.
dmi.board.version: X02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5550
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 00:71:CC:39:BD:22  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:862538 acl:39687 sco:0 events:2668 errors:0
TX bytes:26235 acl:904 sco:0 commands:1021 errors:0

** Affects: unity-control-center
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug xenial

** Attachment added: "bluetooth.service-pairing-with-le-keyboard.log"
   
https://bugs.launchpad.net/bugs/1557298/+attachment/4599510/+files/bluetooth.service-pairing-with-le-keyboard.log

** Also affects: unity-control-center
   Importance: Undecided
   Status: New

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

Title:
  [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

Status in Unity Control Center:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Failed to pair low energy(bluetooth smart, 4.0 or 4.1) devices
  correctly.

  1. bluetooth smart mouse is being listed as "all type" in bluetooth-
  wizard, however it is able to be paired and use, even repair(i'm
  mentioning this because in some circumstance low energy device can be
  only paired once, bug #1515179)

  2. bluetooth smart keyboard is unable to use after bluetooth-wizard
  says "OK". Also the passcode input is also not acting interactively
  like when pairing with bluetooth 3.0 keyboard.

  Above scenario also being verified with bluetoothctl and blueman.

  -
  More details about versions:

  Environment:
  xenial daily (20160307)
  bluez 5.37-0ubuntu5
  gnome-bluetooth 3.18.2-1ubuntu2
  blueman  2.0.3-1ubuntu1
  bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)

  Tested devices:
  Designer Mouse, bluetooth smart (pairable, work, re-pair work)
  Designer Keyboard, bluetooth smart (paired, not working)
  BT3.0 

[Kernel-packages] [Bug 1532466] Re: package linux-firmware 1.149 failed to install/upgrade: package linux-firmware is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-firmware 1.149 failed to install/upgrade: package linux-
  firmware is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  Everytime I log in, I receive a crash message. Unity appears to
  continue to work normally.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-firmware 1.149
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   unity-tweak-tool: Install
   linux-firmware: Configure
   unity-tweak-tool: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jan  9 11:09:50 2016
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.149:package linux-firmware is 
not ready for configuration  cannot configure (current status 'half-installed')
  ErrorMessage: package linux-firmware is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-01-09 (0 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.149 failed to install/upgrade: package 
linux-firmware is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1530346] Re: freeze after Kernel upgraded to 4.2.0-22

[Launchpad Bug Tracker]

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

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

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

Title:
  freeze after Kernel upgraded to 4.2.0-22

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu installed Kernel 4.2.0-22 via auto update.
  After reboot the login screen came and the display resolution was set to 
maybe 800x600, no mouse or keyboard input was possible and after a few seconds 
the password input stopped blinking and it seems that everything was frozen.
  Booting up via selecting old Kernel in Grub is still possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 31 14:34:26 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-352, 352.63, 4.2.0-16-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:3669]
  InstallationDate: Installed on 2015-12-30 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Dec 31 14:28:40 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://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 1532366] Re: package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to install/upgrade: dependency problems - leaving unconfigured

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to
  install/upgrade: dependency problems - leaving unconfigured

Status in linux package in Ubuntu:
  Expired

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  anders 2107 F pulseaudio
   /dev/snd/controlC2:  anders 2107 F pulseaudio
   /dev/snd/controlC1:  anders 2107 F pulseaudio
   /dev/snd/controlC0:  anders 2107 F pulseaudio
  Date: Fri Jan  8 19:36:00 2016
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=8cf14256-7dbc-43db-9f4d-01337418b251
  InstallationDate: Installed on 2015-07-25 (167 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150725)
  MachineType: ASUS All Series
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=5787a1ee-c5ca-47d7-875c-54b7d62ccd6e ro noprompt quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  SourcePackage: linux
  Title: package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to 
install/upgrade: dependency problems - leaving unconfigured
  UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2016-01-09 (0 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd05/15/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
Mailing list: https://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 1533048] Re: [Dell Inc. Inspiron 5537] suspend/resume failure

[Launchpad Bug Tracker]

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

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

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

Title:
  [Dell Inc. Inspiron 5537] suspend/resume failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  Whenever the user logs in, there is a notification about the error.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-12-generic 3.18.0-12.13
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chandransh   1950 F pulseaudio
   /dev/snd/controlC0:  chandransh   1950 F pulseaudio
  Date: Thu Jan  7 11:30:57 2016
  DuplicateSignature: suspend/resume:Dell Inc. Inspiron 5537:A04
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2015-12-01 (41 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Inspiron 5537
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic.efi.signed 
root=UUID=bcd2a969-618f-4a0c-b887-9babfa35e469 ro noprompt quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-12-generic N/A
   linux-backports-modules-3.18.0-12-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 5537] suspend/resume failure
  UpgradeStatus: Upgraded to vivid on 2015-12-01 (41 days ago)
  UserGroups:
   
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 04NGGW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Inspiron 5537
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1534049] Re: Ubuntu 12.04 + QEmu 2.0 + KSM = 1 + OVS, makes Windows 2008 R2 guests to crash

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu 12.04 + QEmu 2.0 + KSM = 1 + OVS, makes Windows 2008 R2 guests
  to crash

Status in linux package in Ubuntu:
  Expired

Bug description:
  hi,

  Recently I met a platform case, troubled me for a long time, is there
  anyone encountered this problem?

  Environment are as follows:

  Openstack environment build with fuel. 
  Controller node: 3
  Compute node: 30
  Ceph node:9
  windows virtio driver version : 61.71.104.1
  Ubuntu 12.04.4 LTS
  QEMU emulator version 2.0.0 (Debian 2.0.0 + dfsg-2ubuntu1.9), Copyright (c) 
2003-2008 Fabrice Bellard

  root@node-96:~# ovs-vsctl --version
  ovs-vsctl (Open vSwitch) 2.0.2
  Compiled Nov 28 2014 21:37:07

  
  Symptoms:
  The guest of Windows virtual machines on one host occasional crash off and 
automatically restart. After the restart the network NIC is automatically 
disabled. Can't allocate ip address with dhcp. Soft reboot is not taking 
effect, only through hard reboot to restore the card back. 

  Note:
  1. The crashed Windows host focused on  a single physical node(HW RH2285), 
although  there are nodes with the same type of machines, but no similar 
problems to happened.
  Maybe it is ovs's bug, cause windows vm received  irregularly packets, then 
resulting in windows nic crash out, later Windows system crash.
  2. when windows vm crashed, there are several windows vm crash 
simultaneously. (about 3 or 4 not all of them)

  At first i thought it was the problem of  Windows virtio drivers , but
  the upgrade windows virtio driver is useless. It feels like qemu
  driver problem. i am not sure about that.

  
  Also, I'm not sure whether this bug and the following related. I have to 
follow the bellow case  turn off  the KSM parameters on HOST, currently in 
testing. If someone run into the same case, please reply.  Thanks.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277


  dmesg log:
  [13766077.712750] init: libvirt-bin main process (35678) killed by KILL signal
  [13766077.712822] init: libvirt-bin main process ended, respawning
  [13766081.675377] ip_set: protocol 6
  [13770171.259174] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13770171.266161] device tape991247b-d0 left promiscuous mode
  [13770171.266200] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13770203.296136] device tape991247b-d0 entered promiscuous mode
  [13770203.329022] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13770203.329040] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13770204.527595] kvm: zapping shadow pages for mmio generation wraparound
  [13771734.263654] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13771734.263704] qbre991247b-d0: port 1(qvbe991247b-d0) entered disabled 
state
  [13771847.638690] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13771847.638742] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13771847.638758] qbre991247b-d0: port 1(qvbe991247b-d0) entered forwarding 
state
  [13771847.638770] qbre991247b-d0: port 1(qvbe991247b-d0) entered forwarding 
state
  [13784647.176340] qbr03992610-e3: port 1(qvb03992610-e3) entered disabled 
state
  [13784668.538526] qbrc9002954-09: port 1(qvbc9002954-09) entered disabled 
state
  [13792069.237135] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13792069.246187] device tape991247b-d0 left promiscuous mode
  [13792069.246215] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13792070.174570] device tape991247b-d0 entered promiscuous mode
  [13792070.207159] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13792070.207181] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13792071.041157] kvm: zapping shadow pages for mmio generation wraparound
  [13794383.653582] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13794383.666387] device tape991247b-d0 left promiscuous mode
  [13794383.666413] qbre991247b-d0: port 2(tape991247b-d0) entered disabled 
state
  [13794384.468924] device tape991247b-d0 entered promiscuous mode
  [13794384.501689] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state
  [13794384.501710] qbre991247b-d0: port 2(tape991247b-d0) entered forwarding 
state

  
  /var/log/libvirt/qemu/instance-304b.log
  qemu: terminating on signal 15 from pid 138887
  2016-01-11 05:16:04.937+: shutting down
  2016-01-11 05:16:05.709+: starting up
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin 
QEMU_AUDIO_DRV=none 

[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

[Selene Scriven]

Yes, this still happens with today's phone image.  It took about a dozen
power cycles to trigger.

** Changed in: canonical-devices-system-image
   Status: Incomplete => Confirmed

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions

-- 
Mailing list: https://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 1557278] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  dm-crypt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  aes-xts-128 mode bit not supported in this kernel
  so existing encrypted drive (/) could not be mounted

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-83-generic 3.13.0-83.127
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pavel  2048 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 15 05:21:57 2016
  MachineType: LENOVO 20206
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=UUID=0d637c5b-aeab-4085-80af-e1988b0c8eb7 ro splash quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  StagingDrivers: keucr
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET74WW(1.11)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20206
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn20206:pvrLenovoB590:rvnLENOVO:rn20206:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20206
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1557278] [NEW] dm-crypt

[Puher]

Public bug reported:

aes-xts-128 mode bit not supported in this kernel
so existing encrypted drive (/) could not be mounted

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-83-generic 3.13.0-83.127
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pavel  2048 F pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 15 05:21:57 2016
MachineType: LENOVO 20206
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=UUID=0d637c5b-aeab-4085-80af-e1988b0c8eb7 ro splash quiet
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-79-generic N/A
 linux-backports-modules-3.13.0-79-generic  N/A
 linux-firmware 1.127.20
SourcePackage: linux
StagingDrivers: keucr
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: H9ET74WW(1.11)
dmi.board.asset.tag: Not Available
dmi.board.name: 20206
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn20206:pvrLenovoB590:rvnLENOVO:rn20206:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20206
dmi.product.version: Lenovo B590
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug staging 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/1557278

Title:
  dm-crypt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  aes-xts-128 mode bit not supported in this kernel
  so existing encrypted drive (/) could not be mounted

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-83-generic 3.13.0-83.127
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pavel  2048 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 15 05:21:57 2016
  MachineType: LENOVO 20206
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=UUID=0d637c5b-aeab-4085-80af-e1988b0c8eb7 ro splash quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  StagingDrivers: keucr
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET74WW(1.11)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20206
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn20206:pvrLenovoB590:rvnLENOVO:rn20206:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20206
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1557258] [NEW] random wifi hangs when transferring large files at high speeds using BCM4331 wifi

[shurikx]

Public bug reported:

My system is: macbook pro retina late 2012 with BCM4331 wifi card
OS: ubuntu 15.10
driver version:  6.30.223.248+bdcom-0ubuntu7

When transferring large files over wifi using the BCM4331 the wifi hangs
randomly. echo 1 > reset in /sys... hangs the system. I tried using the
hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz from the Broadcom site,
but the result is the same. This does not seem to be a hardware bug, as
in MacOS I cannot replicate the problem. When this happens, the system
is operational. No kernel panics or other information in logs. iwlist
wlan0 scan reports device busy. rmmod wl hangs the system.  When
transfering over smb on low speed (about 10MB/s) the hangs are appearing
less often. However, over NFS (reading) with 30-40 MB/s this happens
after less than 1 minute of the transfer.

>From time to time I get in the logs:

[  655.114258]   d4b65ff9 880457443da8 
817ebf13
[  655.114263]    880457443de8 
8107b9d6
[  655.114267]  88045696e078 88044fcc8000 8803dd725900 
009b
[  655.114271] Call Trace:
[  655.114281]  [] dump_stack+0x45/0x57
[  655.114289]  [] warn_slowpath_common+0x86/0xc0
[  655.114293]  [] warn_slowpath_null+0x1a/0x20
[  655.114313]  [] cfg80211_roamed+0x86/0xa0 [cfg80211]
[  655.114368]  [] wl_notify_roaming_status+0xc5/0x140 [wl]
[  655.114415]  [] wl_event_handler+0x64/0x1f0 [wl]
[  655.114459]  [] ? wl_free_wdev.isra.23+0x80/0x80 [wl]
[  655.114464]  [] kthread+0xd8/0xf0
[  655.114468]  [] ? kthread_create_on_node+0x1f0/0x1f0
[  655.114473]  [] ret_from_fork+0x3f/0x70
[  655.114477]  [] ? kthread_create_on_node+0x1f0/0x1f0
[  655.114480] ---[ end trace 673f2b48cc352431 ]---

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Mar 15 03:04:54 2016
InstallationDate: Installed on 2015-05-16 (303 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: bcmwl
UpgradeStatus: Upgraded to wily on 2015-12-11 (94 days ago)

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


** Tags: amd64 apport-bug wily

** Description changed:

  My system is: macbook pro retina late 2012 with BCM4331 wifi card
  OS: ubuntu 15.10
  driver version:  6.30.223.248+bdcom-0ubuntu7
  
  When transferring large files over wifi using the BCM4331 the wifi hangs
  randomly. echo 1 > reset in /sys... hangs the system. I tried using the
  hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz from the Broadcom site,
  but the result is the same. This does not seem to be a hardware bug, as
  in MacOS I cannot replicate the problem. When this happens, the system
  is operational. No kernel panics or other information in logs. iwlist
  wlan0 scan reports device busy. rmmod wl hangs the system.  When
  transfering over smb on low speed (about 10MB/s) the hangs are appearing
  less often. However, over NFS (reading) with 30-40 MB/s this happens
  after less than 1 minute of the transfer.
  
- From time to time I get in the logs: 
- Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS 
MBP101.88Z.00EE.B0A.1509111559 09/11/2015
+ From time to time I get in the logs:
+ 
  [  655.114258]   d4b65ff9 880457443da8 
817ebf13
  [  655.114263]    880457443de8 
8107b9d6
  [  655.114267]  88045696e078 88044fcc8000 8803dd725900 
009b
  [  655.114271] Call Trace:
  [  655.114281]  [] dump_stack+0x45/0x57
  [  655.114289]  [] warn_slowpath_common+0x86/0xc0
  [  655.114293]  [] warn_slowpath_null+0x1a/0x20
  [  655.114313]  [] cfg80211_roamed+0x86/0xa0 [cfg80211]
  [  655.114368]  [] wl_notify_roaming_status+0xc5/0x140 [wl]
  [  655.114415]  [] wl_event_handler+0x64/0x1f0 [wl]
  [  655.114459]  [] ? wl_free_wdev.isra.23+0x80/0x80 [wl]
  [  655.114464]  [] kthread+0xd8/0xf0
  [  655.114468]  [] ? kthread_create_on_node+0x1f0/0x1f0
  [  655.114473]  [] ret_from_fork+0x3f/0x70
  [  655.114477]  [] ? kthread_create_on_node+0x1f0/0x1f0
  [  655.114480] ---[ end trace 673f2b48cc352431 ]---
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Mar 15 03:04:54 2016
  InstallationDate: Installed on 2015-05-16 (303 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: bcmwl
  UpgradeStatus: Upgraded to wily on 2015-12-11 (94 days ago)

-- 

[Kernel-packages] [Bug 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported

[Miles Krell]

dagny, could you elaborate?  I find it highly unlikely that adding
firmware files for this card could have deleted a partition from a drive
on your computer.  Could your problem have something to do with the
kernel you're using?

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

Title:
  Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041]
  is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed

Bug description:
  This card remains unsupported out-of-the-box by the ath10k_pci kernel
  module.  At this point, it looks like kvalo's ath10k-firmware repo
  just needs to be pulled in.

  Speaking of which, that repo contains a folder for the QCA6174, but
  not for the QCA6164.  The firmware in the QCA6174 folder works for the
  QCA6164; I still find it strange.  I'm not sure how well the actual
  QCA6174 [168c:003e] firmware works.

  ---

  HOW TO GET THIS CARD TO WORK:

  As of February 26, 2016, this has become very simple.

  I'm unsure of what version kernel you need to be using - it's either
  at least 4.0 or at least 4.2.  I'm currently using 4.4.3.  If the
  kernel you have isn't working, try that one.

  1) Get the latest firmware from https://github.com/kvalo/ath10k-
  firmware/archive/master.zip

  2) Unzip this file, and copy the ath10k folder's contents to
  /lib/firmware/ath10k.

  3) Reboot your computer.  Run "lshw -C network" to see if your card is
  recognized.

  If you created a "/lib/modprobe.d/ath10k.conf" file earlier to disable
  otp, you can remove it.  I did, and the card still works fine.

  Last updated February 28, 2016

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

-- 
Mailing list: https://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 1557250] Missing required logs.

[Brad Figg]

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

apport-collect 1557250

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

Title:
  linux fails to load x.509 built-in certificate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ dmesg | grep '\.509'
  [   11.950518] Loading compiled-in X.509 certificates
  [   11.951343] Problem loading in-kernel X.509 certificate (-74)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Mar 14 21:39:09 2016
  HibernationDevice: RESUME=/dev/mapper/vg0-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/vg0-rootfs BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-12-generic N/A
   linux-backports-modules-4.4.0-12-generic  N/A
   linux-firmware1.156
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1557250] [NEW] linux fails to load x.509 built-in certificate

[Dimitri John Ledkov]

Public bug reported:

$ dmesg | grep '\.509'
[   11.950518] Loading compiled-in X.509 certificates
[   11.951343] Problem loading in-kernel X.509 certificate (-74)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-12-generic 4.4.0-12.28
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic s390x
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20-0ubuntu3
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Mon Mar 14 21:39:09 2016
HibernationDevice: RESUME=/dev/mapper/vg0-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/mapper/vg0-rootfs BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-12-generic N/A
 linux-backports-modules-4.4.0-12-generic  N/A
 linux-firmware1.156
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug s390x xenial

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

Title:
  linux fails to load x.509 built-in certificate

Status in linux package in Ubuntu:
  New

Bug description:
  $ dmesg | grep '\.509'
  [   11.950518] Loading compiled-in X.509 certificates
  [   11.951343] Problem loading in-kernel X.509 certificate (-74)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Mar 14 21:39:09 2016
  HibernationDevice: RESUME=/dev/mapper/vg0-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/vg0-rootfs BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-12-generic N/A
   linux-backports-modules-4.4.0-12-generic  N/A
   linux-firmware1.156
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1550050] Re: repeating phantom key when bt disconnects

[Daniel van Vugt]

Is this one critical or just high?

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Mir:
  In Progress
Status in Mir 0.20 series:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions

-- 
Mailing list: https://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 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working

[Robert Ancell]

linux-
image-4.1.0-040100rc1-generic_4.1.0-040100rc1.201603101727_amd64.deb -
fails to boot. Stops at "Loading initial ramdisk"

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

Title:
  [Toshiba P50W-B00F] Touchscreen no longer working

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

Bug description:
  Sometime in the last month or so my touchscreen stopped working on my
  Toshiba P50W. The dmesg log shows it constantly reconnecting to it:

  [  556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd
  [  556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.538349] usb 1-4: Product: Touchscreen
  [  556.538351] usb 1-4: Manufacturer: ELAN
  [  556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  556.547788] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374
  [  556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  556.600584] usb 1-4: USB disconnect, device number 119

  [  556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd
  [  556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.990503] usb 1-4: Product: Touchscreen
  [  556.990506] usb 1-4: Manufacturer: ELAN
  [  556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  557.001248] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376
  [  557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  557.013831] usb 1-4: USB disconnect, device number 120

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bob2041 F pulseaudio
   /dev/snd/controlC0:  bob2041 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 09:46:25 2015
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (635 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago)
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://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 1531362] Re: The micmute hotkey can't work on a Lenovo Thinkcenter AIO

[Hui Wang]

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

** Changed in: hwe-next
   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/1531362

Title:
  The micmute hotkey can't work on a Lenovo Thinkcenter AIO

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

Bug description:
  1. $ arecord aa.wav. During recording, press 'mic-mute' key intermittently.
  2. $ aplay aa.wav.

  Expected result:
  The aa.wav played intermittently.

  Actual result:
  Mic could not be mute, the sound play in whole range; Its LED is off always.

  
  This is bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1531362/+subscriptions

-- 
Mailing list: https://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 1555912] Re: The mic mute key and led can't work on a Lenovo AIO machine

[Hui Wang]

commit 6ef2f68fa38bf415830f67903d87180d933e0f47
Author: Hui Wang 
Date:   Fri Mar 11 12:04:02 2016 +0800

ALSA: hda - fix the mic mute button and led problem for a Lenovo AIO

This Lenovo ThinkCentre AIO also uses Line2 as mic mute button and
uses GPIO2 to control the mic mute led, so applying this quirk can
make both the button and led work.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1555912
Signed-off-by: Hui Wang 
Signed-off-by: Takashi Iwai 


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

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

Title:
  The mic mute key and led can't work on a Lenovo AIO machine

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

Bug description:
  Press the mic mute button on the side of the AIO monitor, Mic could
  not be mute, the  LED is off always.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1555912/+subscriptions

-- 
Mailing list: https://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 806032] Re: Fn + F[89] does not work for controlling brightness on Clevo laptops (B7130, W150HRM)

[Egbert van der Wal]

I'm not sure if this is still / again the same problem, but I have a
very similar issue on a recently bought Clevo P650RA laptop, running
Ubuntu Xenial / 16.04 and the similar bug search when reporting a new
bug led me to this issue.

The brightness keys do not work; setting the brightness manually through
/sys/class/backlight/intel_backlight works fine.

Probably related: in the BIOS I can select either MSHYBRID or DISCRETE
for the GPU, meaning either Optimus-like-technology or DISCRETE only.
When using DISCRETE, the brightness keys do work. However, in that case
I'm forced to use the Nouveau driver since the nvidia driver will not
work anymore. And the nouveau driver makes this laptop crash after a
short while, so it's not really a viable alternative.

When running in MSHYBRID, maybe there are more possible connected
devices making this bug appear?

There's also some ACPI Warnings in DMESG that may be related. I'll
attach the output of dmesg to this message.

Please let me know if I should report a new bug rather than necroposting
in this old bug that appears to be resolved long ago. I'd be happy to
provide more information if you point me in the right direction for
obtaining that information.


** Attachment added: "dmesg.txt showing some ACPI warnings that may be related"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/806032/+attachment/4599404/+files/dmesg.txt

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

Title:
  Fn + F[89] does not work for controlling brightness on Clevo laptops
  (B7130, W150HRM)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I cannot modify the brightness level through Fn + F[89] keys even if I
  can control it through `/sys/class/backlight/acpi_video0` or the Power
  management applet in KDE.

  I followed the instructions on 
https://wiki.ubuntu.com/Hotkeys/Troubleshooting without luck
  I've already tried `xev`, `udevadm monitor`, looking in dmesg and 
/var/log/kern.log, using /lib/udev/keymap for monitoring keyboard input.

  Per suggestion by apw in #ubuntu-kernel, I installed input-utils and
  ran `sudo lsinput` to get a list of devices. On each device, I did
  `sudo input-events -t 10 $number` to watch for events. Each time I
  pressed a regular key ("c"), another Fn key (Fn + F6 / Volume Up) and
  Fn + F[89] (brightness up/down). I didn't get any output for the Fn +
  F[89] events.

  Link to user guides (which includes images):
  http://www.clevo.com.tw/en/e-services/download/USRManualOut.asp?model=B7130

  IRC log:
  http://irclogs.ubuntu.com/2011/07/05/%23ubuntu-kernel.html#t15:02

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: VT1812 Analog [VT1812 Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter 21076 F pulseaudio
   /dev/snd/pcmC0D0p:   peter 21076 F...m pulseaudio
  CRDA: Error: [Errno 2] Bestand of map bestaat niet
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfd80 irq 50'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:11060448,15587130,0010 
HDA:80862804,15587130,0010'
     Controls  : 29
     Simple ctrls  : 14
  Date: Tue Jul  5 17:55:27 2011
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426.3)
  MachineType: CLEVO CO. B7130
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, user)
   LANG=nl_NL.UTF-8
   LC_MESSAGES=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic 
root=/dev/mapper/sda2_crypt ro splash vt.handoff=7 break=modules,premount,mount
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.52
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: B7130
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/27/2010:svnCLEVOCO.:pnB7130:pvrNotApplicable:rvnCLEVOCO.:rnB7130:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A:
  

[Kernel-packages] [Bug 1552985] Re: [Dell Inspiron 14 3000 Series] System hangs on poweroff

[José Jorge Enríquez Rodríguez]

Christopher,

no, I don't need a backport to a release prior to 16.04, so I'm marking
this as Status Invalid.

Thank you so much for your help.

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

Title:
  [Dell Inspiron 14 3000 Series] System hangs on poweroff

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Xubuntu 14.04.4 LTS
  Linux 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  When shutting down the system, it gets stuck on the Xubuntu splash
  screen. I have to press the power button for a while to have it shut
  down.

  This is a dual boot system: Windows 10 and Xubuntu 14.04. I updated BIOS 
version to A10 a couple of days ago. It hanged when trying to shut down from 
both Windows and Xubuntu.
  After installing the firmware update from 
http://www.dell.com/support/article/mx/es/mxbsdt1/SLN300281/EN, the computer 
shuts down correctly from Windows, but still gets stuck when trying to shut 
down from Xubuntu, no matter if using the "Shutdown" button or running 
"shutdown -h now" or "poweroff" from a terminal.

  I found a similar bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341925?comments=all,
  but the solution mentioned there did not work for me, also, I don't
  have any problems when rebooting the computer, just when trying to
  shut down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-79-generic 3.13.0-79.123
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jorge  2347 F pulseaudio
   /dev/snd/controlC1:  jorge  2347 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Mar  3 18:43:20 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-18 (471 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  MachineType: Dell Inc. Inspiron 3442
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed 
root=UUID=bc5b1ae8-a10c-4705-afc7-3cf3c2538883 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0260GN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/03/2015:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0260GN:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1550879] Re: [Dell Inc. Inspiron 7559] suspend/resume failure

[Jimmy Pan]

cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
PEG2  S4*disabled
PEGP  S4*disabled
RP09  S4*disabled
PXSX  S4*disabled
RP10  S4*disabled
PXSX  S4*disabled
RP11  S4*disabled
PXSX  S4*disabled
RP12  S4*disabled
PXSX  S4*disabled
RP13  S4*disabled
PXSX  S4*disabled
RP01  S4*disabled  pci::00:1c.0
PXSX  S4*disabled
RP02  S4*disabled
PXSX  S4*disabled
RP03  S4*disabled
PXSX  S4*disabled
RP04  S4*disabled
PXSX  S4*disabled
RP05  S4*disabled  pci::00:1c.4
PXSX  S4*enabled   pci::04:00.0
RP06  S4*disabled  pci::00:1c.5
PXSX  S4*disabled  pci::05:00.0
RP07  S4*disabled  pci::00:1c.6
PXSX  S4*disabled  pci::06:00.0
*disabled  platform:rtsx_pci_sdmmc.0
*disabled  platform:rtsx_pci_ms.0
RP08  S4*disabled
PXSX  S4*disabled
RP17  S4*disabled
PXSX  S4*disabled
RP18  S4*disabled
PXSX  S4*disabled
RP19  S4*disabled
PXSX  S4*disabled
RP20  S4*disabled
PXSX  S4*disabled
RP14  S4*disabled
PXSX  S4*disabled
RP15  S4*disabled
PXSX  S4*disabled
RP16  S4*disabled
PXSX  S4*disabled
PEG1  S4*disabled  pci::00:01.0
PEGP  S4*disabled
PEG0  S4*disabled  pci::00:01.1
PEGP  S4*disabled  pci::02:00.0
XHC   S3*enabled   pci::00:14.0
XDCI  S4*disabled
HDAS  S4*disabled  pci::00:1f.3
LID0  S3*enabled   platform:PNP0C0D:00

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

Title:
  [Dell Inc. Inspiron 7559] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using command of pm-suspend, the machine might be suspended, but
  cannot be waken either by clicking the keyboard or power button.

  Sometimes the suspension will fail too.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pjm2439 F...m pulseaudio
   /dev/snd/controlC0:  pjm2439 F pulseaudio
  Date: Sun Feb 28 15:30:13 2016
  DuplicateSignature: suspend/resume:Dell Inc. Inspiron 7559:1.1.3
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=447ec3f7-71bc-498d-ba0f-03ed68deccf2
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Inspiron 7559
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed 
root=UUID=d19074ca-3e53-4e29-b6ba-95daa56f7da0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 7559] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H87XC
  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.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1550879] Re: [Dell Inc. Inspiron 7559] suspend/resume failure

[Jimmy Pan]

** Attachment added: "pmtest_output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550879/+attachment/4599397/+files/pmtest_output

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

Title:
  [Dell Inc. Inspiron 7559] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using command of pm-suspend, the machine might be suspended, but
  cannot be waken either by clicking the keyboard or power button.

  Sometimes the suspension will fail too.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pjm2439 F...m pulseaudio
   /dev/snd/controlC0:  pjm2439 F pulseaudio
  Date: Sun Feb 28 15:30:13 2016
  DuplicateSignature: suspend/resume:Dell Inc. Inspiron 7559:1.1.3
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=447ec3f7-71bc-498d-ba0f-03ed68deccf2
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Inspiron 7559
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed 
root=UUID=d19074ca-3e53-4e29-b6ba-95daa56f7da0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 7559] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H87XC
  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.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1550879] Re: [Dell Inc. Inspiron 7559] suspend/resume failure

[Jimmy Pan]

suspension failed in any way, first clipping my laptop screen doesn't
work, executing pm-suspend or clicking the suspend button in gnome don't
work either.

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

Title:
  [Dell Inc. Inspiron 7559] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using command of pm-suspend, the machine might be suspended, but
  cannot be waken either by clicking the keyboard or power button.

  Sometimes the suspension will fail too.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pjm2439 F...m pulseaudio
   /dev/snd/controlC0:  pjm2439 F pulseaudio
  Date: Sun Feb 28 15:30:13 2016
  DuplicateSignature: suspend/resume:Dell Inc. Inspiron 7559:1.1.3
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=447ec3f7-71bc-498d-ba0f-03ed68deccf2
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Inspiron 7559
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed 
root=UUID=d19074ca-3e53-4e29-b6ba-95daa56f7da0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 7559] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H87XC
  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.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1550879] Re: [Dell Inc. Inspiron 7559] suspend/resume failure

[Jimmy Pan]

the output of pm test

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

Title:
  [Dell Inc. Inspiron 7559] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using command of pm-suspend, the machine might be suspended, but
  cannot be waken either by clicking the keyboard or power button.

  Sometimes the suspension will fail too.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pjm2439 F...m pulseaudio
   /dev/snd/controlC0:  pjm2439 F pulseaudio
  Date: Sun Feb 28 15:30:13 2016
  DuplicateSignature: suspend/resume:Dell Inc. Inspiron 7559:1.1.3
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=447ec3f7-71bc-498d-ba0f-03ed68deccf2
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Inspiron 7559
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed 
root=UUID=d19074ca-3e53-4e29-b6ba-95daa56f7da0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 7559] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H87XC
  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.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1555353] Re: integer overflow in xt_alloc_table_info

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

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

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

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

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

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

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

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-quantal (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-raring (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-saucy (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-mako (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-manta (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-goldfish (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-flo (Ubuntu Trusty)
   

[Kernel-packages] [Bug 1555919] Re: linux-armadaxp: 3.2.0-1664.88 -proposed tracker

[Ike Panhc]

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

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

Title:
  linux-armadaxp: 3.2.0-1664.88 -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:
  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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

Bug description:
  This bug is for tracking the 3.2.0-1664.88 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-Prepare-package-start:Friday, 11. March 2016 04:04 UTC
  kernel-stable-master-bug:1555809
  kernel-stable-Promote-to-proposed-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Certification-testing-end:Saturday, 12. March 2016 03:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. March 2016 03:02 UTC
  kernel-stable-Prepare-package-end:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 12. March 2016 05:01 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Saturday, 12. March 2016 15:30 UTC
  kernel-stable-Verification-testing-start:Saturday, 12. March 2016 15:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Saturday, 12. March 2016 15:31 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1555919/+subscriptions

-- 
Mailing list: https://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 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Fix Released

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Importance: Undecided => High

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Fix Released

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: linux-lts-raring (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Importance: Undecided => High

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

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

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

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

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was upgrading with update-manager -d

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bud1924 F pulseaudio
  Date: Tue Mar 15 00:59:01 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=5d922ba3-2d87-4da0-93ca-38fdb08afc9e
  InstallationDate: Installed on 2016-03-11 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: eMachines eM355
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=377221af-6a2f-4d1c-8f99-f0a45836f2c0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: linux
  Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-03-15 (0 days ago)
  dmi.bios.date: 04/22/2011
  dmi.bios.vendor: eMachines
  dmi.bios.version: V3.16(DDR3)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HM02_PT
  dmi.board.vendor: eMachines
  dmi.board.version: V3.16(DDR3)
  dmi.chassis.type: 10
  dmi.chassis.vendor: eMachines
  dmi.chassis.version: V3.16(DDR3)
  dmi.modalias: 
dmi:bvneMachines:bvrV3.16(DDR3):bd04/22/2011:svneMachines:pneM355:pvrV3.16(DDR3):rvneMachines:rnHM02_PT:rvrV3.16(DDR3):cvneMachines:ct10:cvrV3.16(DDR3):
  dmi.product.name: eM355
  dmi.product.version: V3.16(DDR3)
  dmi.sys.vendor: eMachines

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

-- 
Mailing list: https://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 1557231] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-extra-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: dependency problems - leaving unconfigured

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was upgrading with update-manager -d

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bud1924 F pulseaudio
  Date: Tue Mar 15 01:00:35 2016
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=5d922ba3-2d87-4da0-93ca-38fdb08afc9e
  InstallationDate: Installed on 2016-03-11 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: eMachines eM355
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=377221af-6a2f-4d1c-8f99-f0a45836f2c0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: dependency problems - leaving unconfigured
  UpgradeStatus: Upgraded to xenial on 2016-03-15 (0 days ago)
  dmi.bios.date: 04/22/2011
  dmi.bios.vendor: eMachines
  dmi.bios.version: V3.16(DDR3)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HM02_PT
  dmi.board.vendor: eMachines
  dmi.board.version: V3.16(DDR3)
  dmi.chassis.type: 10
  dmi.chassis.vendor: eMachines
  dmi.chassis.version: V3.16(DDR3)
  dmi.modalias: 
dmi:bvneMachines:bvrV3.16(DDR3):bd04/22/2011:svneMachines:pneM355:pvrV3.16(DDR3):rvneMachines:rnHM02_PT:rvrV3.16(DDR3):cvneMachines:ct10:cvrV3.16(DDR3):
  dmi.product.name: eM355
  dmi.product.version: V3.16(DDR3)
  dmi.sys.vendor: eMachines

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

-- 
Mailing list: https://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 1557231] [NEW] package linux-image-extra-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: dependency problems - leaving unconfigured

[Michele Olivo]

Public bug reported:

I was upgrading with update-manager -d

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-12-generic 4.4.0-12.28
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bud1924 F pulseaudio
Date: Tue Mar 15 01:00:35 2016
ErrorMessage: dependency problems - leaving unconfigured
HibernationDevice: RESUME=UUID=5d922ba3-2d87-4da0-93ca-38fdb08afc9e
InstallationDate: Installed on 2016-03-11 (3 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
MachineType: eMachines eM355
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=377221af-6a2f-4d1c-8f99-f0a45836f2c0 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36
SourcePackage: linux
Title: package linux-image-extra-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: dependency problems - leaving unconfigured
UpgradeStatus: Upgraded to xenial on 2016-03-15 (0 days ago)
dmi.bios.date: 04/22/2011
dmi.bios.vendor: eMachines
dmi.bios.version: V3.16(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HM02_PT
dmi.board.vendor: eMachines
dmi.board.version: V3.16(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: V3.16(DDR3)
dmi.modalias: 
dmi:bvneMachines:bvrV3.16(DDR3):bd04/22/2011:svneMachines:pneM355:pvrV3.16(DDR3):rvneMachines:rnHM02_PT:rvrV3.16(DDR3):cvneMachines:ct10:cvrV3.16(DDR3):
dmi.product.name: eM355
dmi.product.version: V3.16(DDR3)
dmi.sys.vendor: eMachines

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-extra-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: dependency problems - leaving unconfigured

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was upgrading with update-manager -d

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bud1924 F pulseaudio
  Date: Tue Mar 15 01:00:35 2016
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=5d922ba3-2d87-4da0-93ca-38fdb08afc9e
  InstallationDate: Installed on 2016-03-11 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: eMachines eM355
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=377221af-6a2f-4d1c-8f99-f0a45836f2c0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: dependency problems - leaving unconfigured
  UpgradeStatus: Upgraded to xenial on 2016-03-15 (0 days ago)
  dmi.bios.date: 04/22/2011
  dmi.bios.vendor: eMachines
  dmi.bios.version: V3.16(DDR3)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HM02_PT
  dmi.board.vendor: eMachines
  dmi.board.version: V3.16(DDR3)
  dmi.chassis.type: 10
  dmi.chassis.vendor: eMachines
  dmi.chassis.version: V3.16(DDR3)
  dmi.modalias: 
dmi:bvneMachines:bvrV3.16(DDR3):bd04/22/2011:svneMachines:pneM355:pvrV3.16(DDR3):rvneMachines:rnHM02_PT:rvrV3.16(DDR3):cvneMachines:ct10:cvrV3.16(DDR3):
  dmi.product.name: eM355
  dmi.product.version: V3.16(DDR3)
  dmi.sys.vendor: eMachines

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

-- 
Mailing list: https://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 1557230] [NEW] package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Michele Olivo]

Public bug reported:

I was upgrading with update-manager -d

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-12-generic 4.4.0-12.28
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bud1924 F pulseaudio
Date: Tue Mar 15 00:59:01 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=5d922ba3-2d87-4da0-93ca-38fdb08afc9e
InstallationDate: Installed on 2016-03-11 (3 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
MachineType: eMachines eM355
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=377221af-6a2f-4d1c-8f99-f0a45836f2c0 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36
SourcePackage: linux
Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: Upgraded to xenial on 2016-03-15 (0 days ago)
dmi.bios.date: 04/22/2011
dmi.bios.vendor: eMachines
dmi.bios.version: V3.16(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HM02_PT
dmi.board.vendor: eMachines
dmi.board.version: V3.16(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: V3.16(DDR3)
dmi.modalias: 
dmi:bvneMachines:bvrV3.16(DDR3):bd04/22/2011:svneMachines:pneM355:pvrV3.16(DDR3):rvneMachines:rnHM02_PT:rvrV3.16(DDR3):cvneMachines:ct10:cvrV3.16(DDR3):
dmi.product.name: eM355
dmi.product.version: V3.16(DDR3)
dmi.sys.vendor: eMachines

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  I was upgrading with update-manager -d

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bud1924 F pulseaudio
  Date: Tue Mar 15 00:59:01 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=5d922ba3-2d87-4da0-93ca-38fdb08afc9e
  InstallationDate: Installed on 2016-03-11 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: eMachines eM355
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=377221af-6a2f-4d1c-8f99-f0a45836f2c0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: linux
  Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-03-15 (0 days ago)
  dmi.bios.date: 04/22/2011
  dmi.bios.vendor: eMachines
  dmi.bios.version: V3.16(DDR3)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HM02_PT
  dmi.board.vendor: eMachines
  dmi.board.version: V3.16(DDR3)
  dmi.chassis.type: 10
  dmi.chassis.vendor: eMachines
  dmi.chassis.version: V3.16(DDR3)
  dmi.modalias: 
dmi:bvneMachines:bvrV3.16(DDR3):bd04/22/2011:svneMachines:pneM355:pvrV3.16(DDR3):rvneMachines:rnHM02_PT:rvrV3.16(DDR3):cvneMachines:ct10:cvrV3.16(DDR3):
  dmi.product.name: eM355
  dmi.product.version: V3.16(DDR3)
  dmi.sys.vendor: eMachines

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

-- 
Mailing list: https://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 1549200] Re: CVE-2016-2549

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549200

Title:
  CVE-2016-2549

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1549189] Re: CVE-2016-2546

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549189

Title:
  CVE-2016-2546

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1549195] Re: CVE-2016-2548

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549195

Title:
  CVE-2016-2548

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1549190] Re: CVE-2016-2547

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549190

Title:
  CVE-2016-2547

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1551395] Re: CVE-2016-2782

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

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

** Changed in: linux-lts-vivid (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1551395

Title:
  CVE-2016-2782

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Released
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in 

[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic

[ais523]

Thanks for your advice. I will test the recent mainstream kernels in a
few days, but I am not able to do so immediately. I will leave the bug
as incomplete until then.

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

Title:
  Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
  causes an endless reset loop or a kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce (happens > 50% of the time, but not every time):

  Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable
  while both the device and computer are on (i.e. hotplug).

  Observed symptoms:
  - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the 
LEDs on the front of the device flashing rapidly), being reset approximately 
every 200ms; on such occasions, the Ubuntu user interface often reacts as 
though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly 
adding an "Audio CD" icon to the launcher and then removing it, and putting up 
dialog boxes complaining about failure to read the data).
  - sometimes the kernel panics (often some time after the reset loop starts, 
perhaps up to 10 seconds); when this happens there was always or nearly always 
a reset loop occurring beforehand.
  - sometimes the device resets once or not at all, then works as expected 
(showing up as a network interface, and allowing me to communicate to the 
Internet with a wired connection); I'm currently using an Osprey 2 Mini for 
this purpose right now.

  The kernel panics lock up the entire system (forcing a hard power
  off). lt-Sysrq commands don't work in this state (even though I have
  them enabled), and sometimes the Caps Lock light flashes repeatedly.
  The logs end some time before the panic occurs.

  /var/log/syslog:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog

  The reset loops also occurred when I was using Ubuntu vivid. The
  kernel panics only happened after an upgrade to wily. Output of lsusb
  -v is attached.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 6233 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007
  InstallationDate: Installed on 2014-06-03 (648 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-32-generic x86_64
  UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2186
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1549184] Re: CVE-2016-2545

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549184

Title:
  CVE-2016-2545

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1549182] Re: CVE-2016-2544

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549182

Title:
  CVE-2016-2544

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1546177] Re: CVE-2016-2384

[Steve Beattie]

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  CVE-2016-2384

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in 

[Kernel-packages] [Bug 1538429] Re: CVE-2016-2069

[Steve Beattie]

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1538429

Title:
  CVE-2016-2069

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-lts-wily source package in Vivid:
  Invalid
Status in linux-lts-xenial 

[Kernel-packages] [Bug 1533042] Re: CVE-2015-8767

[Steve Beattie]

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

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1533042

Title:
  CVE-2015-8767

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in 

[Kernel-packages] [Bug 1533044] Re: CVE-2016-0723

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

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

** Changed in: linux-lts-vivid (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1533044

Title:
  CVE-2016-0723

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  

[Kernel-packages] [Bug 1549181] Re: CVE-2016-2543

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1549181

Title:
  CVE-2016-2543

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source 

[Kernel-packages] [Bug 1527643] Re: use after free of task_struct->numa_faults in task_numa_find_cpu

[Kamal Mostafa]

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

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

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

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

Title:
  use after free of task_struct->numa_faults in task_numa_find_cpu

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The use-after-free invalid read bug, which happens in really tricky
  case, would use the numa_faults data already freed for the NUMA
  balance to make a decision to migrate the exiting process.

  The bug was found by the Ubuntu-3.13.0-65 with KASan backported.
  binary package:
  http://kernel.ubuntu.com/~gavinguo/kasan/Ubuntu-3.13.0-65.105/

  source code:
  
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=Ubuntu-3.13.0-65-kasan

  ==
  BUG: KASan: use after free in task_numa_find_cpu+0x64c/0x890 at addr 
880dd393ecd8
  Read of size 8 by task qemu-system-x86/3998900
  =
  BUG kmalloc-128 (Tainted: G B ): kasan: bad access detected
  -

  INFO: Allocated in task_numa_fault+0xc1b/0xed0 age=41980 cpu=18 pid=3998890
  __slab_alloc+0x4f8/0x560
  __kmalloc+0x1eb/0x280
  task_numa_fault+0xc1b/0xed0
  do_numa_page+0x192/0x200
  handle_mm_fault+0x808/0x1160
  __do_page_fault+0x218/0x750
  do_page_fault+0x1a/0x70
  page_fault+0x28/0x30
  SyS_poll+0x66/0x1a0
  system_call_fastpath+0x1a/0x1f
  INFO: Freed in task_numa_free+0x1d2/0x200 age=62 cpu=18 pid=0
  __slab_free+0x2ab/0x3f0
  kfree+0x161/0x170
  task_numa_free+0x1d2/0x200
  finish_task_switch+0x1d2/0x210
  __schedule+0x5d4/0xc60
  schedule_preempt_disabled+0x40/0xc0
  cpu_startup_entry+0x2da/0x340
  start_secondary+0x28f/0x360
  INFO: Slab 0xea00374e4f00 objects=37 used=17 fp=0x880dd393ecb0 
flags=0x6004080
  INFO: Object 0x880dd393ecb0 @offset=11440 fp=0x880dd393f700

  Bytes b4 880dd393eca0: 0c 00 00 00 18 00 00 00 af 63 3a 04 01 00 00 00 
.c:.
  Object 880dd393ecb0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecc0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecd0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ece0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecf0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed00: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed10: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed20: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 
kkk.
  CPU: 61 PID: 3998900 Comm: qemu-system-x86 Tainted: G B 3.13.0-65-generic #105
  Hardware name: Supermicro X8QB6/X8QB6, BIOS 2.0c 06/11/2
   ea00374e4f00 8816c572b420 81a6ce35 88045f00f500
   8816c572b450 81244aed 88045f00f500 ea00374e4f00
   880dd393ecb0 0012 8816c572b478 8124ac36
  Call Trace:
   [] dump_stack+0x45/0x56
   [] print_trailer+0xfd/0x170
   [] object_err+0x36/0x40
   [] kasan_report_error+0x1e9/0x3a0
   [] kasan_report+0x40/0x50
   [] ? task_numa_find_cpu+0x64c/0x890
   [] __asan_load8+0x69/0xa0
   [] ? find_next_bit+0xd8/0x120
   [] task_numa_find_cpu+0x64c/0x890
   [] task_numa_migrate+0x4ac/0x7b0
   [] numa_migrate_preferred+0xb3/0xc0
   [] task_numa_fault+0xb88/0xed0
   [] do_numa_page+0x192/0x200
   [] handle_mm_fault+0x808/0x1160
   [] ? sched_clock_cpu+0x10d/0x160
   [] ? native_load_tls+0x82/0xa0
   [] __do_page_fault+0x218/0x750
   [] ? hrtimer_try_to_cancel+0x76/0x160
   [] ? schedule_hrtimeout_range_clock.part.24+0xf7/0x1c0
   [] do_page_fault+0x1a/0x70
   [] page_fault+0x28/0x30
   [] ? do_sys_poll+0x1c4/0x6d0
   [] ? enqueue_task_fair+0x4b6/0xaa0
   [] ? sched_clock+0x9/0x10
   [] ? resched_task+0x7a/0xc0
   [] ? check_preempt_curr+0xb3/0x130
   [] ? poll_select_copy_remaining+0x170/0x170
   [] ? wake_up_state+0x10/0x20
   [] ? drop_futex_key_refs.isra.14+0x1f/0x90
   [] ? futex_requeue+0x3de/0xba0
   [] ? do_futex+0xbe/0x8f0
   [] ? read_tsc+0x9/0x20
   [] ? ktime_get_ts+0x12d/0x170
   [] ? 

[Kernel-packages] [Bug 1543980] Re: Kernel 3.13.0-77 crashes (can be triggered by Samba)

[Kamal Mostafa]

This fix (a5527dd af_unix: Guard against other == sk in
unix_dgram_sendmsg) has now been committed to Trusty, scheduled for the
next kernel release (3.13.0-84.128).


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

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

Title:
  Kernel 3.13.0-77 crashes (can be triggered by Samba)

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Ubuntu 14.04.3 LTS

  After updating to kernel 3.13.0-77 system crashes.
  First, network dies, then the whole system.
  There are several kernel crashes in the logs.

  --- snip ---
  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Date: Wed Feb 10 09:20:35 2016
  Failure: oops
  OopsText:
   BUG: soft lockup - CPU#1 stuck for 23s! [smbd:5908]
  --- snap ---

  Followed by kernel stack traces.

  After some investigation, it turned out that the crash can be triggered by 
Samba.
  It's easily reproducible by running the following commands in the Samba 
master branch:
  ./configure.developer
  TDB_NO_FSYNC=1 make -j test FAIL_IMMEDIATELY=1 SOCKET_WRAPPER_KEEP_PCAP=1 
TESTS="samba3.raw.composite"

  Downgrading to kernel 3.13.0-76 solves this problem.

  Please let me know if we can provide more information or help testing.

  Thanks!

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

-- 
Mailing list: https://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 1557191] Re: Trusty update to v3.13.11-ckt36 stable release

[Kamal Mostafa]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v3.13.11-ckt36 upstream 
stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v3.13.11-ckt36 upstream 
stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://kernel.ubuntu.com/ubuntu/linux.git
  
-git://kernel.ubuntu.com/ubuntu/linux.git
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v3.13.11-ckt36 stable release
+ shall be applied:
  
-The following patches from the v3.13.11-ckt36 stable release
- shall be applied:
+ Linux 3.13.11-ckt36
+ pipe: limit the per-user amount of pages allocated in pipes
+ af_unix: Don't set err in unix_stream_read_generic unless there was an error
+ net/mlx4_en: Choose time-stamping shift value according to HW frequency
+ ipv4: fix memory leaks in ip_cmsg_send() callers
+ bonding: Fix ARP monitor validation
+ sctp: Fix port hash table size computation
+ unix_diag: fix incorrect sign extension in unix_lookup_by_ino
+ rtnl: RTM_GETNETCONF: fix wrong return value
+ pppoe: fix reference counting in PPPoE proxy
+ net/mlx4_en: Count HW buffer overrun only once
+ qmi_wwan: add "4G LTE usb-modem U901"
+ af_unix: Guard against other == sk in unix_dgram_sendmsg
+ sctp: translate network order to host order when users get a hmacid
+ net:Add sysctl_max_skb_frags
+ unix: correctly track in-flight fds in sending process user_struct
+ ipv6: fix a lockdep splat
+ net/ipv6: add sysctl option accept_ra_min_hop_limit
+ ipv6/udp: use sticky pktinfo egress ifindex on connect()
+ sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
+ pptp: fix illegal memory access caused by multiple bind()s
+ af_unix: fix struct pid memory leak
+ tcp: fix NULL deref in tcp_v4_send_ack()
+ net: dp83640: Fix tx timestamp overflow handling.
+ af_iucv: Validate socket address length in iucv_sock_bind()
+ do_last(): don't let a bogus return value from ->open() et.al. to confuse us
+ hpfs: don't truncate the file when delete fails
+ KVM: x86: MMU: fix ubsan index-out-of-range warning
+ libceph: don't bail early from try_read() when skipping a message
+ tracing: Fix showing function event in available_events
+ KVM: async_pf: do not warn on page allocation failures
+ sunrpc/cache: fix off-by-one in qword_get()
+ can: ems_usb: Fix possible tx overflow
+ drivers: android: correct the size of struct binder_uintptr_t for 
BC_DEAD_BINDER_DONE
+ kernel/resource.c: fix muxed resource handling in __request_region()
+ ext4: fix crashes in dioread_nolock mode
+ ext4: fix bh->b_state corruption
+ hwmon: (ads1015) Handle negative conversion values correctly
+ USB: option: add "4G LTE usb-modem U901"
+ USB: cp210x: add IDs for GE B650V3 and B850V3 boards
+ USB: option: add support for SIM7100E
+ NFSv4: Fix a dentry leak on alias use
+ drm/qxl: use kmalloc_array to alloc reloc_info in qxl_process_single_command
+ drm/radeon: use post-decrement in error handling
+ ALSA: seq: Fix double port list deletion
+ tracing: Fix freak link error caused by branch tracer
+ tracepoints: Do not trace when cpu is offline
+ dmaengine: dw: disable BLOCK IRQs for non-cyclic xfer
+ ALSA: seq: Fix leak of pool buffer at concurrent writes
+ ALSA: seq: Drop superfluous error/debug messages after malloc failures
+ xen/pcifront: Fix mysterious crashes when NUMA locality information was 
extracted.
+ xen/pciback: Save the number of MSI-X entries to be copied later.
+ xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY
+ bio: return EINTR if copying to user space got interrupted
+ ext4: don't read blocks from disk after extents being swapped
+ ext4: fix potential integer overflow
+ btrfs: properly set the termination value of ctx->pos in readdir
+ ARM: 8519/1: ICST: try other dividends than 1
+ s390/dasd: fix refcount for PAV reassignment
+ s390/dasd: prevent incorrect length error under z/VM after PAV changes
+ cifs: fix erroneous return value
+ workqueue: handle NUMA_NO_NODE for unbound pool_workqueue lookup
+ ahci: Intel DNV device IDs SATA
+ drm/i915: fix error path in intel_setup_gmbus()
+ phy: twl4030-usb: Relase usb phy on unload
+ ALSA: timer: Fix race at concurrent reads
+ ALSA: timer: Fix race 

[Kernel-packages] [Bug 1557151] Re: ZFS: send fails to transmit some holes [corruption]

[Tim Gardner]

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

** Also affects: zfs-linux (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
   Status: In Progress

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

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

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

Title:
  ZFS: send fails to transmit some holes [corruption]

Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  
https://github.com/zfsonlinux/zfs/commit/c352ec27d5c5ecea8f6af066258dfd106085eaac

  "In certain circumstances, "zfs send -i" (incremental send) can produce
  a stream which will result in incorrect sparse file contents on the
  target.

  The problem manifests as regions of the received file that should be
  sparse (and read a zero-filled) actually contain data from a file that
  was deleted (and which happened to share this file's object ID)."

  This bug causes data corruption, and has privacy/security
  implications. I think we need to get this fix into Xenial ASAP.

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

-- 
Mailing list: https://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 1550351] Re: [Asus P8Z68-V LX] suspend/resume failure

[WinEunuchs2Unix]

I'd like to delete my previous two comments because on a second Suspend
under 3.13.0-32 the laptop resumed immediately and led to a system crash
again. However I'm loath to delete what's already been written.

A few months whilst still running Windows 7 ago I changed the BIOS to
wake on USB activity for a now shelved project for the UPS triggered USB
interrupt to send out an e-mail that the power has gone off.

It turns out syslog under Ubuntu is now being spammed with the message:
 "hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?"

Turning off the BIOS option to wake up on USB fixed the problem with
immediate Resume after Suspend followed by crash in Ubuntu. I don't have
Windows 7 reinstalled yet to see if the same happens there.

My apologies to those I mislead based on one-time test results. The new
test results have proven true 3 times so far :).

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

Title:
  [Asus P8Z68-V LX] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Got crash message upon booting after update.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-79-generic 3.13.0-79.123
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  don2040 F pulseaudio
   /dev/snd/controlC0:  don2040 F pulseaudio
  Date: Thu Feb 25 15:38:44 2016
  DuplicateSignature: suspend/resume:System manufacturer System Product 
Name:0401
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=ffd2b5a3-0e8e-4f9b-9288-cff133a90145
  InstallationDate: Installed on 2011-12-18 (1530 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python3.4
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic 
root=UUID=9f13b409-27bd-4e42-99c0-59fccdb87241 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  SourcePackage: linux
  Title: [System manufacturer System Product Name] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-08-18 (557 days ago)
  UserGroups:
   
  dmi.bios.date: 07/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://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 1557151] Missing required logs.

[Brad Figg]

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

apport-collect 1557151

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

Title:
  ZFS: send fails to transmit some holes [corruption]

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  
https://github.com/zfsonlinux/zfs/commit/c352ec27d5c5ecea8f6af066258dfd106085eaac

  "In certain circumstances, "zfs send -i" (incremental send) can produce
  a stream which will result in incorrect sparse file contents on the
  target.

  The problem manifests as regions of the received file that should be
  sparse (and read a zero-filled) actually contain data from a file that
  was deleted (and which happened to share this file's object ID)."

  This bug causes data corruption, and has privacy/security
  implications. I think we need to get this fix into Xenial ASAP.

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

-- 
Mailing list: https://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 1557151] Re: ZFS: send fails to transmit some holes [corruption]

[Tim Gardner]

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

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

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

Title:
  ZFS: send fails to transmit some holes [corruption]

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  
https://github.com/zfsonlinux/zfs/commit/c352ec27d5c5ecea8f6af066258dfd106085eaac

  "In certain circumstances, "zfs send -i" (incremental send) can produce
  a stream which will result in incorrect sparse file contents on the
  target.

  The problem manifests as regions of the received file that should be
  sparse (and read a zero-filled) actually contain data from a file that
  was deleted (and which happened to share this file's object ID)."

  This bug causes data corruption, and has privacy/security
  implications. I think we need to get this fix into Xenial ASAP.

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

-- 
Mailing list: https://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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

[Manu Cogolludo]

Lenovo Think Pad X1 Carbon Intel® Core™ i7-5600U CPU @ 2.60GHz × 4

Kernel solved

uname -a

Linux  4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a recent intel NUC using i915 graphics, I get the following errors
  in dmesg:

  [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
  lied (SDE)!

  There are two monitors connected to this box, one with mini-
  HDMI->HDMI, one with mini-DP->HDMI cable.

  Maybe related:

  https://bugs.freedesktop.org/show_bug.cgi?id=80896

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.26.25
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Wed Aug 26 10:07:31 2015
  InstallationDate: Installed on 2015-08-01 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1528684] Re: Error parsing PCC subspaces from PCCT

[Manu Cogolludo]

Error is also an Lenovo Think Pad X1 Carbon, Intel® Core™ i7-5600U CPU @
2.60GHz × 4


sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

N14ET32W (1.10 )
08/13/2015

uname  -a

4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Error parsing PCC subspaces from PCCT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my Thinkpad laptop I am seeing this error every time after the boot
  in the dmesg output:

  "Error parsing PCC subspaces from PCCT" (Portable C Compiler)

  The attached log files should reveal more. I have no idea what it
  means but seems serious. Hope you can solve this for once and all?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael-heuberger   2972 F pulseaudio
   /dev/snd/controlC1:  michael-heuberger   2972 F pulseaudio
  Date: Wed Dec 23 09:36:44 2015
  HibernationDevice: RESUME=UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a
  InstallationDate: Installed on 2015-05-22 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20A7006KAU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 ro cgroup_enable=memory 
swapaccount=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-15 (36 days ago)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET42WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A7006KAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET42WW(1.19):bd11/20/2014:svnLENOVO:pn20A7006KAU:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7006KAU:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A7006KAU
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Alex Ng]

In addition to what @jrp mentioned, I would also add:

b9830d120cbe155863399f25eaef6aa8353e767f "Drivers: hv: util: Pass the
channel information during the init call"

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

-- 
Mailing list: https://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 1557151] Re: ZFS: send fails to transmit some holes [corruption]

[Seth Arnold]

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

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

Title:
  ZFS: send fails to transmit some holes [corruption]

Status in linux package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  
https://github.com/zfsonlinux/zfs/commit/c352ec27d5c5ecea8f6af066258dfd106085eaac

  "In certain circumstances, "zfs send -i" (incremental send) can produce
  a stream which will result in incorrect sparse file contents on the
  target.

  The problem manifests as regions of the received file that should be
  sparse (and read a zero-filled) actually contain data from a file that
  was deleted (and which happened to share this file's object ID)."

  This bug causes data corruption, and has privacy/security
  implications. I think we need to get this fix into Xenial ASAP.

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

-- 
Mailing list: https://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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joshua R. Poulson]

That's drivers/hv/hv_snapshot.c

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

-- 
Mailing list: https://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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joshua R. Poulson]

A few more upstream commits to make sure are present:
drivers/hv/

2d0c3b5a... "hv: utils: Invoke the poll function after handshake" (could be the 
smoking gun here)
ed9ba608... "hv: vss: run only on support host versions" (I think we got this 
one in another bug)
3cace4a61... "hv: utils: run polling callback always in interrupt context" (We 
probably got this one as a prereq)

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

-- 
Mailing list: https://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 1557191] [NEW] Trusty update to v3.13.11-ckt36 stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

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

   git://kernel.ubuntu.com/ubuntu/linux.git

TEST CASE: TBD

   The following patches from the v3.13.11-ckt36 stable release
shall be applied:

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Trusty update to v3.13.11-ckt36 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Trusty:
  New

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 v3.13.11-ckt36 upstream 
stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

 The following patches from the v3.13.11-ckt36 stable release
  shall be applied:

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

-- 
Mailing list: https://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 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic

[Christopher M. Penalver]

ais523, 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.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags removed: bios-outdated-f.68
** Tags added: latest-bios-f.68

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

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

Title:
  Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
  causes an endless reset loop or a kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce (happens > 50% of the time, but not every time):

  Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable
  while both the device and computer are on (i.e. hotplug).

  Observed symptoms:
  - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the 
LEDs on the front of the device flashing rapidly), being reset approximately 
every 200ms; on such occasions, the Ubuntu user interface often reacts as 
though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly 
adding an "Audio CD" icon to the launcher and then removing it, and putting up 
dialog boxes complaining about failure to read the data).
  - sometimes the kernel panics (often some time after the reset loop starts, 
perhaps up to 10 seconds); when this happens there was always or nearly always 
a reset loop occurring beforehand.
  - sometimes the device resets once or not at all, then works as expected 
(showing up as a network interface, and allowing me to communicate to the 
Internet with a wired connection); I'm currently using an Osprey 2 Mini for 
this purpose right now.

  The kernel panics lock up the entire system (forcing a hard power
  off). lt-Sysrq commands don't work in this state (even though I have
  them enabled), and sometimes the Caps Lock light flashes repeatedly.
  The logs end some time before the panic occurs.

  /var/log/syslog:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog

  The reset loops also occurred when I was using Ubuntu vivid. The
  kernel panics only happened after an upgrade to wily. Output of lsusb
  -v is attached.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 6233 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007
  InstallationDate: Installed on 2014-06-03 (648 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1556247] modoc (ppc64el) - tests ran: 22, failed: 5

[Brad Figg]

tests ran:  22, failed: 5;
  
http://kernel.ubuntu.com/testing/4.4.0-13.29/modoc__4.4.0-13.29__2016-03-14_21-02-00/results-index.html

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

Title:
  linux: 4.4.0-13.29 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
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:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-13.29 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-Prepare-package-start:Friday, 11. March 2016 19:07 UTC
  kernel-phase-changed:Friday, 11. March 2016 19:07 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Friday, 11. March 2016 20:00 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1556247/+subscriptions

-- 
Mailing list: https://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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Stunts]

@Marco:
Just "press" "Enter" and the file should be saved. Don't worry about that 
message. Nano always asks that question before saving a file.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

-- 
Mailing list: https://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 1556577] Re: [ASUSTeK Computer Inc. hostname] hibernate/resume failure

[Christopher M. Penalver]

Tomasz Kazimierczak, 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.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

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

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

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1556577

Title:
  [ASUSTeK Computer Inc. hostname] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  pm-hibernate does not work

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-11-generic 4.4.0-11.26
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1146 F pulseaudio
tomasz 1680 F pulseaudio
  Date: Sun Mar 13 10:50:26 2016
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. U36SD:U36SD.205
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2016-02-24 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  InterpreterPath: /usr/bin/python3.5
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic 
root=UUID=a638f00b-30bc-492b-b280-8240260e63d8 ro quiet splash pcie_aspm=force 
elevator=noop vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-11-generic N/A
   linux-backports-modules-4.4.0-11-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. hostname] hibernate/resume failure
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (11 days ago)
  UserGroups:
   
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  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.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U36SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:

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

[Mike Gerow]

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

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

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

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

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1528684] Re: Error parsing PCC subspaces from PCCT

[Guy Taylor]

This error is also present on an Asus ZenBook UX305F

uname -a
Linux other-laptop 4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
UX305FA.210
05/19/2015

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

Title:
  Error parsing PCC subspaces from PCCT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my Thinkpad laptop I am seeing this error every time after the boot
  in the dmesg output:

  "Error parsing PCC subspaces from PCCT" (Portable C Compiler)

  The attached log files should reveal more. I have no idea what it
  means but seems serious. Hope you can solve this for once and all?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael-heuberger   2972 F pulseaudio
   /dev/snd/controlC1:  michael-heuberger   2972 F pulseaudio
  Date: Wed Dec 23 09:36:44 2015
  HibernationDevice: RESUME=UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a
  InstallationDate: Installed on 2015-05-22 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20A7006KAU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 ro cgroup_enable=memory 
swapaccount=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-15 (36 days ago)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET42WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A7006KAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET42WW(1.19):bd11/20/2014:svnLENOVO:pn20A7006KAU:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7006KAU:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A7006KAU
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1556782] Re: USB3 not working

[cangaru]

** Tags added: apport-collected trusty

** Description changed:

  I am constantly getting these messages in dmesg:
  [114755.239681] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [114760.252354] usb 2-1: device descriptor read/8, error -110
  [114760.353433] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [114765.366486] usb 2-1: device descriptor read/8, error -110
  [114765.518703] sd 6:0:0:0: [sdf] FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [114765.518705] usb 2-1: USB disconnect, device number 2
  [114765.518707] sd 6:0:0:0: [sdf] CDB: 
  [114765.518708] Write(10): 2a 00 3a 36 db b7 00 00 10 00
  [114765.518712] blk_update_request: I/O error, dev sdf, sector 976673719
  [114765.518720] Aborting journal on device sdf1-8.
  [114765.524571] sd 6:0:0:0: [sdf] FAILED Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
  
  I am trying to use a Toshiba external disk, in a usb3 port which I use for 
backup. It worked flawlessly on an old version of Redhat, but on moving to a 
new server, Intel S1200RP with updated firmware, I am in a world of pain. I 
have switched off standby for usb on boot, I have ensured that power is 
continually on for all usb ports. 
  I have tried a number of kernels, currently 3.19.0-031900rc4-lowlatency which 
had been less bad, but am still getting this fault.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2015-05-13 (306 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_AU:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
+ Tags:  trusty
+ Uname: Linux 3.19.0-031900rc4-lowlatency x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

Title:
  USB3 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am constantly getting these messages in dmesg:
  [114755.239681] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [114760.252354] usb 2-1: device descriptor read/8, error -110
  [114760.353433] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [114765.366486] usb 2-1: device descriptor read/8, error -110
  [114765.518703] sd 6:0:0:0: [sdf] FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [114765.518705] usb 2-1: USB disconnect, device number 2
  [114765.518707] sd 6:0:0:0: [sdf] CDB: 
  [114765.518708] Write(10): 2a 00 3a 36 db b7 00 00 10 00
  [114765.518712] blk_update_request: I/O error, dev sdf, sector 976673719
  [114765.518720] Aborting journal on device sdf1-8.
  [114765.524571] sd 6:0:0:0: [sdf] FAILED Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK

  I am trying to use a Toshiba external disk, in a usb3 port which I use for 
backup. It worked flawlessly on an old version of Redhat, but on moving to a 
new server, Intel S1200RP with updated firmware, I am in a world of pain. I 
have switched off standby for usb on boot, I have ensured that power is 
continually on for all usb ports. 
  I have tried a number of kernels, currently 3.19.0-031900rc4-lowlatency which 
had been less bad, but am still getting this fault.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-05-13 (306 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Tags:  trusty
  Uname: Linux 3.19.0-031900rc4-lowlatency x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic

[ais523]

Oh, and recovering from a reset loop spontaneously doesn't always
happen, on an earlier occasion, I was stuck in a reset loop for several
minutes before I decided to disconnect the device to see if, when and
how the system would crash.

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

Title:
  Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
  causes an endless reset loop or a kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce (happens > 50% of the time, but not every time):

  Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable
  while both the device and computer are on (i.e. hotplug).

  Observed symptoms:
  - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the 
LEDs on the front of the device flashing rapidly), being reset approximately 
every 200ms; on such occasions, the Ubuntu user interface often reacts as 
though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly 
adding an "Audio CD" icon to the launcher and then removing it, and putting up 
dialog boxes complaining about failure to read the data).
  - sometimes the kernel panics (often some time after the reset loop starts, 
perhaps up to 10 seconds); when this happens there was always or nearly always 
a reset loop occurring beforehand.
  - sometimes the device resets once or not at all, then works as expected 
(showing up as a network interface, and allowing me to communicate to the 
Internet with a wired connection); I'm currently using an Osprey 2 Mini for 
this purpose right now.

  The kernel panics lock up the entire system (forcing a hard power
  off). lt-Sysrq commands don't work in this state (even though I have
  them enabled), and sometimes the Caps Lock light flashes repeatedly.
  The logs end some time before the panic occurs.

  /var/log/syslog:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog

  The reset loops also occurred when I was using Ubuntu vivid. The
  kernel panics only happened after an upgrade to wily. Output of lsusb
  -v is attached.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 6233 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007
  InstallationDate: Installed on 2014-06-03 (648 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-32-generic x86_64
  UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2186
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1557129] Re: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Brad Aytes]

Is there a fix/patch for this, or is it still being investigated? No
worries, no rush, just curious.

Thanks,

Brad

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error Msg Displays After Each Restart

  Would Only Allow Me To Attach 1 File ("version.log"),

  Below Is lspci-vnvn.log:

  

  00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller 
[1028:04f5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Dell Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [1028:04f5]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in 

[Kernel-packages] [Bug 1557172] Missing required logs.

[Brad Figg]

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

apport-collect 1557172

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

** Tags added: 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/1557172

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic

[ais523]

Thanks. I found the update in question. (It seems that some HP BIOS
updates install on Linux, and others require Windows; luckily I had a
dual-boot setup available to install it.)

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F.68
09/21/2015

I can confirm that the issue still occurs. I also determined some
further information:

- The hangs are definitely triggered upon disconnecting the device (or
turning it off) during a reset loop. This has a 100% correlation so far;
if it's not in a reset loop when I disconnect it (even if there was a
loop earlier), the kernel is fine, and if it's in a reset loop but I
don't disconnect it, the kernel is also fine.

- The kernel/device have, on occasion, recovered from a reset loop
"spontaneously" after several seconds. (This has happened twice now.) My
current boot is one such occasion; I attached the device while the
system was booting (reasonably late in the boot sequence), and the reset
loop stopped after a while. I've attached the syslog from this boot
session, in case it helps.

- I managed to catch one of the non-panic hangs (i.e. computer responds
to no input, not even Alt-SysRq combinations, but the Caps Lock light
does not flash) while on the Ctrl-Alt-F1 text terminal. It happened when
I disconnected the Osprey Mini 2 during a reset loop, and started (as
happens in other cases) with text scrolling far too fast to read. Then
it stabilized into displaying messages about CPUs being stuck every 20s
or so. One of them was along the lines of "CPU #2 HARD lockup" (I forget
the exact phrasing, and didn't have time to write it down or take a
photograph); all the others mentioned other CPUs (mostly CPU #3). The
error message for CPU #3 was always almost the same:

NMI watchdog: BUG: CPU #3 stuck for 22s! [apache2:4544]

(the time shown changed on occasion, sometimes it was 21s)

The information only stayed onscreen for a limited time, so I couldn't
write much down; I decided that the top of the stack trace would
probably be the most helpful piece of information for debugging:

queue_read_lock_slowpath+0x92/0xa0
_raw_read_lock+0x1c/0x20
no_wait [I didn't write down the offsets from here on so that I could get more 
of the stack]
SyS_wait4
? _task_stopped_code

Additionally, after a while of this, the CPU fan settled on a speed that
it normally reaches if 1 of my 4 cores is running at 100% and the others
are all idle. It thus seems most likely that CPU #2 was in a tight loop,
and the other CPUs were blocking on locks that CPU #1 held, thus
preventing the system making any progress.

- The error message in the panic case is not always the same. I've seen
a few different stacktraces, and although I can't remember the details,
they were definitely different each time.

** Attachment added: "system spontaneously recovering from a reset loop"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4599246/+files/syslog

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

Title:
  Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
  causes an endless reset loop or a kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce (happens > 50% of the time, but not every time):

  Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable
  while both the device and computer are on (i.e. hotplug).

  Observed symptoms:
  - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the 
LEDs on the front of the device flashing rapidly), being reset approximately 
every 200ms; on such occasions, the Ubuntu user interface often reacts as 
though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly 
adding an "Audio CD" icon to the launcher and then removing it, and putting up 
dialog boxes complaining about failure to read the data).
  - sometimes the kernel panics (often some time after the reset loop starts, 
perhaps up to 10 seconds); when this happens there was always or nearly always 
a reset loop occurring beforehand.
  - sometimes the device resets once or not at all, then works as expected 
(showing up as a network interface, and allowing me to communicate to the 
Internet with a wired connection); I'm currently using an Osprey 2 Mini for 
this purpose right now.

  The kernel panics lock up the entire system (forcing a hard power
  off). lt-Sysrq commands don't work in this state (even though I have
  them enabled), and sometimes the Caps Lock light flashes repeatedly.
  The logs end some time before the panic occurs.

  /var/log/syslog:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog

  The reset loops also occurred when I was using Ubuntu vivid. The
  kernel panics only happened after an upgrade to 

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

[Mike Gerow]

Public bug reported:

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

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

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

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

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

[Kernel-packages] [Bug 1556577] Re: [ASUSTeK Computer Inc. hostname] hibernate/resume failure

[Tomasz Kazimierczak]

After updating BiOS sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date  gives this
U36SD.206
09/26/2011

which I suppose it should since i've updated it exactly to this (i
presume the latest) version.

But now pm-hibernate literally do nothing, or at least I do not observe that 
anything happens,
except this record in /var/log/syslog:
Mar 14 21:34:44 U36SD systemd[1]: Stopped Run anacron jobs.

An that's it! no hibernation, no crush, even no screen blink. Swap also
stays untouched.

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

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

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

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

Title:
  [ASUSTeK Computer Inc. hostname] hibernate/resume failure

Status in linux package in Ubuntu:
  In Progress

Bug description:
  pm-hibernate does not work

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-11-generic 4.4.0-11.26
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1146 F pulseaudio
tomasz 1680 F pulseaudio
  Date: Sun Mar 13 10:50:26 2016
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. U36SD:U36SD.205
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2016-02-24 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  InterpreterPath: /usr/bin/python3.5
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic 
root=UUID=a638f00b-30bc-492b-b280-8240260e63d8 ro quiet splash pcie_aspm=force 
elevator=noop vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-11-generic N/A
   linux-backports-modules-4.4.0-11-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. hostname] hibernate/resume failure
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (11 days ago)
  UserGroups:
   
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  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.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U36SD
  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/1556577/+subscriptions

-- 
Mailing list: https://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 1543419] Re: ubuntu 14.04.4 installation with "Guided - use entire disk and set up LVM" fails for ext3 file system.

[Tim Gardner]

Try it on another machine ?

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

Title:
  ubuntu 14.04.4 installation with "Guided - use entire disk and set up
  LVM" fails for ext3 file system.

Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description
  ===
  ubuntu 14.04.4 installation on Firestone baremetal with "Guided - use entire 
disk and set up LVM" fails when ext3 is chosen as / file system. Below error 
message is displayed.

  
  ? [!!] Partition disks ?
  ?  ?
  ?Failed to create a file system?
  ? The ext3 file system creation in partition #1 of LVM VG FR21p01-vg,  ?
  ? LV root failed.  ?
  ?  ?
  ?   ?
  ?  ?
  

  
  Steps to Reproduce
  =
  1. Start netboot installation on Firestone baremetal machine from 
  
http://ports.ubuntu.com/ubuntu-ports/dists/trusty-proposed/main/installer-ppc64el/current/images/wily-netboot/
  2. During "Partition disks" select 
  Manual -> Guided partitioning -> Guided - use entire disk and set up LVM

?? [!!] Partition disks ???
? ?
? The installer can guide you through partitioning a disk (using  ?
? different standard schemes) or, if you prefer, you can do it?
? manually. With guided partitioning you will still have a chance later   ?
? to review and customise the results.?
? ?
? If you choose guided partitioning for an entire disk, you will next ?
? be asked which disk should be used. ?
? ?
? Partitioning method:?
? ?
?  Guided - use entire partition, SCSI5 (0,0,0), partition #2 (sdk)   ?
?  Guided - use the largest continuous free space ?   ?
?  Guided - use entire disk and set up LVM?   ?
?  Guided - use entire disk and set up encrypted LVM  ?
?  Manual ?
? ?
??
? ?
???

?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  Guided partitioning?
?  Configure software RAID?
?  Configure the Logical Volume Manager   ?   ?
?  Configure encrypted volumes?   ?
?  Configure iSCSI volumes?   ?
? ?   ?
?  LVM VG tul8p1-vg, LV root - 959.4 GB Linux device-mapper (linear)  ?   ?
?  > #1959.4 GBxfs?   ?
?  LVM VG tul8p1-vg, LV swap_1 - 40.5 GB Linux device-mapper (linear  ?   ?
?  > #1 40.5 GB F  swap  swap ?
? ?
??
? ?

[Kernel-packages] [Bug 1556247] Re: linux: 4.4.0-13.29 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-development-workflow/automated-testing
   Status: Incomplete => 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/1556247

Title:
  linux: 4.4.0-13.29 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
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:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-13.29 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-Prepare-package-start:Friday, 11. March 2016 19:07 UTC
  kernel-phase-changed:Friday, 11. March 2016 19:07 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Friday, 11. March 2016 20:00 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1556247/+subscriptions

-- 
Mailing list: https://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 1557138] Re: Request to cherry-pick uvcvideo patch for Xenial kernel support of RealSense camera

[Tim Gardner]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
   Status: Triaged

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

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

Title:
  Request to cherry-pick uvcvideo patch for Xenial kernel support of
  RealSense camera

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

Bug description:
  The Raspberry-Pi form factor compatible UP board from Aaeon now
  supports RealSense depth enabled camera (http://www.up-
  board.org/kickstarter/up-intel-realsense-technology/) , and Intel has
  made a significant contribution to open source by supporting Robot
  Operating System code enabling use of that camera.  The current v4.4
  kernel has all patches merged to support RealSense camera, except v4.5
  change-id 120c41d3477a23c6941059401db63677736f1935 from
  https://github.com/torvalds/linux.git, which has a few minor editions
  to support required camera depth format.

  Can you please include this cherry-pick in the official Xenial kernel
  for 16.04 LTS?  This would enabled customers to avoid having to hand-
  patch uvcvideo.ko

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

-- 
Mailing list: https://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 1555434] Re: Black screen/system lockup on 4.4.0-11

[Joe Barnett]

I've just tested again with 4.4.0-10-generic and 4.4.0-9-generic, and
those kernels are seeing the same issue.  Perhaps this is a bug in X,
not the kernel?  Let me know if you still want me to test 4.4.3/4.4.4.

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

Title:
  Black screen/system lockup on 4.4.0-11

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2016-March/016281.html references xenial freezing when
  plugging in a 2nd monitor on a 2015 macbook pro.  I'm seeing similar
  freezes when _unplugging_ the 2nd monitor -- the screen turns black
  and everything is unresponsive.  Not sure that it happens every time,
  but have noticed it multiple times today (first time booting with
  4.4.0-11), and have not seen it before today (yesterday was booting
  4.4.0-10 and the freeze did not occur).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-11-generic 4.4.0-11.26
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   2270 F pulseaudio
   /dev/snd/controlC1:  jbarnett   2270 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Mar  9 20:31:07 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945
  InstallationDate: Installed on 2015-08-21 (201 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  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=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-11-generic N/A
   linux-backports-modules-4.4.0-11-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

-- 
Mailing list: https://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 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic

[Christopher M. Penalver]

ais523, you didn't see F.68 because HP interferes with the URL based on
browser agent string. You have to click to the right of "Software
available for your operating system:" the word "Change" to see other
options.

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

Title:
  Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
  causes an endless reset loop or a kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce (happens > 50% of the time, but not every time):

  Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable
  while both the device and computer are on (i.e. hotplug).

  Observed symptoms:
  - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the 
LEDs on the front of the device flashing rapidly), being reset approximately 
every 200ms; on such occasions, the Ubuntu user interface often reacts as 
though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly 
adding an "Audio CD" icon to the launcher and then removing it, and putting up 
dialog boxes complaining about failure to read the data).
  - sometimes the kernel panics (often some time after the reset loop starts, 
perhaps up to 10 seconds); when this happens there was always or nearly always 
a reset loop occurring beforehand.
  - sometimes the device resets once or not at all, then works as expected 
(showing up as a network interface, and allowing me to communicate to the 
Internet with a wired connection); I'm currently using an Osprey 2 Mini for 
this purpose right now.

  The kernel panics lock up the entire system (forcing a hard power
  off). lt-Sysrq commands don't work in this state (even though I have
  them enabled), and sometimes the Caps Lock light flashes repeatedly.
  The logs end some time before the panic occurs.

  /var/log/syslog:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog

  The reset loops also occurred when I was using Ubuntu vivid. The
  kernel panics only happened after an upgrade to wily. Output of lsusb
  -v is attached.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 6233 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007
  InstallationDate: Installed on 2014-06-03 (648 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-32-generic x86_64
  UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2186
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1527643] Re: use after free of task_struct->numa_faults in task_numa_find_cpu

[Tim Gardner]

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

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

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

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

Title:
  use after free of task_struct->numa_faults in task_numa_find_cpu

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The use-after-free invalid read bug, which happens in really tricky
  case, would use the numa_faults data already freed for the NUMA
  balance to make a decision to migrate the exiting process.

  The bug was found by the Ubuntu-3.13.0-65 with KASan backported.
  binary package:
  http://kernel.ubuntu.com/~gavinguo/kasan/Ubuntu-3.13.0-65.105/

  source code:
  
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=Ubuntu-3.13.0-65-kasan

  ==
  BUG: KASan: use after free in task_numa_find_cpu+0x64c/0x890 at addr 
880dd393ecd8
  Read of size 8 by task qemu-system-x86/3998900
  =
  BUG kmalloc-128 (Tainted: G B ): kasan: bad access detected
  -

  INFO: Allocated in task_numa_fault+0xc1b/0xed0 age=41980 cpu=18 pid=3998890
  __slab_alloc+0x4f8/0x560
  __kmalloc+0x1eb/0x280
  task_numa_fault+0xc1b/0xed0
  do_numa_page+0x192/0x200
  handle_mm_fault+0x808/0x1160
  __do_page_fault+0x218/0x750
  do_page_fault+0x1a/0x70
  page_fault+0x28/0x30
  SyS_poll+0x66/0x1a0
  system_call_fastpath+0x1a/0x1f
  INFO: Freed in task_numa_free+0x1d2/0x200 age=62 cpu=18 pid=0
  __slab_free+0x2ab/0x3f0
  kfree+0x161/0x170
  task_numa_free+0x1d2/0x200
  finish_task_switch+0x1d2/0x210
  __schedule+0x5d4/0xc60
  schedule_preempt_disabled+0x40/0xc0
  cpu_startup_entry+0x2da/0x340
  start_secondary+0x28f/0x360
  INFO: Slab 0xea00374e4f00 objects=37 used=17 fp=0x880dd393ecb0 
flags=0x6004080
  INFO: Object 0x880dd393ecb0 @offset=11440 fp=0x880dd393f700

  Bytes b4 880dd393eca0: 0c 00 00 00 18 00 00 00 af 63 3a 04 01 00 00 00 
.c:.
  Object 880dd393ecb0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecc0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecd0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ece0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecf0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed00: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed10: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed20: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 
kkk.
  CPU: 61 PID: 3998900 Comm: qemu-system-x86 Tainted: G B 3.13.0-65-generic #105
  Hardware name: Supermicro X8QB6/X8QB6, BIOS 2.0c 06/11/2
   ea00374e4f00 8816c572b420 81a6ce35 88045f00f500
   8816c572b450 81244aed 88045f00f500 ea00374e4f00
   880dd393ecb0 0012 8816c572b478 8124ac36
  Call Trace:
   [] dump_stack+0x45/0x56
   [] print_trailer+0xfd/0x170
   [] object_err+0x36/0x40
   [] kasan_report_error+0x1e9/0x3a0
   [] kasan_report+0x40/0x50
   [] ? task_numa_find_cpu+0x64c/0x890
   [] __asan_load8+0x69/0xa0
   [] ? find_next_bit+0xd8/0x120
   [] task_numa_find_cpu+0x64c/0x890
   [] task_numa_migrate+0x4ac/0x7b0
   [] numa_migrate_preferred+0xb3/0xc0
   [] task_numa_fault+0xb88/0xed0
   [] do_numa_page+0x192/0x200
   [] handle_mm_fault+0x808/0x1160
   [] ? sched_clock_cpu+0x10d/0x160
   [] ? native_load_tls+0x82/0xa0
   [] __do_page_fault+0x218/0x750
   [] ? hrtimer_try_to_cancel+0x76/0x160
   [] ? schedule_hrtimeout_range_clock.part.24+0xf7/0x1c0
   [] do_page_fault+0x1a/0x70
   [] page_fault+0x28/0x30
   [] ? do_sys_poll+0x1c4/0x6d0
   [] ? enqueue_task_fair+0x4b6/0xaa0
   [] ? sched_clock+0x9/0x10
   [] ? resched_task+0x7a/0xc0
   [] ? check_preempt_curr+0xb3/0x130
   [] ? poll_select_copy_remaining+0x170/0x170
   [] ? wake_up_state+0x10/0x20
   [] ? drop_futex_key_refs.isra.14+0x1f/0x90
   [] ? futex_requeue+0x3de/0xba0
   [] ? do_futex+0xbe/0x8f0
   [] ? read_tsc+0x9/0x20
   [] ? ktime_get_ts+0x12d/0x170
   [] ? 

[Kernel-packages] [Bug 1557138] Re: Request to cherry-pick uvcvideo patch for Xenial kernel support of RealSense camera

[Leann Ogasawara]

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

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

Title:
  Request to cherry-pick uvcvideo patch for Xenial kernel support of
  RealSense camera

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The Raspberry-Pi form factor compatible UP board from Aaeon now
  supports RealSense depth enabled camera (http://www.up-
  board.org/kickstarter/up-intel-realsense-technology/) , and Intel has
  made a significant contribution to open source by supporting Robot
  Operating System code enabling use of that camera.  The current v4.4
  kernel has all patches merged to support RealSense camera, except v4.5
  change-id 120c41d3477a23c6941059401db63677736f1935 from
  https://github.com/torvalds/linux.git, which has a few minor editions
  to support required camera depth format.

  Can you please include this cherry-pick in the official Xenial kernel
  for 16.04 LTS?  This would enabled customers to avoid having to hand-
  patch uvcvideo.ko

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

-- 
Mailing list: https://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 1527643] Re: use after free of task_struct->numa_faults in task_numa_find_cpu

[Tim Gardner]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Triaged

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

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

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

Title:
  use after free of task_struct->numa_faults in task_numa_find_cpu

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The use-after-free invalid read bug, which happens in really tricky
  case, would use the numa_faults data already freed for the NUMA
  balance to make a decision to migrate the exiting process.

  The bug was found by the Ubuntu-3.13.0-65 with KASan backported.
  binary package:
  http://kernel.ubuntu.com/~gavinguo/kasan/Ubuntu-3.13.0-65.105/

  source code:
  
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=Ubuntu-3.13.0-65-kasan

  ==
  BUG: KASan: use after free in task_numa_find_cpu+0x64c/0x890 at addr 
880dd393ecd8
  Read of size 8 by task qemu-system-x86/3998900
  =
  BUG kmalloc-128 (Tainted: G B ): kasan: bad access detected
  -

  INFO: Allocated in task_numa_fault+0xc1b/0xed0 age=41980 cpu=18 pid=3998890
  __slab_alloc+0x4f8/0x560
  __kmalloc+0x1eb/0x280
  task_numa_fault+0xc1b/0xed0
  do_numa_page+0x192/0x200
  handle_mm_fault+0x808/0x1160
  __do_page_fault+0x218/0x750
  do_page_fault+0x1a/0x70
  page_fault+0x28/0x30
  SyS_poll+0x66/0x1a0
  system_call_fastpath+0x1a/0x1f
  INFO: Freed in task_numa_free+0x1d2/0x200 age=62 cpu=18 pid=0
  __slab_free+0x2ab/0x3f0
  kfree+0x161/0x170
  task_numa_free+0x1d2/0x200
  finish_task_switch+0x1d2/0x210
  __schedule+0x5d4/0xc60
  schedule_preempt_disabled+0x40/0xc0
  cpu_startup_entry+0x2da/0x340
  start_secondary+0x28f/0x360
  INFO: Slab 0xea00374e4f00 objects=37 used=17 fp=0x880dd393ecb0 
flags=0x6004080
  INFO: Object 0x880dd393ecb0 @offset=11440 fp=0x880dd393f700

  Bytes b4 880dd393eca0: 0c 00 00 00 18 00 00 00 af 63 3a 04 01 00 00 00 
.c:.
  Object 880dd393ecb0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecc0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecd0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ece0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ecf0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed00: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed10: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 

  Object 880dd393ed20: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 
kkk.
  CPU: 61 PID: 3998900 Comm: qemu-system-x86 Tainted: G B 3.13.0-65-generic #105
  Hardware name: Supermicro X8QB6/X8QB6, BIOS 2.0c 06/11/2
   ea00374e4f00 8816c572b420 81a6ce35 88045f00f500
   8816c572b450 81244aed 88045f00f500 ea00374e4f00
   880dd393ecb0 0012 8816c572b478 8124ac36
  Call Trace:
   [] dump_stack+0x45/0x56
   [] print_trailer+0xfd/0x170
   [] object_err+0x36/0x40
   [] kasan_report_error+0x1e9/0x3a0
   [] kasan_report+0x40/0x50
   [] ? task_numa_find_cpu+0x64c/0x890
   [] __asan_load8+0x69/0xa0
   [] ? find_next_bit+0xd8/0x120
   [] task_numa_find_cpu+0x64c/0x890
   [] task_numa_migrate+0x4ac/0x7b0
   [] numa_migrate_preferred+0xb3/0xc0
   [] task_numa_fault+0xb88/0xed0
   [] do_numa_page+0x192/0x200
   [] handle_mm_fault+0x808/0x1160
   [] ? sched_clock_cpu+0x10d/0x160
   [] ? native_load_tls+0x82/0xa0
   [] __do_page_fault+0x218/0x750
   [] ? hrtimer_try_to_cancel+0x76/0x160
   [] ? schedule_hrtimeout_range_clock.part.24+0xf7/0x1c0
   [] do_page_fault+0x1a/0x70
   [] page_fault+0x28/0x30
   [] ? do_sys_poll+0x1c4/0x6d0
   [] ? enqueue_task_fair+0x4b6/0xaa0
   [] ? sched_clock+0x9/0x10
   [] ? resched_task+0x7a/0xc0
   [] ? check_preempt_curr+0xb3/0x130
   [] ? poll_select_copy_remaining+0x170/0x170
   [] ? wake_up_state+0x10/0x20
   [] ? drop_futex_key_refs.isra.14+0x1f/0x90
   [] ? futex_requeue+0x3de/0xba0
   [] ? do_futex+0xbe/0x8f0
   [] ? read_tsc+0x9/0x20
   [] ? ktime_get_ts+0x12d/0x170
   [] ? 

[Kernel-packages] [Bug 1557138] Re: Request to cherry-pick uvcvideo patch for Xenial kernel support of RealSense camera

[Joseph Salisbury]

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

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

Title:
  Request to cherry-pick uvcvideo patch for Xenial kernel support of
  RealSense camera

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The Raspberry-Pi form factor compatible UP board from Aaeon now
  supports RealSense depth enabled camera (http://www.up-
  board.org/kickstarter/up-intel-realsense-technology/) , and Intel has
  made a significant contribution to open source by supporting Robot
  Operating System code enabling use of that camera.  The current v4.4
  kernel has all patches merged to support RealSense camera, except v4.5
  change-id 120c41d3477a23c6941059401db63677736f1935 from
  https://github.com/torvalds/linux.git, which has a few minor editions
  to support required camera depth format.

  Can you please include this cherry-pick in the official Xenial kernel
  for 16.04 LTS?  This would enabled customers to avoid having to hand-
  patch uvcvideo.ko

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

-- 
Mailing list: https://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 1557138] Missing required logs.

[Brad Figg]

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

apport-collect 1557138

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

Title:
  Request to cherry-pick uvcvideo patch for Xenial kernel support of
  RealSense camera

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Raspberry-Pi form factor compatible UP board from Aaeon now
  supports RealSense depth enabled camera (http://www.up-
  board.org/kickstarter/up-intel-realsense-technology/) , and Intel has
  made a significant contribution to open source by supporting Robot
  Operating System code enabling use of that camera.  The current v4.4
  kernel has all patches merged to support RealSense camera, except v4.5
  change-id 120c41d3477a23c6941059401db63677736f1935 from
  https://github.com/torvalds/linux.git, which has a few minor editions
  to support required camera depth format.

  Can you please include this cherry-pick in the official Xenial kernel
  for 16.04 LTS?  This would enabled customers to avoid having to hand-
  patch uvcvideo.ko

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

-- 
Mailing list: https://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 1508331] Re: CVE-2015-7833

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

** Changed in: linux-lts-vivid (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1508331

Title:
  CVE-2015-7833

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  

[Kernel-packages] [Bug 1557001] Re: Xilinx KU3 Capi card does not show up in Ubuntu 16.04

[Steve Langasek]

** Package changed: Ubuntu Xenial => linux (Ubuntu Xenial)

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

Title:
  Xilinx KU3 Capi card does not show up in Ubuntu  16.04

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

Bug description:
  Canonical,

  There is a missing fix on top of the CAPI patches that was already
  accepted in Ubuntu 16.04 regarding Xilinx card.

  The patch will be send later today.

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

-- 
Mailing list: https://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 1534440] Re: CVE-2015-7566

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

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

** Changed in: linux-lts-vivid (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1534440

Title:
  CVE-2015-7566

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1557001] [NEW] Xilinx KU3 Capi card does not show up in Ubuntu 16.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Canonical,

There is a missing fix on top of the CAPI patches that was already
accepted in Ubuntu 16.04 regarding Xilinx card.

The patch will be send later today.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress


** Tags: architecture-ppc64 bot-comment bugnameltc-138881 severity-high 
targetmilestone-inin---
-- 
Xilinx KU3 Capi card does not show up in Ubuntu  16.04
https://bugs.launchpad.net/bugs/1557001
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://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 1556782] Re: USB3 not working

[cangaru]

This began when I migrated to a new server, the Intel I referred to, and
installed Ubuntu 15.04 on it. The standard kernel produced this error. I
tried many kernels. In the 4.4 and beyond series, including 4.5-wily, it
would not assemble or mount my raid array. So not much good there. But i
will test again. I am offsite at the moment so the apport does not
work...

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

Title:
  USB3 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am constantly getting these messages in dmesg:
  [114755.239681] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [114760.252354] usb 2-1: device descriptor read/8, error -110
  [114760.353433] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [114765.366486] usb 2-1: device descriptor read/8, error -110
  [114765.518703] sd 6:0:0:0: [sdf] FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [114765.518705] usb 2-1: USB disconnect, device number 2
  [114765.518707] sd 6:0:0:0: [sdf] CDB: 
  [114765.518708] Write(10): 2a 00 3a 36 db b7 00 00 10 00
  [114765.518712] blk_update_request: I/O error, dev sdf, sector 976673719
  [114765.518720] Aborting journal on device sdf1-8.
  [114765.524571] sd 6:0:0:0: [sdf] FAILED Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK

  I am trying to use a Toshiba external disk, in a usb3 port which I use for 
backup. It worked flawlessly on an old version of Redhat, but on moving to a 
new server, Intel S1200RP with updated firmware, I am in a world of pain. I 
have switched off standby for usb on boot, I have ensured that power is 
continually on for all usb ports. 
  I have tried a number of kernels, currently 3.19.0-031900rc4-lowlatency which 
had been less bad, but am still getting this fault.

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

-- 
Mailing list: https://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 1557129] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error Msg Displays After Each Restart

  Would Only Allow Me To Attach 1 File ("version.log"),

  Below Is lspci-vnvn.log:

  

  00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller 
[1028:04f5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Dell Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [1028:04f5]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in use: pcieport

[Kernel-packages] [Bug 1549601] Re: [Hyper-V] x86, pageattr: prevent overflow in slow_virt_to_phys() for X86_PAE

[Tim Gardner]

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

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

Title:
  [Hyper-V] x86,pageattr: prevent overflow in slow_virt_to_phys() for
  X86_PAE

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

Bug description:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1cd1210834649ce1ca6bafe5ac25d2f40331343

  x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE
  pte_pfn() returns a PFN of long (32 bits in 32-PAE), so "long <<
  PAGE_SHIFT" will overflow for PFNs above 4GB.

  Due to this issue, some Linux 32-PAE distros, running as guests on Hyper-V,
  with 5GB memory assigned, can't load the netvsc driver successfully and
  hence the synthetic network device can't work (we can use the kernel parameter
  mem=3000M to work around the issue).

  Cast pte_pfn() to phys_addr_t before shifting.

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

-- 
Mailing list: https://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 1537859] Re: Vivid update to 3.19.8-ckt13 stable release

[Tim Gardner]

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

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

Title:
  Vivid update to 3.19.8-ckt13 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Released

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 3.19.8-ckt13 upstream 
stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches from the 3.19.8-ckt13 stable release
  shall be applied:

  Linux 3.19.8-ckt13
  firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6
  kvm: x86: only channel 0 of the i8254 is linked to the HPET
  net: possible use after free in dst_release
  net: sched: fix missing free per cpu on qstats
  net: filter: make JITs zero A for SKF_AD_ALU_XOR_X
  ASoC: Use nested lock for snd_soc_dapm_mutex_lock
  ipv6/addrlabel: fix ip6addrlbl_get()
  include/linux/mmdebug.h: should include linux/bug.h
  net/mlx4_en: Fix HW timestamp init issue upon system startup
  net/mlx4_en: Remove dependency between timestamping capability and 
service_task
  net: fix warnings in 'make htmldocs' by moving macro definition out of field 
declaration
  ser_gigaset: fix deallocation of platform device structure
  qlcnic: fix a timeout loop
  amd-xgbe: fix a couple timeout loops
  mISDN: fix a loop count
  sh_eth: fix TX buffer byte-swapping
  net: phy: mdio-mux: Check return value of mdiobus_alloc()
  pinctrl: bcm2835: Fix initial value for direction_output
  sctp: start t5 timer only when peer rwnd is 0 and local state is 
SHUTDOWN_PENDING
  sctp: convert sack_needed and sack_generation to bits
  usb: musb: USB_TI_CPPI41_DMA requires dmaengine support
  vmstat: allocate vmstat_wq before it is used
  ftrace/module: Call clean up function when module init fails early
  dts: vt8500: Add SDHC node to DTS file for WM8650
  async_tx: use GFP_NOWAIT rather than GFP_IO
  ARM: versatile: fix MMC/SD interrupt assignment
  tile: provide CONFIG_PAGE_SIZE_64KB etc for tilepro
  tracing: Fix setting of start_index in find_next()
  ftrace/scripts: Fix incorrect use of sprintf in recordmcount
  mm/memory_hotplug.c: check for missing sections in test_pages_in_a_zone()
  ocfs2: fix BUG when calculate new backup super
  [PATCH] arm: fix handling of F_OFD_... in oabi_fcntl64()
  ASoC: arizona: Fix bclk for sample rates that are multiple of 4kHz
  MIPS: uaccess: Fix strlen_user with EVA
  ALSA: hda/realtek - Fix silent headphone output on MacPro 4,1 (v2)
  parisc: Fix syscall restarts
  i2c: rcar: disable runtime PM correctly in slave mode
  x86/mce: Ensure offline CPUs don't participate in rendezvous process
  USB: fix invalid memory access in hub_activate()
  USB: ipaq.c: fix a timeout loop
  [media] airspy: increase USB control message buffer size
  s390/dis: Fix handling of format specifiers
  ALSA: hda - Set SKL+ hda controller power at freeze() and thaw()
  powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type
  ARC: dw2 unwind: Ignore CIE version !=1 gracefully instead of bailing
  ARC: dw2 unwind: Reinstante unwinding out of modules
  ftrace/scripts: Have recordmcount copy the object file
  dma-debug: Fix dma_debug_entry offset calculation
  scripts: recordmcount: break hardlinks
  spi: fix parent-device reference leak
  ALSA: hda - Add a fixup for Thinkpad X1 Carbon 2nd
  ARM: 8471/1: need to save/restore arm register(r11) when it is corrupted
  ARM: dts: imx6: Fix Ethernet PHY mode on Ventana boards
  ALSA: usb-audio: Add a more accurate volume quirk for AudioQuest DragonFly
  genirq: Prevent chip buslock deadlock
  tty: Fix GPF in flush_to_ldisc()
  n_tty: Fix poll() after buffer-limited eof push read
  ASoC: wm8974: set cache type for regmap
  sh64: fix __NR_fgetxattr
  ocfs2: fix SGID not inherited issue
  drivers/base/memory.c: prohibit offlining of memory blocks with missing 
sections
  mm: hugetlb: call huge_pte_alloc() only if ptep is null
  mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't make any 
progress
  vmstat: Reduce time interval to stat update on idle cpu
  mm: hugetlb: fix hugepage memory leak caused by wrong reserve count
  parisc iommu: fix panic due to trying to allocate too large region
  powercap / RAPL: fix BIOS lock check
  USB: add quirk for devices with broken LPM
  xhci: fix usb2 resume timing and races.
  ses: fix additional element 

[Kernel-packages] [Bug 1557138] [NEW] Request to cherry-pick uvcvideo patch for Xenial kernel support of RealSense camera

[Matt Curfman]

Public bug reported:

The Raspberry-Pi form factor compatible UP board from Aaeon now supports
RealSense depth enabled camera (http://www.up-board.org/kickstarter/up-
intel-realsense-technology/) , and Intel has made a significant
contribution to open source by supporting Robot Operating System code
enabling use of that camera.  The current v4.4 kernel has all patches
merged to support RealSense camera, except v4.5 change-id
120c41d3477a23c6941059401db63677736f1935 from
https://github.com/torvalds/linux.git, which has a few minor editions to
support required camera depth format.

Can you please include this cherry-pick in the official Xenial kernel
for 16.04 LTS?  This would enabled customers to avoid having to hand-
patch uvcvideo.ko

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

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

Title:
  Request to cherry-pick uvcvideo patch for Xenial kernel support of
  RealSense camera

Status in linux package in Ubuntu:
  New

Bug description:
  The Raspberry-Pi form factor compatible UP board from Aaeon now
  supports RealSense depth enabled camera (http://www.up-
  board.org/kickstarter/up-intel-realsense-technology/) , and Intel has
  made a significant contribution to open source by supporting Robot
  Operating System code enabling use of that camera.  The current v4.4
  kernel has all patches merged to support RealSense camera, except v4.5
  change-id 120c41d3477a23c6941059401db63677736f1935 from
  https://github.com/torvalds/linux.git, which has a few minor editions
  to support required camera depth format.

  Can you please include this cherry-pick in the official Xenial kernel
  for 16.04 LTS?  This would enabled customers to avoid having to hand-
  patch uvcvideo.ko

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

-- 
Mailing list: https://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 1537886] Re: CVE-2013-4312

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-utopic (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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1537886

Title:
  CVE-2013-4312

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in 

Re: [Kernel-packages] [Bug 1556605] Re: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[eddiebeer]

Hello,

I executed all the steps on my laptop, an didn't receive any error's but
I'm not sure if this fixed it, that deleting and having the system recreate
my sources list fixed the problem. I have had some problems with that as
well. Something got corrupted during an update or something.

Is there anything else I should check to help you or is this the end of the
line for this issue?

Kind regards,

Erwin van Klinken.

On Mon, Mar 14, 2016 at 4:41 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> You may need to run the following from a terminal:
>
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
>
> Then re-install the package or updates.
>
> If that does not resolve your issue, please mark the bug as "Confirmed"
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1556605
>
> Title:
>   package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
>   install/upgrade: subprocess installed post-installation script
>   returned error exit status 2
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Error occured during update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.4.0-12-generic 4.4.0-12.28
>   ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
>   Uname: Linux 4.4.0-11-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   erwin  1556 F...m pulseaudio
>/dev/snd/controlC0:  gdm1339 F pulseaudio
> erwin  1556 F pulseaudio
>   Date: Sun Mar 13 12:46:16 2016
>   Df:
>
>   Dmesg:
>
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 2
>   HibernationDevice: RESUME=UUID=f5de7790-a1af-4ddc-bc56-e9ceed5b4372
>   InstallationDate: Installed on 2015-09-23 (171 days ago)
>   InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64
> (20150826.1)
>   Lsusb:
>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 003: ID 064e:d250 Suyin Corp.
>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
>   MachineType: Acer Aspire 5750
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic
> root=UUID=75c179e5-e8c3-46a4-8edc-8ad5c8137568 ro quiet splash vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions: grub-pc 2.02~beta2-36
>   SourcePackage: linux
>   Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 2
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/17/2011
>   dmi.bios.vendor: Acer
>   dmi.bios.version: V1.13
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: JE50_HR
>   dmi.board.vendor: Acer
>   dmi.board.version: Base Board Version
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.13
>   dmi.modalias:
> dmi:bvnAcer:bvrV1.13:bd08/17/2011:svnAcer:pnAspire5750:pvrV1.13:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.13:
>   dmi.product.name: Aspire 5750
>   dmi.product.version: V1.13
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556605/+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/1556605

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Error occured during update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   erwin  1556 F...m pulseaudio
   /dev/snd/controlC0:  gdm1339 F pulseaudio
erwin  1556 F pulseaudio
  Date: Sun Mar 13 12:46:16 2016
  Df:
   
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: 

[Kernel-packages] [Bug 1557130] [NEW] Current 4.4 kernel won't boot on powerpc

[Stéphane Graber]

Public bug reported:

19:06 < stgraber> apw: hey, so looks like powerpc (not 64el) isn't booting with 
current 4.4 from xenial
19:06 < stgraber> apw: smoser may have some more details for you, all I know is 
that I dist-upgraded my ppc VM and it stopped booting, smoser had to reboot me 
into 3.19 manually
19:08 < apw> stgraber, which versoin number is that ?
19:08 < stgraber> ii  linux-image-4.4.0-12-powerpc64-smp4.4.0-12.28 
powerpc  Linux kernel image for version 4.4.0 on 64-bit PowerPC 
SMP
19:08 < apw> stgraber, and do you have one which did boot before that, in 4.4 ?
19:08 < smoser> 3.19 booted
19:08 < apw> stgraber, i think we need a bug and i'll get jsalisbury to get 
this bisected
19:08 < apw> i just realised we don't run adt on power, sigh
19:08 < stgraber> apw: nope, I upgraded from trusty to xenial so it's the first 
4.4 I try
19:09 < smoser> qemu cmdline that results in "cant find root" looks like this
19:09 < smoser> qemu-system-ppc64 -name rockne-01 -echr 0x05 -enable-kvm -M 
pseries -cpu host -smp cores=2,threads=1 -m 8G -net 
nic,macaddr=52:54:00:00:42:01 -net tap,script=no,downscript=no,ifname=tap4201 
-device spapr-vscsi -drive 
file=/var/lib/libvirt/images/shared/rockne-01/disk1.img -drive 
file=/var/lib/libvirt/images/shared/rockne-01/eph0.img -drive 
file=/var/lib/libvirt/images/shared/rockne-01/save.img -nographic -vga none
19:09 < jsalisbury> apw, I'll watch for the bug to come in
19:09 < smoser> where disk1.img has the root filesystem on it.
19:09 < stgraber> apw: the issue is storage related, smoser got dropped into a 
shell with no block listed in /proc/partitions
19:09 < smoser> only ram disks.

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

** Affects: linux (Ubuntu Xenial)
 Importance: Critical
 Status: Triaged


** Tags: bot-stop-nagging kernel-key regression-release

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

Title:
  Current 4.4 kernel won't boot on powerpc

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

Bug description:
  19:06 < stgraber> apw: hey, so looks like powerpc (not 64el) isn't booting 
with current 4.4 from xenial
  19:06 < stgraber> apw: smoser may have some more details for you, all I know 
is that I dist-upgraded my ppc VM and it stopped booting, smoser had to reboot 
me into 3.19 manually
  19:08 < apw> stgraber, which versoin number is that ?
  19:08 < stgraber> ii  linux-image-4.4.0-12-powerpc64-smp4.4.0-12.28   
  powerpc  Linux kernel image for version 4.4.0 on 64-bit 
PowerPC SMP
  19:08 < apw> stgraber, and do you have one which did boot before that, in 4.4 
?
  19:08 < smoser> 3.19 booted
  19:08 < apw> stgraber, i think we need a bug and i'll get jsalisbury to get 
this bisected
  19:08 < apw> i just realised we don't run adt on power, sigh
  19:08 < stgraber> apw: nope, I upgraded from trusty to xenial so it's the 
first 4.4 I try
  19:09 < smoser> qemu cmdline that results in "cant find root" looks like this
  19:09 < smoser> qemu-system-ppc64 -name rockne-01 -echr 0x05 -enable-kvm -M 
pseries -cpu host -smp cores=2,threads=1 -m 8G -net 
nic,macaddr=52:54:00:00:42:01 -net tap,script=no,downscript=no,ifname=tap4201 
-device spapr-vscsi -drive 
file=/var/lib/libvirt/images/shared/rockne-01/disk1.img -drive 
file=/var/lib/libvirt/images/shared/rockne-01/eph0.img -drive 
file=/var/lib/libvirt/images/shared/rockne-01/save.img -nographic -vga none
  19:09 < jsalisbury> apw, I'll watch for the bug to come in
  19:09 < smoser> where disk1.img has the root filesystem on it.
  19:09 < stgraber> apw: the issue is storage related, smoser got dropped into 
a shell with no block listed in /proc/partitions
  19:09 < smoser> only ram disks.

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

-- 
Mailing list: https://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 1557130] Re: Current 4.4 kernel won't boot on powerpc

[Joseph Salisbury]

** Tags added: kernel-key

** Also affects: linux (Ubuntu Xenial)
   Importance: Critical
   Status: 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/1557130

Title:
  Current 4.4 kernel won't boot on powerpc

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

Bug description:
  19:06 < stgraber> apw: hey, so looks like powerpc (not 64el) isn't booting 
with current 4.4 from xenial
  19:06 < stgraber> apw: smoser may have some more details for you, all I know 
is that I dist-upgraded my ppc VM and it stopped booting, smoser had to reboot 
me into 3.19 manually
  19:08 < apw> stgraber, which versoin number is that ?
  19:08 < stgraber> ii  linux-image-4.4.0-12-powerpc64-smp4.4.0-12.28   
  powerpc  Linux kernel image for version 4.4.0 on 64-bit 
PowerPC SMP
  19:08 < apw> stgraber, and do you have one which did boot before that, in 4.4 
?
  19:08 < smoser> 3.19 booted
  19:08 < apw> stgraber, i think we need a bug and i'll get jsalisbury to get 
this bisected
  19:08 < apw> i just realised we don't run adt on power, sigh
  19:08 < stgraber> apw: nope, I upgraded from trusty to xenial so it's the 
first 4.4 I try
  19:09 < smoser> qemu cmdline that results in "cant find root" looks like this
  19:09 < smoser> qemu-system-ppc64 -name rockne-01 -echr 0x05 -enable-kvm -M 
pseries -cpu host -smp cores=2,threads=1 -m 8G -net 
nic,macaddr=52:54:00:00:42:01 -net tap,script=no,downscript=no,ifname=tap4201 
-device spapr-vscsi -drive 
file=/var/lib/libvirt/images/shared/rockne-01/disk1.img -drive 
file=/var/lib/libvirt/images/shared/rockne-01/eph0.img -drive 
file=/var/lib/libvirt/images/shared/rockne-01/save.img -nographic -vga none
  19:09 < jsalisbury> apw, I'll watch for the bug to come in
  19:09 < smoser> where disk1.img has the root filesystem on it.
  19:09 < stgraber> apw: the issue is storage related, smoser got dropped into 
a shell with no block listed in /proc/partitions
  19:09 < smoser> only ram disks.

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

-- 
Mailing list: https://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 1557129] [NEW] package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Brad Aytes]

Public bug reported:

Error Msg Displays After Each Restart

Would Only Allow Me To Attach 1 File ("version.log"),

Below Is lspci-vnvn.log:



00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller 
[1028:04f5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Dell Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [1028:04f5]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 
00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell 2nd Generation Core Processor Family Integrated 
Graphics Controller [1028:04f5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 

[Kernel-packages] [Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

[Christoph Buchner]

thank you, installing now. :-)

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

Bug description:
  Hi,

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

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

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

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

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

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

[Kernel-packages] [Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

[Joseph Salisbury]

@Christoph Buchner, correct.   You should upgrade to the latest Ubuntu
4.2 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/1548867

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

Bug description:
  Hi,

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

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

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

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

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

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

[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic

[ais523]

The most recent BIOS offered via the page you linked was F.66. I updated
my BIOS to that version:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F.66
07/01/2014

After updating, I connected and disconnected the Osprey 2 Mini four
times, with no crashes. Then I rebooted, connected it and got a reset
loop, and disconnected it and got a system hang (Caps Lock was not
flashing but the system did not respond to any input, not even Alt-
SysRq-B, and I had to hold down the power button to shut it off).

As such, I believe the BIOS update did nothing to prevent the bug
occurring, and that the bug is still present.

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

Title:
  Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
  causes an endless reset loop or a kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce (happens > 50% of the time, but not every time):

  Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable
  while both the device and computer are on (i.e. hotplug).

  Observed symptoms:
  - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the 
LEDs on the front of the device flashing rapidly), being reset approximately 
every 200ms; on such occasions, the Ubuntu user interface often reacts as 
though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly 
adding an "Audio CD" icon to the launcher and then removing it, and putting up 
dialog boxes complaining about failure to read the data).
  - sometimes the kernel panics (often some time after the reset loop starts, 
perhaps up to 10 seconds); when this happens there was always or nearly always 
a reset loop occurring beforehand.
  - sometimes the device resets once or not at all, then works as expected 
(showing up as a network interface, and allowing me to communicate to the 
Internet with a wired connection); I'm currently using an Osprey 2 Mini for 
this purpose right now.

  The kernel panics lock up the entire system (forcing a hard power
  off). lt-Sysrq commands don't work in this state (even though I have
  them enabled), and sometimes the Caps Lock light flashes repeatedly.
  The logs end some time before the panic occurs.

  /var/log/syslog:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog

  The reset loops also occurred when I was using Ubuntu vivid. The
  kernel panics only happened after an upgrade to wily. Output of lsusb
  -v is attached.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 6233 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007
  InstallationDate: Installed on 2014-06-03 (648 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-32-generic x86_64
  UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2186
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1529971] bantam (amd64) - tests ran: 11, failed: 3

[Brad Figg]

tests ran:  11, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-13.29/s2lp6g101__4.4.0-13.29__2016-03-14_10-42-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-43.49~14.04.1 -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:
  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 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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-43.49~14.04.1 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-Prepare-package-start:Tuesday, 29. December 2015 22:50 UTC
  kernel-stable-master-bug:1529362
  kernel-stable-Prepare-package-end:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Certification-testing-end:Monday, 04. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 04. January 2016 18:08 UTC
  kernel-stable-Security-signoff-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Regression-testing-start:Monday, 04. January 2016 18:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Verification-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Regression-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 05. January 2016 09:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 05. January 2016 10:01 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 05. January 2016 16:10 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 05. January 2016 18:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1529971/+subscriptions

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