[Kernel-packages] [Bug 1576034] 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/1576034

Title:
  package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During update this was reported

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-74-generic 3.13.0-74.118
  ProcVersionSignature: Ubuntu 3.13.0-80.124-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-80-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  barry  2367 F pulseaudio
   /dev/snd/seq:timidity   1670 F timidity
  Date: Wed Apr 27 13:23:21 2016
  DuplicateSignature: 
package:linux-headers-3.13.0-74-generic:3.13.0-74.118:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=0bb2e22b-90f8-41af-a875-da53ff3b3e14
  InstallationDate: Installed on 2013-06-04 (1058 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: TOSHIBA Satellite Pro L40
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-80-generic 
root=UUID=9cc5835c-5d86-4401-ba77-94a20c9c7192 ro splash quiet
  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-9ubuntu1.8
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Title: package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (732 days ago)
  dmi.bios.date: 09/19/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.60
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Satellite Pro L40
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.60:bd09/19/2007:svnTOSHIBA:pnSatelliteProL40:pvrPSL4BE-00N006DU:rvnTOSHIBA:rnSatelliteProL40:rvr1.0:cvnTOSHIBA:ct10:cvr:
  dmi.product.name: Satellite Pro L40
  dmi.product.version: PSL4BE-00N006DU
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1576034] [NEW] package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

[Barry Mildner]

Public bug reported:

During update this was reported

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-headers-3.13.0-74-generic 3.13.0-74.118
ProcVersionSignature: Ubuntu 3.13.0-80.124-generic 3.13.11-ckt35
Uname: Linux 3.13.0-80-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  barry  2367 F pulseaudio
 /dev/snd/seq:timidity   1670 F timidity
Date: Wed Apr 27 13:23:21 2016
DuplicateSignature: 
package:linux-headers-3.13.0-74-generic:3.13.0-74.118:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
HibernationDevice: RESUME=UUID=0bb2e22b-90f8-41af-a875-da53ff3b3e14
InstallationDate: Installed on 2013-06-04 (1058 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: TOSHIBA Satellite Pro L40
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-80-generic 
root=UUID=9cc5835c-5d86-4401-ba77-94a20c9c7192 ro splash quiet
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-9ubuntu1.8
RfKill:
 1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
Title: package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to trusty on 2014-04-26 (732 days ago)
dmi.bios.date: 09/19/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.60
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Satellite Pro L40
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.60:bd09/19/2007:svnTOSHIBA:pnSatelliteProL40:pvrPSL4BE-00N006DU:rvnTOSHIBA:rnSatelliteProL40:rvr1.0:cvnTOSHIBA:ct10:cvr:
dmi.product.name: Satellite Pro L40
dmi.product.version: PSL4BE-00N006DU
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-package i386 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/1576034

Title:
  package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  During update this was reported

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-74-generic 3.13.0-74.118
  ProcVersionSignature: Ubuntu 3.13.0-80.124-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-80-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  barry  2367 F pulseaudio
   /dev/snd/seq:timidity   1670 F timidity
  Date: Wed Apr 27 13:23:21 2016
  DuplicateSignature: 
package:linux-headers-3.13.0-74-generic:3.13.0-74.118:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=0bb2e22b-90f8-41af-a875-da53ff3b3e14
  InstallationDate: Installed on 2013-06-04 (1058 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: TOSHIBA Satellite Pro L40
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-80-generic 
root=UUID=9cc5835c-5d86-4401-ba77-94a20c9c7192 ro splash quiet
  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-9ubuntu1.8
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Title: package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (732 days ago)
  dmi.bios.date: 09/19/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.60
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Satellite Pro L40
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.modalias: 

[Kernel-packages] [Bug 1576034] Re: package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  During update this was reported

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-74-generic 3.13.0-74.118
  ProcVersionSignature: Ubuntu 3.13.0-80.124-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-80-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  barry  2367 F pulseaudio
   /dev/snd/seq:timidity   1670 F timidity
  Date: Wed Apr 27 13:23:21 2016
  DuplicateSignature: 
package:linux-headers-3.13.0-74-generic:3.13.0-74.118:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=0bb2e22b-90f8-41af-a875-da53ff3b3e14
  InstallationDate: Installed on 2013-06-04 (1058 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: TOSHIBA Satellite Pro L40
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-80-generic 
root=UUID=9cc5835c-5d86-4401-ba77-94a20c9c7192 ro splash quiet
  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-9ubuntu1.8
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Title: package linux-headers-3.13.0-74-generic 3.13.0-74.118 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (732 days ago)
  dmi.bios.date: 09/19/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.60
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Satellite Pro L40
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.60:bd09/19/2007:svnTOSHIBA:pnSatelliteProL40:pvrPSL4BE-00N006DU:rvnTOSHIBA:rnSatelliteProL40:rvr1.0:cvnTOSHIBA:ct10:cvr:
  dmi.product.name: Satellite Pro L40
  dmi.product.version: PSL4BE-00N006DU
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1576025] 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 1576025

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

Title:
  Different kernal images seen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I got i686 when I used the following command

  madhu@madhu-desktop:~$ uname -mrsn
  Linux madhu-desktop 4.4.0-21-generic i686

  madhu@madhu-desktop:~$ dpkg --list | grep linux-image
  ii  linux-image-4.4.0-21-generic 4.4.0-21.37  
   i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
  ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37  
   i386 Linux kernel extra modules for version 
4.4.0 on 32 bit x86 SMP
  ii  linux-image-generic  4.4.0.21.22  
   i386 Generic Linux kernel image
  madhu@madhu-desktop:~$

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

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

[Kernel-packages] [Bug 1576025] Re: Different kernal images seen

[MadhuSoodanan]

Screenshot

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576025/+attachment/4649720/+files/Screenshot%20from%202016-04-28%2010-00-21.jpg

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

Title:
  Different kernal images seen

Status in linux package in Ubuntu:
  New

Bug description:
  I got i686 when I used the following command

  madhu@madhu-desktop:~$ uname -mrsn
  Linux madhu-desktop 4.4.0-21-generic i686

  madhu@madhu-desktop:~$ dpkg --list | grep linux-image
  ii  linux-image-4.4.0-21-generic 4.4.0-21.37  
   i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
  ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37  
   i386 Linux kernel extra modules for version 
4.4.0 on 32 bit x86 SMP
  ii  linux-image-generic  4.4.0.21.22  
   i386 Generic Linux kernel image
  madhu@madhu-desktop:~$

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

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

[Kernel-packages] [Bug 1576025] 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 1576025

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

Title:
  Different kernal images seen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I got i686 when I used the following command

  madhu@madhu-desktop:~$ uname -mrsn
  Linux madhu-desktop 4.4.0-21-generic i686

  madhu@madhu-desktop:~$ dpkg --list | grep linux-image
  ii  linux-image-4.4.0-21-generic 4.4.0-21.37  
   i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
  ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37  
   i386 Linux kernel extra modules for version 
4.4.0 on 32 bit x86 SMP
  ii  linux-image-generic  4.4.0.21.22  
   i386 Generic Linux kernel image
  madhu@madhu-desktop:~$

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

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

[Kernel-packages] [Bug 1576025] [NEW] Different kernal images seen

[MadhuSoodanan]

Public bug reported:

I got i686 when I used the following command

madhu@madhu-desktop:~$ uname -mrsn
Linux madhu-desktop 4.4.0-21-generic i686

madhu@madhu-desktop:~$ dpkg --list | grep linux-image
ii  linux-image-4.4.0-21-generic 4.4.0-21.37
 i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37
 i386 Linux kernel extra modules for version 4.4.0 
on 32 bit x86 SMP
ii  linux-image-generic  4.4.0.21.22
 i386 Generic Linux kernel image
madhu@madhu-desktop:~$

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

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

Title:
  Different kernal images seen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I got i686 when I used the following command

  madhu@madhu-desktop:~$ uname -mrsn
  Linux madhu-desktop 4.4.0-21-generic i686

  madhu@madhu-desktop:~$ dpkg --list | grep linux-image
  ii  linux-image-4.4.0-21-generic 4.4.0-21.37  
   i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
  ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37  
   i386 Linux kernel extra modules for version 
4.4.0 on 32 bit x86 SMP
  ii  linux-image-generic  4.4.0.21.22  
   i386 Generic Linux kernel image
  madhu@madhu-desktop:~$

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

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

[Kernel-packages] [Bug 1519461] Re: Black screen, when nvidia enabled after wakeup from suspend

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

Title:
  Black screen, when nvidia enabled after wakeup from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  When NVidia 820m is enabled in UEFI, after wake up from suspend mode i have 
hang on black screen (ctrl + alt + Fx is not working).
  Also i report about this bug to Nvidia (on official blob drivers problem is 
here), and they have reproduced this problem and will submit info to 
engineering nvidia.
  I try add this parameter ADD_PARAMETERS="--quirk-dpms-on" to 
/etc/pm/config.d/config, and after wake up from suspend mode i see lockscreen 
(ubuntu greeter), but mouse, keyboard not working again. Again hang system, but 
with image on display!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 24 22:39:29 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0866]
 Subsystem: Acer Incorporated [ALI] GeForce 820M [1025:0868]
  InstallationDate: Installed on 2015-11-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Extensa 2510G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=f6094b80-a9d8-4e96-8077-66b0e59e75b0 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Extensa 2510G
  dmi.product.version: V1.27
  dmi.sys.vendor: Acer
  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.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  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: Tue Nov 24 22:32:11 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5566 
   vendor CMN
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[PocketSam]

Also a funny glitches happen with Google Documents very often.

** Attachment added: "Снимок экрана от 2016-04-28 08-21-35.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+attachment/4649672/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-04-28%2008-21-35.png

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-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.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: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1574044] Re: ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)

[Matt Corallo]

Similar errors went away for me after updating to the latest BIOS.

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

Title:
  ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup failure,
  AE_NOT_FOUND (20150930/psargs-359)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After unplugging the external display (connected over USB Type-C), I
  see following in dmesg:

  [53204.035444] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup 
failure, AE_NOT_FOUND (20150930/psargs-359)
  [53204.035449] ACPI Error: Method parse/execution failed [\PNOT] (Node 
8804700d64b0), AE_NOT_FOUND (20150930/psparse-542)
  [53204.035454] ACPI Error: Method parse/execution failed [\_SB.AC._PSR] (Node 
8804700e92a8), AE_NOT_FOUND (20150930/psparse-542)
  [53204.035481] ACPI Exception: AE_NOT_FOUND, Error reading AC Adapter state 
(20150930/ac-128)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   cromo  2489 F...m pulseaudio
   /dev/snd/pcmC0D0p:   cromo  2489 F...m pulseaudio
   /dev/snd/controlC0:  cromo  2489 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:13:12 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1095 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0c45:670c Microdia 
   Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (31 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Joseph Salisbury]

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

** Tags added: kernel-da-key

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0xefff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at 
[880fbba0]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] No NUMA configuration found
  [0.00] Faking a node at [mem 0x-0x0001efff]
  [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff]
  [0.00] Zone ranges:
  [0.00]   DMA  [mem 0x1000-0x00ff]
  [0.00]   DMA32[mem 0x0100-0x]
  [0.00]   Normal   [mem 0x0001-0x0001efff]
  [0.00]   Device   empty
  [0.00] Movable zone start for each node
  [0.00] Early memory node ranges
  [0.00]   node   0: [mem 0x1000-0x0009dfff]
  [0.00]   node   0: [mem 0x0010-0xefff]
  [0.00]   node   0: [mem 0x0001-0x0001efff]
  [0.00] Initmem setup node 0 [mem 

[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

[Adric Norris]

Just tried the 4.6-rc5-wily kernel image, which unfortunately still
exhibits this problem. I'll keep trying updated kernels periodically,
especially when ones tagged for xenial begin appearing.

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discrenable reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behaviour

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  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-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  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/1575437/+subscriptions

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

[Kernel-packages] [Bug 1571020] Re: CVE-2016-3961

[Steve Beattie]

** Description changed:

  Xen and the Linux kernel through 4.5.x do not properly suppress
  hugetlbfs support in x86 PV guests, which allows local PV guest users to
  cause a denial of service (guest OS crash) by attempting to access a
  hugetlbfs mapped area.
+ 
+ Break-Fix: - 103f6112f253017d7062cd74d17f4a514ed4485c

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

Title:
  CVE-2016-3961

Status in linux package in Ubuntu:
  New
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-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:
  New
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 package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  

[Kernel-packages] [Bug 1528904] Re: CVE-2015-8660

[Steve Beattie]

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

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

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

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

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

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

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

Title:
  CVE-2015-8660

Status in linux package in Ubuntu:
  Fix Released
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:
  Invalid
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:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
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:
  Invalid
Status in linux source package in Trusty:
  Invalid
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:
  Invalid
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:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
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:
  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 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:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
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 

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joakim Plate]

Some interesting additional observations. I'm running kernel 4.2.0-35 on
15.10 ubuntu. Last night it hung with readonly system ala- this report.
What was interesting was that the machine that hung was NOT included in
the backups run on the host system. The host hypervisor does run backups
on other virtual hosts, as well as some subdirectories on the same
physical disk where the virtual machines vhdx file reside, but not on
the now hung virtual machine.

Even thou it's not included in the backup, it will still FREEZE and THAW
using the VSS service on the virtual machine. Thus it's not even safe to
exclude the machines from backup.

I was able to recover the machine after a reboot after a automatic fsk
correction.

-- 
You 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
Status in linux source package in Xenial:
  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 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs

[Andrew]

** Description changed:

- Not sure what package this is related to. My best guess is Unity, but i
- honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04
- on my Dell Inspiron laptop consistently freezes up and is unresponsive
- keyboard or mouse. The only way is to do a hard shutdown. I'm usually in
- a browser when this happens, and often watching a video or two. So i
- wonder if this has something to do with my memory buffer or something.
- It seems to happen more often in Google Chrome than Firefox, but it
- happens with both. I know Google Chrome uses more memory though. And it
- has happened at least once with no videos loaded, so i doubt it's some
- sort of weird flash issue. I haven’t observed it freeze / hang when I’m
- not in a browser, but that's mainly what i use my laptop for, so that's
- where most of my time is spent.
+ Not sure what package this is related to. I honestly have no idea. After
+ upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop
+ consistently freezes up and is unresponsive keyboard or mouse. The only
+ way is to do a hard shutdown. I'm usually in a browser when this
+ happens, and often watching a video or two. So i wonder if this has
+ something to do with my memory buffer or something. It seems to happen
+ more often in Google Chrome than Firefox, but it happens with both. I
+ know Google Chrome uses more memory though. And it has happened at least
+ once with no videos loaded, so i doubt it's some sort of weird flash
+ issue. I haven’t observed it freeze / hang when I’m not in a browser,
+ but that's mainly what i use my laptop for, so that's where most of my
+ time is spent.
  
  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while trying
  to reproduce it to see if i can see an error that way.
- 
  
  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)
  
  andrew@andrew-Inspiron-3451:~$ sudo lshw
- andrew-inspiron-3451  
- description: Computer
- width: 64 bits
- capabilities: smbios-2.8 vsyscall32
-   *-core
-description: Motherboard
-physical id: 0
-  *-memory
-   description: System memory
-   physical id: 0
-   size: 3834MiB
-  *-cpu
-   product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
-   vendor: Intel Corp.
-   physical id: 1
-   bus info: cpu@0
-   size: 909MHz
-   capacity: 2665MHz
-   width: 64 bits
-   capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
-  *-pci
-   description: Host bridge
-   product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
-   vendor: Intel Corporation
-   physical id: 100
-   bus info: pci@:00:00.0
-   version: 0e
-   width: 32 bits
-   clock: 33MHz
-   configuration: driver=iosf_mbi_pci
-   resources: irq:0
- *-display
-  description: VGA compatible controller
-  product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
-  vendor: Intel Corporation
-  physical id: 2
-  bus info: pci@:00:02.0
-  version: 0e
-  width: 32 bits
-  clock: 33MHz
-  

[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs

[Andrew]

Both of these bugs sound like the same problem i'm having, but these two
bugs are expired now, but the thing we all have in common is Intel
Pentium processor N3540 and often (but not always) freezes because we
play videos in Chrome browser. So, is this a kernel problem or a video
driver problem or what? I didn't have problems in 14.04, but i do in
16.04.

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

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516108

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

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive keyboard or mouse.
  The only way is to do a hard shutdown. I'm usually in a browser when
  this happens, and often watching a video or two. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. I haven’t observed it freeze / hang when
  I’m not in a browser, but that's mainly what i use my laptop for, so
  that's where most of my time is spent.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci
    resources: irq:0
  *-display
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
     

[Kernel-packages] [Bug 1530623] Re: Ubuntu 15.10 full freeze (maybe intel hd graphics kernel failure)

[Andrew]

This sounds like the same problem i'm having.

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

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

Title:
  Ubuntu 15.10 full freeze (maybe intel hd graphics kernel failure)

Status in linux package in Ubuntu:
  Expired

Bug description:
  My new Acer ES1-411 won't work under Ubuntu. It has a Intel N3540 CPU
  and a integrated Intel HD Graphics GPU. It has a UEFI and I ran
  dualboot Windows 10 and Ubuntu 15.10. UEFI firmware is latest. While
  just working and surfing it runs, but when I look at videos (mp4) it
  takes sometimes only seconds sometimes minutes until the machine full
  freezes, no keyboard and no ssh access to it. So also no logfiles from
  the crashes exist. I still tried to change the GPU frequency with
  intel_gpu_frequency from the lowest to highest value, already switched
  off bluetooth, but no change. I also still tried the latest evaluation
  version of Ubuntu with the 4.3 kernel and the 01.org intel drivers but
  also no change. I tried 4.4.rc7 and it seemd to be better but with
  this kernel touchpad won't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-headers-4.2.0-22 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:  florian1520 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan  3 08:25:32 2016
  HibernationDevice: RESUME=UUID=8131090f-e072-49ad-83e8-2d12bc6eaaef
  InstallationDate: Installed on 2016-01-02 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority', 'warning'] failed with 
exit code 1: Hint: You are currently not seeing messages from other users and 
the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b3 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-411
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic.efi.signed 
root=UUID=314f6b7d-62c3-4eab-ab1e-32dfaaacb32c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  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] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA42_BM
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd12/10/2014:svnAcer:pnAspireES1-411:pvrV1.08:rvnAcer:rnEA42_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire ES1-411
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[Braiam Peguero]

macias, since you were able to find that the issue was fixed upstream,
could you follow the procedure that Joseph explained? Specifically:

> If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

and

> Once testing of the upstream kernel is complete, please mark this bug
as "Confirmed".

This will allow the team to pinpoint what went wrong, and offer a
solution for everyone else.

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1571020] Re: CVE-2016-3961

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-3961

Status in linux package in Ubuntu:
  New
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-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 

[Kernel-packages] [Bug 1572666] Re: CVE-2016-3955

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3955

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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:
  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-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
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:
  New
Status in linux-lts-wily source package in Trusty:
  New
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

[Kernel-packages] [Bug 1574125] Re: suspend not working after upgrade

[dlh]

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

>i have to remove battery to again start the system

Probably holding power button would to the job as well.

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

Title:
  suspend not working after upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joseph Salisbury]

Thanks for the update.  The test of the kernel on my system is still
running, so it's great you could reproduce the bug faster.

I built the next kernel up to commit:
83215219

It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1470250/second-bisect/83215219/

I'll see if there is a way to build predicted kernels to 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/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
Status in linux source package in Xenial:
  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 1574125] Re: suspend not working after upgrade

[saicharan]

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

same issue here with hp notebook
i have to remove battery to again start the system

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

Title:
  suspend not working after upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Jeff Lane]

The current firmware on this box is A28 02/06/2014 (not sure exactly
what that corresponds to just yet, the HP website is less than
forthcoming on firmware updates so far).

You'd mentioned getting one of our firmware devs to take a look would
you prefer I hold off on updating this system until then, or would it be
better to find a more recent firmware and test to see if that resolves
the issues we're seeing?

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(_start, NULL);
  sleep(sleeptime);
  gettimeofday(_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1566221] Re: linux: Enforce signed module loading when UEFI secure boot

[Tim Gardner]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
   Status: Fix Released

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

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

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

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

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

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

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

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

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

Title:
  linux: Enforce signed module loading when UEFI secure boot

Status in linux package in Ubuntu:
  Fix Released
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
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Add code to implement secure boot checks. Unsigned or incorrectly
  signed modules will continue to install while tainting the kernel
  _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled.

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

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

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Colin Ian King]

OK, so the local APIC timer is not working as I expected. Perhaps it's
not wired up to produce the timer interrupt as we expect.

I've disabled the Local APIC timer and lo and behold it works fine:

./clocktest 
Testing for clock jitter on 8 cpus
PASSED: largest jitter seen was 0.001365

Testing clock direction for 5 minutes...
PASSED: Iteration 0 delta: 0.000447
PASSED: Iteration 1 delta: 0.001461
PASSED: Iteration 2 delta: 0.001509
PASSED: Iteration 3 delta: 0.001465
PASSED: Iteration 4 delta: 0.001416
clock direction test: sleeptime 60 sec per iteration, failed iterations: 0

So much hunch is that there is something wrong in the firmware not
setting up the APIC IRQ routing and hence we're not getting wakeups from
the APICS causing the poor scheduling wakeup responses when the CPUs go
into an idle state.  As it stands, I believe there is something not
correct with the way the timer interrupts being configured, which is
certainly BIOS related.   I think we need an AMD APIC expert and/or
somebody with the IRQ firmware routing know-how to verify this
assertion.

BTW,  the kernel is reporting that 4 of the ACPI _PRS objects are not
correctly configured:

<4>[3.114961] ACPI: Invalid _PRS IRQ 0
<6>[3.115192] ACPI: PCI Interrupt Link [U1PI] (IRQs) *0
<4>[3.115613] ACPI: Invalid _PRS IRQ 0
<6>[3.115846] ACPI: PCI Interrupt Link [U2PI] (IRQs) *0
<4>[3.116244] ACPI: Invalid _PRS IRQ 0
<6>[3.116484] ACPI: PCI Interrupt Link [U3PI] (IRQs) *0
<4>[3.116891] ACPI: Invalid _PRS IRQ 0
<6>[3.117147] ACPI: PCI Interrupt Link [U4PI] (IRQs) *0
<6>[3.117439] ACPI: PCI Interrupt Link [SATA] (IRQs *16)
<4>[3.117745] ACPI: Invalid _PRS IRQ 0

so this looks iffy too.

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(_start, NULL);
  sleep(sleeptime);
  gettimeofday(_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 

[Kernel-packages] [Bug 1567191] Re: CVE-2016-3951

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3951

Status in linux package in Ubuntu:
  Fix Committed
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:
  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-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:
  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-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
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:
  New
Status in linux-lts-wily source package in Trusty:
  New
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 

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Colin Ian King]

Just to clarify, the kernel parameter I used to work around the
underlying issue is: nolapic_timer

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(_start, NULL);
  sleep(sleeptime);
  gettimeofday(_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 

[Kernel-packages] [Bug 1554613]

[Nhellwege]

(In reply to jay from comment #50)
> On my end, the issue looks like a random "blanking" of the screen for 1/4 of
> a second, two or three times or so in a row. It can happen several times in
> a few minutes, but I've also seen it last 20 minutes between occurrences. On
> my end it looks nothing like in that video.

Yes, that is the same with me. I dont know if the underlying issues are
identical, but the blanking of the screen is totally different from the
graphical flickering in #91393.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Rodrigo-vivi]

Probably a bisect on drm-intel-nightly is less painful.
But it seems that we are indeed now duplicating the discussion and there is 
more information on the other bug. Please reopen if you believe this one here 
is a different case.

*** This bug has been marked as a duplicate of bug 91393 ***

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1556888] Re: CVE-2016-3140

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3140

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
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 

[Kernel-packages] [Bug 1520519] Re: ASUS ROG GL552 TouchPad not detected

[Maurizio M.]

A quick update. By switching to kernel 4.5rc4 I get the touchpad
recognized as:

I: Bus=0018 Vendor=04f3 Product=0005 Version=
N: Name="Elan Touchpad"
P: Phys=
S: 
Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-7/i2c-ELAN1000:00/input/input12
U: Uniq=
H: Handlers=mouse1 event12 
B: PROP=5
B: EV=b
B: KEY=e520 1 0 0 0 0
B: ABS=66380001303

But with such a kernel there are video artifacts (with both native and 
proprietary drivers.
I have no idea about how adding the above driver to an old kernel that does not 
exhibit the artifacts bug.

Maurizio

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

Title:
  ASUS ROG GL552 TouchPad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop Model  : ASUS ROG GL552 DH71
  First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04. 
Touchpad never detected.
  Manufacturer : ASUS ( as listed under windows 10 )

  * xinput list *

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=10   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=8[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=9[slave  
keyboard (3)]

  * List of devices *
  : Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c05a Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:00:14.0-1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04f2 Product=b424 Version=6969
  N: Name="USB2.0 HD UVC WebCam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH 

[Kernel-packages] [Bug 1554613] Re: screen flickering on XPS13 9350

[Bug Watch Updater]

** Changed in: linux
   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/1554613

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1561388] Re: CVE-2016-3157

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3157

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 

[Kernel-packages] [Bug 1558847] Re: CVE-2016-3156

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3156

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 

[Kernel-packages] [Bug 1568523] Re: CVE-2016-3672

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3672

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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:
  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-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
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:
  New
Status in linux-lts-wily source package in Trusty:
  New
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:
 

[Kernel-packages] [Bug 1566581] Re: CVE-2016-3689

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3689

Status in linux package in Ubuntu:
  Fix Committed
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:
  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-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 Committed
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 Committed
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:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
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

[Kernel-packages] [Bug 1554613]

[Nhellwege]

Created attachment 123104
bisect log for underrun FIFO Error

Bisect log for the i915 Underrun FIFO ERROR. Since no clear method is
known on how to excite the error, the bisect might be unfinished. All
bad commits did show the FIFO error AND also the Flicker. All good ones
did not within a reasonable time (I testet each good Kernal at least 30
minutes). There are some (many) skippes commits, which I was not able to
build. The Faulty commit must be somewhere in these skipped commits.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Jani-nikula]

(In reply to Pranith Kumar from comment #55)
> Is this really resolved? The problem is gone, but I don't think anyone
> identified what is really causing the problem to occur.

In a perfect world we'd get to the roots of every problem, but in
reality we don't have the time to keep debugging issues that seem to be
gone. Especially in areas where we've done a lot of fixing upstream.

> Also, we need to
> identify which patch fixed the issue so that it can be back-ported. Both 4.5
> and 4.6 kernels have this problem.

If the v4.6-rc kernels still have the issue, but drm-intel-nightly
works, it should be a pretty straightforward reverse bisect to find the
commit that fixed the bug. If you provide that, it may be possible to do
the backport.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Nhellwege]

(In reply to tranceash from comment #38)
> looks like a power management issues dating 8 months back, Also happened on
> the broadwell systems https://bugs.freedesktop.org/show_bug.cgi?id=91393.
> This makes any linux system a pain to work because of this integrated gpu
> driver . Skylake has been out for 7 months and we still have problems

Ok, I looked into that bug and it seems its not the same. It
specifically mentions external monitors and also not black screen
flickering, but more a graphical flickering, without the completely
black frames in between.

Nevertheless, I tried the proposes patches from
https://bugs.freedesktop.org/show_bug.cgi?id=91393#c102 on intel-drm-
nightly and I still got the FIFO underrun ERROR and also the black
screen flickering. So thats not a solution.

Also, it seems that the FIFO error does appear for the first flicker,
but not for any ones after the first, so in my opinion, it can be used
as an error criteria.

I could bisect the kernel further, but as seen in
https://bugs.freedesktop.org/attachment.cgi?id=123104 there are so many
commits, which I cannot build. Maybe someone can help me to compile one
of these? I can then do the remaining (since they are all in order, it
seems like the reason they dont compile might be the same).

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1556883] Re: CVE-2016-3139

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

Title:
  CVE-2016-3139

Status in linux package in Ubuntu:
  New
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-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

[Kernel-packages] [Bug 1556880] Re: CVE-2016-3138

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3138

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 

[Kernel-packages] [Bug 1554613]

[Jani-nikula]

Thanks, closing. Please reopen or file new bugs if the problems persist.
(Please be careful about not reopening this one if you have bug 91393)

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[pranith]

Is this really resolved? The problem is gone, but I don't think anyone
identified what is really causing the problem to occur. Also, we need to
identify which patch fixed the issue so that it can be back-ported. Both
4.5 and 4.6 kernels have this problem.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Nhellwege]

I could try to bisect https://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-crack ,which is the base for the
4.6.0-997-generic intel-drm-next. A quick search suggests a list of 4-5
possible commits.

Should this be done? Bisecting is very tedious.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Thomas Bonfort]

As another user confirms on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613 , the
flickering has disappeared on the latest drm-intel-next

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Peteryuchuang]

(In reply to nhellwege from comment #51)
> (In reply to thomas bonfort from comment #49)
> > As another user confirms on
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613 , the
> > flickering has disappeared on the latest drm-intel-next
> 
> I can confirm that the blank screen flickering is gone with
> 4.6.0-997-generic intel-drm-next. 
> 
> Just a follow up question: I am not that familiar with Kernel releases, but
> as I understand, the 4.4. has long term support, whereas the 4.6. doesnt.
> Will the driver from the 4.6. eventually be backported to 4.4.?
> 
> Thanks for all the effort which has gone into this bug.

I can confirm that the flickering is gone with the latest drm-intel-next
kernel too.

Thanks everyone.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[O-jay]

On my end, the issue looks like a random "blanking" of the screen for
1/4 of a second, two or three times or so in a row. It can happen
several times in a few minutes, but I've also seen it last 20 minutes
between occurrences. On my end it looks nothing like in that video.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Thomas Bonfort]

If the underlying issue is the same then fine. I can confirm that the
resulting appearance of this current bug is very different than what the
video shows in 91393

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1554613]

[Nhellwege]

(In reply to thomas bonfort from comment #49)
> As another user confirms on
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613 , the
> flickering has disappeared on the latest drm-intel-next

I can confirm that the blank screen flickering is gone with
4.6.0-997-generic intel-drm-next.

Just a follow up question: I am not that familiar with Kernel releases,
but as I understand, the 4.4. has long term support, whereas the 4.6.
doesnt. Will the driver from the 4.6. eventually be backported to 4.4.?

Thanks for all the effort which has gone into this bug.

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  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
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1575872] 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/1575872

Title:
  USB Mouse freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I connect my USB mouse it works for some seconds and then it
  suddenly stops moving. The same mouse worked on Ubuntu 15.10. For the
  moment, I use a Bluetooth mouse which works without problems.

  When this happens dmesg contains a lot of lines with the following content:
  usb 2-1: input irq status -75 received

  There seem to be some other people with the same problem, but they did not 
find a solution yet. See here:
  
http://askubuntu.com/questions/760367/mouse-stop-working-after-login-ubuntu-16-04
  http://ubuntuforums.org/showthread.php?t=2322272=13478529#post13478529

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 1888 F pulseaudio
   /dev/snd/controlC1:  daniel 1888 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 20:48:33 2016
  HibernationDevice: RESUME=UUID=a67a91aa-8c15-4693-be37-7c177747bc39
  InstallationDate: Installed on 2016-04-22 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BWS03E00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=1a664dfb-0678-4b7f-ac6d-1b191c521109 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET53WW (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS03E00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET53WW(1.18):bd09/14/2015:svnLENOVO:pn20BWS03E00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS03E00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1575872] [NEW] USB Mouse freezes

[Daniel Saier]

Public bug reported:

When I connect my USB mouse it works for some seconds and then it
suddenly stops moving. The same mouse worked on Ubuntu 15.10. For the
moment, I use a Bluetooth mouse which works without problems.

When this happens dmesg contains a lot of lines with the following content:
usb 2-1: input irq status -75 received

There seem to be some other people with the same problem, but they did not find 
a solution yet. See here:
http://askubuntu.com/questions/760367/mouse-stop-working-after-login-ubuntu-16-04
http://ubuntuforums.org/showthread.php?t=2322272=13478529#post13478529

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  daniel 1888 F pulseaudio
 /dev/snd/controlC1:  daniel 1888 F pulseaudio
CurrentDesktop: Unity
Date: Wed Apr 27 20:48:33 2016
HibernationDevice: RESUME=UUID=a67a91aa-8c15-4693-be37-7c177747bc39
InstallationDate: Installed on 2016-04-22 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20BWS03E00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=1a664dfb-0678-4b7f-ac6d-1b191c521109 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET53WW (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS03E00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET53WW(1.18):bd09/14/2015:svnLENOVO:pn20BWS03E00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BWS03E00
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

** Description changed:

  When I connect my USB mouse it works for some seconds and then it
- suddenly stops moving. The same mouse worked on Ubuntu 15.10.
+ suddenly stops moving. The same mouse worked on Ubuntu 15.10. For the
+ moment, I use a Bluetooth mouse which works without problems.
  
  When this happens dmesg contains a lot of lines with the following content:
  usb 2-1: input irq status -75 received
  
  There seem to be some other people with the same problem, but they did not 
find a solution yet. See here:
  
http://askubuntu.com/questions/760367/mouse-stop-working-after-login-ubuntu-16-04
  http://ubuntuforums.org/showthread.php?t=2322272=13478529#post13478529
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  daniel 1888 F pulseaudio
-  /dev/snd/controlC1:  daniel 1888 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  daniel 1888 F pulseaudio
+  /dev/snd/controlC1:  daniel 1888 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 20:48:33 2016
  HibernationDevice: RESUME=UUID=a67a91aa-8c15-4693-be37-7c177747bc39
  InstallationDate: Installed on 2016-04-22 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BWS03E00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=1a664dfb-0678-4b7f-ac6d-1b191c521109 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-21-generic N/A
-  linux-backports-modules-4.4.0-21-generic  N/A
-  linux-firmware1.157
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET53WW (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS03E00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1556878] Re: CVE-2016-3137

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3137

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
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 

[Kernel-packages] [Bug 1556877] Re: CVE-2016-3136

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3136

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
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 

[Kernel-packages] [Bug 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
 Assignee: Tim Gardner (timg-tpi)
   Status: Fix Released

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-keystone (Ubuntu Yakkety)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

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

Title:
  Linux netfilter IPT_SO_SET_REPLACE memory corruption

Status in linux package in Ubuntu:
  Fix Released
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-keystone package in Ubuntu:
  Invalid
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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
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:
  Fix Released
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-keystone 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:
  Fix Released
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-keystone source package in Trusty:
  Fix Released
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 Released
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:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in 

[Kernel-packages] [Bug 1554260] Re: CVE-2016-2847

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Released

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

Title:
  CVE-2016-2847

Status in linux package in Ubuntu:
  Fix Released
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:
  Invalid
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 Committed
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:
  Fix Committed
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 Released
Status in linux-lts-xenial source package in Trusty:
  Fix Released
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

[Kernel-packages] [Bug 1547400] Re: aufs fails to handle sanitize xattrs in workdir, copies SUID binaries from no-suid fuse mounts

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Confirmed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

Title:
  aufs fails to handle sanitize xattrs in workdir, copies SUID binaries
  from no-suid fuse mounts

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Wily:
  New
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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

[Kernel-packages] [Bug 1549203] Re: CVE-2016-2550

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-2550

Status in linux package in Ubuntu:
  Fix Committed
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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
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 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 

[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
   Status: Fix Released

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  integer overflow in xt_alloc_table_info

Status in linux package in Ubuntu:
  Fix Released
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:
  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:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
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:
  Invalid
Status in linux source package in Trusty:
  Invalid
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:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Released
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 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 

[Kernel-packages] [Bug 1554262] Re: CVE-2016-2854

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

Title:
  CVE-2016-2854

Status in linux package in Ubuntu:
  New
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-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

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

[Kernel-packages] [Bug 1561410] Re: CVE-2016-2185

[Steve Beattie]

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2185

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  Fix Committed
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in 

[Kernel-packages] [Bug 1575706] Re: CVE-2016-2187

[Steve Beattie]

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

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

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

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

** Description changed:

  Kernel panic on invalid USB device descriptor (gtco driver)
+ 
+ Break-Fix: - 162f98dea487206d9ab79fc12ed64700667a894d

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

Title:
  CVE-2016-2187

Status in linux package in Ubuntu:
  New
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
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:
  New
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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

[Kernel-packages] [Bug 1561414] Re: CVE-2016-2188

[Steve Beattie]

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2188

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  Fix Committed
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in 

[Kernel-packages] [Bug 1549184] Re: CVE-2016-2545

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184

[Steve Beattie]

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2184

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  Fix Committed
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in 

[Kernel-packages] [Bug 1549200] Re: CVE-2016-2549

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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:

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 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 

[Kernel-packages] [Bug 1561411] Re: CVE-2016-2186

[Steve Beattie]

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2186

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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 package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  Fix Committed
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in 

[Kernel-packages] [Bug 1528904] Re: CVE-2015-8660

[Steve Beattie]

** Description changed:

  The ovl_setattr function in fs/overlayfs/inode.c in the Linux kernel
  through 4.3.3 attempts to merge distinct setattr operations, which
  allows local users to bypass intended access restrictions and modify the
  attributes of arbitrary overlay files via a crafted application.
  
- Break-Fix: - acff81ec2c79492b180fade3c2894425cd35a545
+ Break-Fix: e9be9d5e76e34872f0c37d72e25bc27fe9e2c54c
+ acff81ec2c79492b180fade3c2894425cd35a545

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

Title:
  CVE-2015-8660

Status in linux package in Ubuntu:
  Fix Released
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:
  Invalid
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:
  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-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-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:
  New
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:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
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:
  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 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:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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:
  Fix Released
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 

[Kernel-packages] [Bug 1546173] Re: CVE-2016-2383

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

Title:
  CVE-2016-2383

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:
  Invalid
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:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
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:
  Invalid
Status in linux source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1561414] Re: CVE-2016-2188

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

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

Title:
  CVE-2016-2188

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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:
  

[Kernel-packages] [Bug 1561411] Re: CVE-2016-2186

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

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

Title:
  CVE-2016-2186

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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:
  

[Kernel-packages] [Bug 1538449] Re: CVE-2016-2070

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-2070

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:
  Invalid
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:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
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:
  Invalid
Status in linux source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1546162] Re: CVE-2016-2085

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

Title:
  CVE-2016-2085

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

[Kernel-packages] [Bug 1561403] Re: CVE-2016-2117

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

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

Title:
  CVE-2016-2117

Status in linux package in Ubuntu:
  New
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:
  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-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:
  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-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-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:
  New
Status in linux-lts-vivid source package in Trusty:
  New
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-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 

[Kernel-packages] [Bug 1561410] Re: CVE-2016-2185

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

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

Title:
  CVE-2016-2185

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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:
  

[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Low
   Status: Fix Committed

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Low
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Low
   Status: Invalid

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

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

Title:
  CVE-2016-2184

Status in linux package in Ubuntu:
  Fix Committed
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:
  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:
  Fix Committed
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 Committed
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 Committed
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 Committed
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:
  

[Kernel-packages] [Bug 1575816] 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 1575816

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

Title:
  microsoft tech support phone number for windows 7   800 274 2129
  USA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  microsoft support 18002742129
  microsoft customer service"+1-800-274-2129"
  microsoft phone number
  microsoft help
  microsoft number  #@@+18002742129@@
  microsoft support number  
  windows support   ##1-800-274-2129@@#
  microsoft tech support
  microsoft contact 
  windows help  
  windows 7 support 
  microsoft office support  
  microsoft customer service number 1 800 274 2129
  microsoft contact number  
  microsoft technical support   "18002742129"
  microsoft xbox support
  microsoft helpline
  call microsoft
  microsoft customer support
  microsoft office help 
  microsoft service center  
  microsoft tech support number 
  microsoft support phone number
  microsoft tech support phone number   "@@1800-274-2129"
  microsoft technical support phone number  1800-274-2129
  windows tech support  
  windows customer service  
  contact microsoft support 
  microsoft customer care   
  microsoft office customer service 
  microsoft customer support number 
  microsoft customer service phone number   800 274 2129 USA
  microsoft windows support 
  microsoft phone support   

  windows support number
  windows technical support 
  microsoft support email   
  microsoft online support  
  windows xp support
  microsoft help number 
  windows support phone number  1800-274-2129
  microsoft technical support number
  microsoft help phone number   1-800-274-2129
  call microsoft support
  call from computer
  phone number for microsoft
  how to contact microsoft  
  microsoft office support phone number 1800-274-2129
  windows support software  
  microsoft office phone number 
  windows 7 help
  contact windows   
  microsoft office support number   
  windows live chat 
  microsoft contact us  
  microsoft office contact  
  microsoft telephone number
  windows tech support number   
  windows help and support  
  windows 8 help
  windows technical department  
  windows customer service number   
  windows helpline  
  contact support   
  windows 8.1 support   
  microsoft office technical support phone number   "@@1800-274-2129"
  microsoft office tech support phone number
  microsoft windows 7 support   
  microsoft office contact number   
  microsoft helpline number 
  support windows   
  microsoft live chat support   
  windows technical support phone number800 274 2129 USA
  windows contact number
  windows tech support phone number 800-274-2129 USA
  windows 8.1 help  
  microsoft online help 
  pc tech support   
  windows live support  
  windows live mail support 
  microsoft store support   
  computer technical support
  microsoft office tech support 
  contact microsoft office  
  chat with microsoft support   
  microsoft customer support phone number   1800-274-2129
  windows number
  windows technical support number  
  microsoft customer service and support
  microsoft tech18002742129  "+1-800-274-2129"
  microsoft help center 
  windows customer support  
  microsoft office customer service phone number #@@+18002742129@@
  email microsoft support   
  microsoft customer service email   ##1-800-274-2129@@#
  windows online support
  contact hotmail support   
  website support   
  ms office tech support phone number 1 800 274 2129
  microsoft office customer support phone number
  microsoft call  "18002742129"
  phone number for microsoft support
  windows help number   
  microsoft windows support number  
  windows live help 
  microsoft support help
  microsoft office customer service number  
  windows support center
  window support
  windows support tools"@@1800-274-2129"
  1800-274-2129
  microsoft product support 
  ms office support phone number
  windows customer support number   
  contact number for 

[Kernel-packages] [Bug 1575786] 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 1575786

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

Title:
  Mouse getting "stuck"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  I have a problem with my system freezing, not sure what is causing it.

  Like a minute ago, my mouse wouldn't click any links, but the mouse
  icon would change to that of when mousing over a hyper-link, when my
  mouse was such above the link. It appears to be focus problem, getting
  stuck somewhere.

  I'm not sure how to report it, because it's asking for an application and I 
don't know which application to put it under.
  I got it to freeze when editing the keyboard shortcuts via Unity Control 
Centre, twice as a double check after the first time, to see if it was just a 
coincidence.

  OS: Ubuntu 16.04 (Xenial) x64

  - Blossom
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.5.2-040502-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1575786] Re: Mouse getting "stuck"

[The Powerpuff Girls]

apport information

** Tags added: apport-collected xenial

** Description changed:

  
  I have a problem with my system freezing, not sure what is causing it.
  
  Like a minute ago, my mouse wouldn't click any links, but the mouse icon
  would change to that of when mousing over a hyper-link, when my mouse
  was such above the link. It appears to be focus problem, getting stuck
  somewhere.
  
  I'm not sure how to report it, because it's asking for an application and I 
don't know which application to put it under.
  I got it to freeze when editing the keyboard shortcuts via Unity Control 
Centre, twice as a double check after the first time, to see if it was just a 
coincidence.
  
  OS: Ubuntu 16.04 (Xenial) x64
  
  - Blossom
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-04-24 (2 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.5.2-040502-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1575786/+attachment/4649319/+files/JournalErrors.txt

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

Title:
  Mouse getting "stuck"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  I have a problem with my system freezing, not sure what is causing it.

  Like a minute ago, my mouse wouldn't click any links, but the mouse
  icon would change to that of when mousing over a hyper-link, when my
  mouse was such above the link. It appears to be focus problem, getting
  stuck somewhere.

  I'm not sure how to report it, because it's asking for an application and I 
don't know which application to put it under.
  I got it to freeze when editing the keyboard shortcuts via Unity Control 
Centre, twice as a double check after the first time, to see if it was just a 
coincidence.

  OS: Ubuntu 16.04 (Xenial) x64

  - Blossom
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.5.2-040502-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1575816] [NEW] microsoft tech support phone number for windows 7 800 274 2129 USA

[Richard]

Public bug reported:


microsoft support   18002742129
microsoft customer service  "+1-800-274-2129"
microsoft phone number  
microsoft help  
microsoft number#@@+18002742129@@
microsoft support number
windows support ##1-800-274-2129@@#
microsoft tech support  
microsoft contact   
windows help
windows 7 support   
microsoft office support
microsoft customer service number   1 800 274 2129
microsoft contact number
microsoft technical support "18002742129"
microsoft xbox support  
microsoft helpline  
call microsoft  
microsoft customer support  
microsoft office help   
microsoft service center
microsoft tech support number   
microsoft support phone number  
microsoft tech support phone number "@@1800-274-2129"
microsoft technical support phone number1800-274-2129
windows tech support
windows customer service
contact microsoft support   
microsoft customer care 
microsoft office customer service   
microsoft customer support number   
microsoft customer service phone number 800 274 2129 USA
microsoft windows support   
microsoft phone support 

windows support number  
windows technical support   
microsoft support email 
microsoft online support
windows xp support  
microsoft help number   
windows support phone number1800-274-2129
microsoft technical support number  
microsoft help phone number 1-800-274-2129
call microsoft support  
call from computer  
phone number for microsoft  
how to contact microsoft
microsoft office support phone number   1800-274-2129
windows support software
microsoft office phone number   
windows 7 help  
contact windows 
microsoft office support number 
windows live chat   
microsoft contact us
microsoft office contact
microsoft telephone number  
windows tech support number 
windows help and support
windows 8 help  
windows technical department
windows customer service number 
windows helpline
contact support 
windows 8.1 support 
microsoft office technical support phone number "@@1800-274-2129"
microsoft office tech support phone number  
microsoft windows 7 support 
microsoft office contact number 
microsoft helpline number   
support windows 
microsoft live chat support 
windows technical support phone number  800 274 2129 USA
windows contact number  
windows tech support phone number   800-274-2129 USA
windows 8.1 help
microsoft online help   
pc tech support 
windows live support
windows live mail support   
microsoft store support 
computer technical support  
microsoft office tech support   
contact microsoft office
chat with microsoft support 
microsoft customer support phone number 1800-274-2129
windows number  
windows technical support number
microsoft customer service and support  
microsoft tech  18002742129  "+1-800-274-2129"
microsoft help center   
windows customer support
microsoft office customer service phone number   #@@+18002742129@@
email microsoft support 
microsoft customer service email ##1-800-274-2129@@#
windows online support  
contact hotmail support 
website support 
ms office tech support phone number   1 800 274 2129
microsoft office customer support phone number  
microsoft call"18002742129"
phone number for microsoft support  
windows help number 
microsoft windows support number
windows live help   
microsoft support help  
microsoft office customer service number
windows support center  
window support  
windows support tools  "@@1800-274-2129"
1800-274-2129
microsoft product support   
ms office support phone number  
windows customer support number 
contact number for microsoft
microsoft technical support uk  
microsoft contact phone number  
microsoft support center  800 274 2129 USA
microsoft 1800 number   
microsoft contact info  
contact microsoft windows   
microsoft contact information   
windows help phone number   
microsoft windows technical support phone number
windows 7 help and support  
customer service microsoft  
microsoft help phone1800-274-2129
microsoft help and support  
contact windows support 1-800-274-2129
microsoft support contact number
windows customer care   
microsoft windows customer service  
contact microsoft by phone  
microsoft support contact   1800-274-2129
microsoft contact support   
microsoft support team  18002742129
how do i contact microsoft  "+1-800-274-2129"
microsoft support phone 
windows live chat support   #@@+18002742129@@
microsoft office tech support number
microsoft windows support phone number  ##1-800-274-2129@@#
microsoft customer services 
microsoft windows tech support  
call from microsoft 
microsoft telephone support 
telephone number for 

[Kernel-packages] [Bug 1538428] Re: CVE-2016-2053

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-2053

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:
  Invalid
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:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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 Committed
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:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
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 

[Kernel-packages] [Bug 1535150] Re: overlayfs over fuse should refuse copy_up of files if uid/gid not mapped

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
   Status: Fix Released

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

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

Title:
  overlayfs over fuse should refuse copy_up of files if uid/gid not
  mapped

Status in linux package in Ubuntu:
  Fix Released
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:
  Invalid
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-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 Released
Status in linux-lts-xenial source package in Trusty:
  Invalid
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:
  Fix Released
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 

[Kernel-packages] [Bug 1534961] Re: insecure overlayfs xattrs handling in copy_up

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Released

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  insecure overlayfs xattrs handling in copy_up

Status in linux package in Ubuntu:
  Fix Released
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:
  Invalid
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-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 Released
Status in linux-lts-xenial source package in Trusty:
  Invalid
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:
  Fix Released
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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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:
  Fix Committed
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 

[Kernel-packages] [Bug 1575786] ProcEnviron.txt

[The Powerpuff Girls]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1575786/+attachment/4649320/+files/ProcEnviron.txt

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

Title:
  Mouse getting "stuck"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  I have a problem with my system freezing, not sure what is causing it.

  Like a minute ago, my mouse wouldn't click any links, but the mouse
  icon would change to that of when mousing over a hyper-link, when my
  mouse was such above the link. It appears to be focus problem, getting
  stuck somewhere.

  I'm not sure how to report it, because it's asking for an application and I 
don't know which application to put it under.
  I got it to freeze when editing the keyboard shortcuts via Unity Control 
Centre, twice as a double check after the first time, to see if it was just a 
coincidence.

  OS: Ubuntu 16.04 (Xenial) x64

  - Blossom
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.5.2-040502-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1561389] Re: CVE-2016-0821

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-0821

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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
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 Committed
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:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
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 Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1561399] Re: CVE-2016-0823

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-0823

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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Released
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 Committed
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:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
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:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1563916] Re: CVE-2016-0774

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

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

Title:
  CVE-2016-0774

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:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
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 Committed
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:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
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:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Colin Ian King]

Looks like when CPUs going into a deep C state idle the latency jitter
is low, but when we go into a deep idle on a HLT or WAIT we're taking a
while to get active again.

With non-idle CPUs:

./clocktest 
Testing for clock jitter on 8 cpus
PASSED: largest jitter seen was 0.000184

Testing clock direction for 5 minutes...
PASSED: Iteration 0 delta: 0.62
PASSED: Iteration 1 delta: 0.59
PASSED: Iteration 2 delta: 0.60
PASSED: Iteration 3 delta: 0.58
PASSED: Iteration 4 delta: 0.60
clock direction test: sleeptime 60 sec per iteration, failed iterations: 0

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(_start, NULL);
  sleep(sleeptime);
  gettimeofday(_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  

[Kernel-packages] [Bug 1534887] Re: CVE-2016-0728

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
   Status: Fix Released

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: High
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: High
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: High
   Status: Invalid

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

Title:
  CVE-2016-0728

Status in linux package in Ubuntu:
  Fix Released
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:
  Invalid
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:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
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 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:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
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 

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

[Steve Beattie]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-fsl-imx51 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-manta (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-flo (Ubuntu Yakkety)
   Importance: Medium
   Status: New

** Also affects: linux-lts-trusty (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-wily (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Committed

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
   Status: Invalid

-- 
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:
  Invalid
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 Committed
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 Committed
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 

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[faulpeltz]

586fbce failed for me after 28 hours
It would be nice if we could have packages for maybe 2 further versions in the 
bisect (the current one + good/fail one), so we can run new builds back to back.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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
Status in linux source package in Xenial:
  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