[Kernel-packages] [Bug 1578929] Re: UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

[Gene Soo]

This error hits all of the GUI Distribution Installs. In other words the
only distribution not blown out of the water is Ubuntu Server.

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

Title:
  UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hard Failure with this message during Choosing Keyboard "Continue".

  Must cancel installation.

  Received additional error
  The Install encountered an error copying files to hard disk.

  [Errno 2] No such file or directory:  '/target/usr/lib/x86_64-linux-
  gnu/dri/vdpau_drv_video.so'

  Rest of message directs you to possible faulty hard disk.

  I am running under Virtualbox on solid hardware base so I strongly
  doubt hardware is a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-studio   1887 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: XFCE
  Date: Fri May  6 01:05:34 2016
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160505)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-lowlatency N/A
   linux-backports-modules-4.4.0-21-lowlatency  N/A
   linux-firmware   1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1577810] Re: Xbox 360 wireless controller LED light keeps flashing after sync

[Martin Wimpress]

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

** No longer affects: ubuntu-mate

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

Title:
  Xbox 360 wireless controller LED light keeps flashing after sync

Status in linux package in Ubuntu:
  New

Bug description:
  When connecting a Xbox 360 wireless controller on Ubuntu Mate 16.04
  the LED light continues to flash after syncing to the usb wireless
  receiver, instead of being a solid light indicating what player it is
  assigned. Tried it on Lubuntu 16.04 and its working as it should.

  It used to be a problem for a couple of years, but it was supposedly
  fixed in Kernel Update 4.2:

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

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

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

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

Title:
  UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hard Failure with this message during Choosing Keyboard "Continue".

  Must cancel installation.

  Received additional error
  The Install encountered an error copying files to hard disk.

  [Errno 2] No such file or directory:  '/target/usr/lib/x86_64-linux-
  gnu/dri/vdpau_drv_video.so'

  Rest of message directs you to possible faulty hard disk.

  I am running under Virtualbox on solid hardware base so I strongly
  doubt hardware is a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-studio   1887 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: XFCE
  Date: Fri May  6 01:05:34 2016
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160505)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-lowlatency N/A
   linux-backports-modules-4.4.0-21-lowlatency  N/A
   linux-firmware   1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1578929] [NEW] UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

[Gene Soo]

Public bug reported:

Hard Failure with this message during Choosing Keyboard "Continue".

Must cancel installation.

Received additional error
The Install encountered an error copying files to hard disk.

[Errno 2] No such file or directory:  '/target/usr/lib/x86_64-linux-
gnu/dri/vdpau_drv_video.so'

Rest of message directs you to possible faulty hard disk.

I am running under Virtualbox on solid hardware base so I strongly doubt
hardware is a problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
Uname: Linux 4.4.0-21-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu-studio   1887 F pulseaudio
CasperVersion: 1.376
CurrentDesktop: XFCE
Date: Fri May  6 01:05:34 2016
IwConfig:
 enp0s3no wireless extensions.
 
 lono wireless extensions.
LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160505)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-lowlatency N/A
 linux-backports-modules-4.4.0-21-lowlatency  N/A
 linux-firmware   1.157
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "Log Files to Support Problem report"
   
https://bugs.launchpad.net/bugs/1578929/+attachment/4656905/+files/ubuntu-studio.tar.gz

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

Title:
  UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

Status in linux package in Ubuntu:
  New

Bug description:
  Hard Failure with this message during Choosing Keyboard "Continue".

  Must cancel installation.

  Received additional error
  The Install encountered an error copying files to hard disk.

  [Errno 2] No such file or directory:  '/target/usr/lib/x86_64-linux-
  gnu/dri/vdpau_drv_video.so'

  Rest of message directs you to possible faulty hard disk.

  I am running under Virtualbox on solid hardware base so I strongly
  doubt hardware is a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-studio   1887 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: XFCE
  Date: Fri May  6 01:05:34 2016
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160505)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-lowlatency N/A
   linux-backports-modules-4.4.0-21-lowlatency  N/A
   linux-firmware   1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2

[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

[Milos]

I am experiencing the very same issue on my Lenovo Thinkpad P50.

16.04
4.6.0-040600rc1

It is really annoying.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  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=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

Re: [Kernel-packages] [Bug 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

[Victor van der Lee]

Can someone please post the solution for someone (like me) who doesn't
write code ?

Thank you,
Victor.

2016-05-05 13:51 GMT+02:00 Reinhard Kreuzer :

> Hi,
>
> I'm using a Lenovo Thinkpad E555 with Ubuntu 16.04 Unity.
> I applied the patch from Ralf Lübben and now the webcam works.
> Though, the patch didn't work at first due to wrong path '---
> a/drivers/...' and '+++ b/driver/...', but typing the full path manually
> after it asked me to worked fine.
>
> Thank you,
> Reinhard
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1433906
>
> Title:
>   Acer, Inc ID 5986:055a is useless after 14.04.2 installed.
>
> Status in HWE Next:
>   Won't Fix
> Status in linux-lts-utopic package in Ubuntu:
>   Triaged
> Status in linux-lts-vivid package in Ubuntu:
>   Triaged
> Status in linux-lts-wily package in Ubuntu:
>   Confirmed
> Status in linux-lts-xenial package in Ubuntu:
>   Confirmed
> Status in linux package in Arch Linux:
>   New
> Status in Fedora:
>   Unknown
>
> Bug description:
>   CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
>   CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic)
>
>   Steps:
>   1. Install 14.04.2 on E450 or E555.
>   2. Log in system and open a terminal.
>   3. $ gst-launch-0.10 v4l2src ! xvimagesink
>
>   Expected result:
>   Camara is activated
>
>   Actual result:
>   $  gst-launch-0.10 v4l2src ! xvimagesink
>   Setting pipeline to PAUSED ...
>   ERROR: Pipeline doesn't want to pause.
>   ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot
> identify device '/dev/video0'.
>   Additional debug info:
>   v4l2_calls.c(497): gst_v4l2_open ():
> /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
>   system error: No such file or directory
>   Setting pipeline to NULL ...
>   Freeing pipeline ...
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified:
> boot/vmlinuz-3.16.0-30-generic]
>   ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
>   Uname: Linux 3.16.0-30-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 2.14.1-0ubuntu3.7
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Thu Mar 19 02:21:31 2015
>   InstallationDate: Installed on 2015-03-16 (2 days ago)
>   InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150218.1)
>   SourcePackage: linux-lts-utopic
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hwe-next/+bug/1433906/+subscriptions
>

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

Title:
  Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

Status in HWE Next:
  Won't Fix
Status in linux-lts-utopic package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Triaged
Status in linux-lts-wily package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in Fedora:
  Unknown

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450 or E555.
  2. Log in system and open a terminal.
  3. $ gst-launch-0.10 v4l2src ! xvimagesink

  Expected result:
  Camara is activated

  Actual result:
  $  gst-launch-0.10 v4l2src ! xvimagesink
  Setting pipeline to PAUSED ...
  ERROR: Pipeline doesn't want to pause.
  ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot 
identify device '/dev/video0'.
  Additional debug info:
  v4l2_calls.c(497): gst_v4l2_open (): 
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
  system error: No such file or directory
  Setting pipeline to NULL ...
  Freeing pipeline ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: 
boot/vmlinuz-3.16.0-30-generic]
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 02:21:31 2015
  InstallationDate: Installed on 2015-03-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1578916] [NEW] Hibernate not working on Ubuntu 16.04 LTS

[Swapnil Bhavsar]

Public bug reported:

Hibernate is not working on Ubuntu 16.04 LTS for my HP Pavilion g6
laptop.

Laptop Specs:
Processor: Intel Core i5 3210
Chipset: B75 Express
Graphics : Intel HD4000m / AMD 7670m
RAM: 8 GB

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:  swapnil1853 F pulseaudio
CurrentDesktop: Unity
Date: Fri May  6 10:51:59 2016
HibernationDevice: RESUME=UUID=8309f535-564b-475c-b049-f76cb4408140
InstallationDate: Installed on 2016-05-01 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=b2f9e75c-9600-49b6-a701-69d38d7b910b 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
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 183E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr08841138591610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 08841138591610100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

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

Title:
  Hibernate not working on Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hibernate is not working on Ubuntu 16.04 LTS for my HP Pavilion g6
  laptop.

  Laptop Specs:
  Processor: Intel Core i5 3210
  Chipset: B75 Express
  Graphics : Intel HD4000m / AMD 7670m
  RAM: 8 GB

  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:  swapnil1853 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 10:51:59 2016
  HibernationDevice: RESUME=UUID=8309f535-564b-475c-b049-f76cb4408140
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=b2f9e75c-9600-49b6-a701-69d38d7b910b 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr08841138591610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 08841138591610100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

Title:
  Hibernate not working on Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hibernate is not working on Ubuntu 16.04 LTS for my HP Pavilion g6
  laptop.

  Laptop Specs:
  Processor: Intel Core i5 3210
  Chipset: B75 Express
  Graphics : Intel HD4000m / AMD 7670m
  RAM: 8 GB

  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:  swapnil1853 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 10:51:59 2016
  HibernationDevice: RESUME=UUID=8309f535-564b-475c-b049-f76cb4408140
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=b2f9e75c-9600-49b6-a701-69d38d7b910b 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr08841138591610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 08841138591610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1578317] Re: Regression: Mouse stuck at start-up

[Walter Garcia-Fontes]

** Summary changed:

- Mouse stuck at start-up
+ Regression: Mouse stuck at start-up

** Tags added: regression-release

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

Title:
  Regression: Mouse stuck at start-up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My mouse is stuck at start-up. A workaround is to enter "sudo rmmod
  usbhid; modprobe usbhid" and the mouse starts working.

  josep@josep-GJ306AA-ABE-m8175-es:~$ lsusb
  Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
  Bus 008 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface 
Subclass)
  Bus 008 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface 
Subclass)
  Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 004: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  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:  josep  1664 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 19:08:48 2016
  HibernationDevice: RESUME=UUID=b0bbcadd-00af-44cd-8f5d-eea7fee41c90
  InstallationDate: Installed on 2016-04-28 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: HP-Pavilion GJ306AA-ABE m8175.es
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=816f2dbe-34e1-4512-a2b8-565bc86cb28e 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
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.05
  dmi.board.name: Berkeley
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: GJ306AA-ABE m8175.es
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1578721] Re: linux: 4.4.0-22.39 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1578721

Title:
  linux: 4.4.0-22.39 -proposed tracker

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

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

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

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1545399] Re: hp af008ax ubuntu wifi signal weak

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

Title:
  hp af008ax ubuntu wifi signal weak

Status in linux package in Ubuntu:
  Expired

Bug description:
  hp af008ax ubuntu wifi signal is very weak changed the Changing power
  options as well. But didnt help

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 14 11:19:53 2016
  InstallationDate: Installed on 2016-02-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1547897] Re: kernel 4.2.0-27 does not boot on h170 board

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

Title:
  kernel 4.2.0-27 does not boot on h170 board

Status in linux package in Ubuntu:
  Expired

Bug description:
  I upgraded the kernel from 3.13.0-77 to 4.2.0-27.  But kernel 4.2.0-27
  does not boot on h170 board.  The mother board I am using is ASRock
  H170 Pro4 .   The boot process just stops after a few seconds.   The
  installation dvd does not boot either.  I can not get to the
  installation gui.  The kernel just prints acpi errors continuously.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 09:32:28 2016
  InstallationDate: Installed on 2013-04-02 (1054 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2016-02-19 (1 days ago)

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

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

[Kernel-packages] [Bug 1544737] Re: wireless does not work on aspire e15

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

Title:
  wireless does not work on aspire e15

Status in linux package in Ubuntu:
  Expired

Bug description:
  wireless could not be enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Feb 11 22:33:28 2016
  InstallationDate: Installed on 2016-02-11 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1391674] Re: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O

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

Title:
  "Reset adapter unexpectedly" - NIC hangs using e1000e driver under
  average I/O

Status in linux package in Ubuntu:
  Expired

Bug description:
  Using ubuntu 14.04 LTS

  > uname -a
  Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  /var/log/syslog:

  Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: 
Reset adapter unexpectedly
  Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered 
disabled state
  Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered 
forwarding state
  Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered 
forwarding state
  Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: 
Detected Hardware Unit Hang:
  Nov 11 23:29:08 argeste kernel: [846171.956810]   TDH  <0>
  Nov 11 23:29:08 argeste kernel: [846171.956810]   TDT  <1>
  Nov 11 23:29:08 argeste kernel: [846171.956810]   next_to_use  <1>
  Nov 11 23:29:08 argeste kernel: [846171.956810]   next_to_clean<0>
  Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]:
  Nov 11 23:29:08 argeste kernel: [846171.956810]   time_stamp   
<10c9ab819>
  Nov 11 23:29:08 argeste kernel: [846171.956810]   next_to_watch<0>
  Nov 11 23:29:08 argeste kernel: [846171.956810]   jiffies  
<10c9ab9d1>
  Nov 11 23:29:08 argeste kernel: [846171.956810]   next_to_watch.status <0>
  Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status 
<40080183>
  Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d>
  Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status  <3800>
  Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000>
  Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10>
  Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: 
Detected Hardware Unit Hang:
  Nov 11 23:29:10 argeste kernel: [846173.956722]   TDH  <0>
  Nov 11 23:29:10 argeste kernel: [846173.956722]   TDT  <1>
  Nov 11 23:29:10 argeste kernel: [846173.956722]   next_to_use  <1>
  Nov 11 23:29:10 argeste kernel: [846173.956722]   next_to_clean<0>
  Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]:
  Nov 11 23:29:10 argeste kernel: [846173.956722]   time_stamp   
<10c9ab819>
  Nov 11 23:29:10 argeste kernel: [846173.956722]   next_to_watch<0>
  Nov 11 23:29:10 argeste kernel: [846173.956722]   jiffies  
<10c9abbc5>
  Nov 11 23:29:10 argeste kernel: [846173.956722]   next_to_watch.status <0>
  Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status 
<40080183>
  Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Status <796d>
  Nov 11 23:29:10 argeste kernel: [846173.956722] PHY 1000BASE-T Status  <3800>
  Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Extended Status<3000>
  Nov 11 23:29:10 argeste kernel: [846173.956722] PCI Status <10>
  Nov 11 23:29:12 argeste kernel: [846175.956759] e1000e :00:19.0 eth1: 
Detected Hardware Unit Hang:
  Nov 11 23:29:12 argeste kernel: [846175.956759]   TDH  <0>
  Nov 11 23:29:12 argeste kernel: [846175.956759]   TDT  <1>
  Nov 11 23:29:12 argeste kernel: [846175.956759]   next_to_use  <1>
  Nov 11 23:29:12 argeste kernel: [846175.956759]   next_to_clean<0>
  Nov 11 23:29:12 argeste kernel: [846175.956759] buffer_info[next_to_clean]:
  Nov 11 23:29:12 argeste kernel: [846175.956759]   time_stamp   
<10c9ab819>
  Nov 11 23:29:12 argeste kernel: [846175.956759]   next_to_watch<0>
  Nov 11 23:29:12 argeste kernel: [846175.956759]   jiffies  
<10c9abdb9>
  Nov 11 23:29:12 argeste kernel: [846175.956759]   next_to_watch.status <0>
  Nov 11 23:29:12 argeste kernel: [846175.956759] MAC Status 
<40080183>
  Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Status <796d>
  Nov 11 23:29:12 argeste kernel: [846175.956759] PHY 1000BASE-T Status  <3800>
  Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Extended Status<3000>
  Nov 11 23:29:12 argeste kernel: [846175.956759] PCI Status <10>
  Nov 11 23:29:14 argeste kernel: [846177.956686] e1000e :00:19.0 eth1: 
Detected Hardware Unit Hang:
  Nov 11 23:29:14 argeste kernel: [846177.956686]   TDH  <0>

[Kernel-packages] [Bug 1347008] Re: Call trace and “TCP: out of memory… consider tuning tcp_mem”

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

Title:
  Call trace and “TCP: out of memory… consider tuning tcp_mem”

Status in linux package in Ubuntu:
  Expired

Bug description:
  The install on a remote machine was upgraded to the trusty-lts kernel
  as stated in the HWE instructions. There is a bridge (br0) configured
  with the Ethernet interface (eth0) through the interfaces(5)
  configuration. After a couple of hours the machine would only respond
  to ICMP queries and connections with all services running on TCP ports
  could not be established. Therefore, a hard reboot was issued.
  Attached is the contents of /var/log/kern.log, post-reboot, with what
  seems to be relevant information (call trace, kernel message with
  “TCP: out of memory… consider tuning tcp_mem”, etc) around the
  relevant timespan. Inbound services running on TCP ports being
  inaccessible was first noticed around 02:30 (the machine's time). This
  matches up with the first “out of memory” message.

  The machine is running precise 12.04.4:

  valdearg@blair:~$ uname -a;dpkg -l linux-generic-lts-trusty 
linux-image-3.13.0-32-generic;grep 'LTS' /etc/lsb-release;lspci|grep Ether 
  Linux blair 3.13.0-32-generic #57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version  
Description
  
+++---
  ii  linux-generic-lts-trusty 3.13.0.32.28 
Generic Linux kernel image and headers
  ii  linux-image-3.13.0-32-generic3.13.0-32.57~precise1
Linux kernel image for version 3.13.0 on 64 bit x86 SMP
  DISTRIB_DESCRIPTION="Ubuntu 12.04.4 LTS"
  04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

  
  This incident might be related to these bug reports:
  https://bugzilla.kernel.org/show_bug.cgi?id=77481
  https://lists.debian.org/debian-kernel/2014/04/msg00184.html

  Please let me know if there is anything else I can provide.

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

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

[Kernel-packages] [Bug 1351996] Re: nouveau kernel driver: failed suspend, -16

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

Title:
  nouveau kernel driver: failed suspend, -16

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have intel/noveau hybrid graphics, and recently installed the Trusty
  HWE.

  Now when I try to go to suspend, it fails with errors from the nouveau
  kernel driver:

   [ 3139.483363] nouveau  [ DRM] suspending display...
   [ 3139.483365] nouveau  [ DRM] unpinning framebuffer(s)...
   [ 3139.483368] nouveau  [ DRM] evicting buffers...
   [ 3139.483369] nouveau  [ DRM] waiting for kernel channels to go idle...
   [ 3139.483411] nouveau  [ DRM] suspending client object trees...
   [ 3139.484327] nouveau  [ DRM] suspending kernel object tree...
   [ 3141.487119] nouveau E[   
PDISP][:01:00.0][0xc000857c][880231adb180] fini timeout, 0xc2061008
   [ 3141.487121] nouveau E[   
PDISP][:01:00.0][0xc000857c][880231adb180] failed suspend, -16
   [ 3141.487123] nouveau E[ DRM] 0xd150:0xd15c7c00 suspend failed with 
-16
   [ 3141.487151] nouveau E[ DRM] 0x:0xd150 suspend failed with 
-16
   [ 3141.487258] nouveau E[ DRM] 0x:0x suspend failed with 
-16
   [ 3141.488005] nouveau E[ DRM] 0x:0x suspend failed with 
-16
   [ 3141.488114] nouveau  [ DRM] resuming display...
   [ 3141.507688] pci_pm_suspend(): nouveau_pmops_suspend+0x0/0xd0 [nouveau] 
returns -16
   [ 3141.507691] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
   [ 3141.507693] PM: Device :01:00.0 failed to suspend async: error -16
   [ 3141.507735] PM: Some devices failed to suspend, or early wake event 
detected

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Aug  3 20:46:49 2014
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-08-03 (0 days ago)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-32-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nobled 2239 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf740 irq 56'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0269,15581500,00100100 
HDA:80862805,15581500,0010'
 Controls  : 39
 Simple ctrls  : 15
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=1d0e531b-8312-4c2f-b247-bd7379e9ef92
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: CLEVO CO. W150HRM
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=UUID=edbd5209-22ff-45f1-843c-0e4cbbfcc662 ro i915.i915_enable_fbc=1 
i915.i915_enable_rc6=0x1 drm.debug=0x0 kmemleak=off slub_debug=- splash 
i915.i915_enable_fbc=1 i915.i915_enable_rc6=0x1 drm.debug=0x0 kmemleak=off 
slub_debug=- vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.79.14
  Tags:  precise running-unity
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-08-03 (0 days ago)
  UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare 
wireshark
  dmi.bios.date: 05/31/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W150HRM
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd05/31/2011:svnCLEVOCO.:pnW150HRM:pvrN/A:rvnCLEVOCO.:rnW150HRM:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.n

[Kernel-packages] [Bug 1541918] Re: fix bug as soon as possible

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

Title:
  fix bug as soon as possible

Status in linux package in Ubuntu:
  Expired

Bug description:
  Network problem

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-60-generic 3.16.0-60.80~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
  Uname: Linux 3.16.0-60-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Thu Feb  4 21:47:51 2016
  InstallationDate: Installed on 2015-12-18 (48 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1344795] Re: Suspend/resume not working after HWE EOL upgrade to 3.13.0-32

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

Title:
  Suspend/resume not working after HWE EOL upgrade to  3.13.0-32

Status in linux package in Ubuntu:
  Expired

Bug description:
  IBM R50e running 12.04. Upgrade Tool  – Kernel von 3.5 to 3.13.0-32
  led to above problem. Graphic chip: Intel Extreme Graphics 2

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Sat Jul 19 11:29:05 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: Upgraded to precise on 2013-10-25 (266 days ago)

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

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

[Kernel-packages] [Bug 1332940] Re: Kernel oops during movie play with vlc - freeze of screen

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

Title:
  Kernel oops during movie play with vlc - freeze of screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have both video and audio over HDMI. In the middle of watching a
  dvd-movie with vlc the screen froze but audio continued to play via
  HDMI. Also I was still able to connect with ssh to the linux-pc.

  Here is the syslog that was generated:

  Jun 22 11:06:12 localhost kernel: [149202.892989] BUG: unable to handle 
kernel NULL pointer dereference at 0069
  Jun 22 11:06:12 localhost kernel: [149202.893042] IP: [] 
syscall_trace_enter+0x14a/0x280
  Jun 22 11:06:12 localhost kernel: [149202.893078] PGD b5a72067 PUD b5a73067 
PMD 0
  Jun 22 11:06:12 localhost kernel: [149202.893105] Oops:  [#1] SMP
  Jun 22 11:06:12 localhost kernel: [149202.893126] Modules linked in: 
ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 
ip6table_filter ip6_tables xt_nat xt_tcpudp xt_state ipt_MASQUERADE xt_LOG 
xt_limit iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables bnep rfcomm 
bluetooth arc4 ath9k mac80211 joydev snd_hda_codec_hdmi snd_hda_codec_realtek 
i915 snd_hda_intel snd_hda_codec ath9k_common snd_hwdep ath9k_hw snd_pcm 
snd_seq_midi snd_rawmidi ath snd_seq_midi_event snd_seq snd_timer 
drm_kms_helper snd_seq_device snd cfg80211 drm mxm_wmi gpio_ich video mei_me 
lpc_ich mac_hid serio_raw mei soundcore snd_page_alloc wmi bonding lp parport 
ses enclosure hid_generic usbhid hid igb ahci libahci dca i2c_algo_bit r8169 
mii ptp pps_core megaraid_sas
  Jun 22 11:06:12 localhost kernel: [149202.893720] CPU: 3 PID: 5991 Comm: vlc 
Not tainted 3.13.0-27-generic #50~precise1-Ubuntu
  Jun 22 11:06:12 localhost kernel: [149202.893751] Hardware name: Gigabyte 
Technology Co., Ltd. Z68X-UD3H-B3/Z68X-UD3H-B3, BIOS F12 03/20/2012
  Jun 22 11:06:12 localhost kernel: [149202.893787] task: 88020824afe0 ti: 
88020833a000 task.ti: 88020833a000
  Jun 22 11:06:12 localhost kernel: [149202.893815] RIP: 
0010:[]  [] syscall_trace_enter+0x14a/0x280
  Jun 22 11:06:12 localhost kernel: [149202.893851] RSP: 0018:88020833bf08  
EFLAGS: 00010246
  Jun 22 11:06:12 localhost kernel: [149202.893873] RAX: 00ca RBX: 
7f605000a728 RCX: 0089
  Jun 22 11:06:12 localhost kernel: [149202.893900] RDX: 7f605000a72c RSI: 
e576e574 RDI: 0246
  Jun 22 11:06:12 localhost kernel: [149202.893926] RBP: 88020833bf48 R08: 
507f R09: 7f6045944d30
  Jun 22 11:06:12 localhost kernel: [149202.893953] R10: 7f6045944d30 R11: 
0001 R12: 00ca
  Jun 22 11:06:12 localhost kernel: [149202.893981] R13:  R14: 
ff92 R15: 
  Jun 22 11:06:12 localhost kernel: [149202.894009] FS:  7f6045945700() 
GS:88021fac() knlGS:
  Jun 22 11:06:12 localhost kernel: [149202.894039] CS:  0010 DS:  ES:  
CR0: 80050033
  Jun 22 11:06:12 localhost kernel: [149202.894062] CR2: 0069 CR3: 
b5a7e000 CR4: 000407e0
  Jun 22 11:06:12 localhost kernel: [149202.894088] Stack:
  Jun 22 11:06:12 localhost kernel: [149202.894098]  8102290d 
  7f605000a728
  Jun 22 11:06:12 localhost kernel: [149202.894132]  507f 
7f6045944d30 ff92 
  Jun 22 11:06:12 localhost kernel: [149202.894166]  7f6045944e50 
81765f1c  ff92
  Jun 22 11:06:12 localhost kernel: [149202.894199] Call Trace:
  Jun 22 11:06:12 localhost kernel: [149202.895754]  [] ? 
syscall_trace_leave+0xdd/0x150
  Jun 22 11:06:12 localhost kernel: [149202.897263]  [] 
tracesys+0x7e/0xe6
  Jun 22 11:06:12 localhost kernel: [149202.898739] Code: 00 4c 8b 4b 68 4c 8b 
43 60 48 8b 4b 58 48 8b 53 28 0f 85 ef 00 00 00 4d 85 ed 48 c7 c0 ff ff ff ff 
75 04 48 8b 43 78 48 8b 5d d8 <4c> 8b 65 e0 4c 8b 6d e8 4c 8b 75 f0 4c 8b 7d f8 
c9 c3 0f 1f 40
  Jun 22 11:06:12 localhost kernel: [149202.900429] RIP  [] 
syscall_trace_enter+0x14a/0x280
  Jun 22 11:06:12 localhost kernel: [149202.902030]  RSP 
  Jun 22 11:06:12 localhost kernel: [149202.903630] CR2: 0069
  Jun 22 11:06:12 localhost kernel: [149202.914008] ---[ end trace 
84ca3afe81b6d89d ]---

  After the oops I tried to get to a tty-console (to get rid of the
  frozen screen) with ctrl-alt-F1 but then also audio playback stopped
  and I got those syslogs:

  Jun 22 11:07:12 localhost pulseaudio[2233]: [alsa-sink] protocol-native.c: 
Failed to push data into queue
  Jun 22 11:07:23 localhost 

[Kernel-packages] [Bug 1352161] Re: Screen remains blank after sleep on HP netbook, i945GME video chipset

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

Title:
  Screen remains blank after sleep on HP netbook, i945GME video chipset

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  HP mini netbook, 2GB RAM, atom processor

  from dmesg:
  [0.087839] smpboot: CPU0: Intel(R) Atom(TM) CPU N280   @ 1.66GHz (fam: 
06, model: 1c, stepping: 02)

  [1.299784] Linux agpgart interface v0.103
  [1.299985] agpgart-intel :00:00.0: Intel 945GME Chipset
  [1.300151] agpgart-intel :00:00.0: detected gtt size: 262144K total, 
262144K mappable
  [1.300292] agpgart-intel :00:00.0: detected 8192K stolen memory
  [1.300539] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xd000

  Obviously, this is not an nvidia driver issue already mentioned on
  launchpad.

  This seems to be related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938

  I can successfully  ftp, telnet or SSH to the netbook after I try to
  wake it, but the screen refuses to turn on.

  It also seems to recognise new USB devices that are plugged in while
  the screen remains blank.

  Ctrl-Alt-f1 allowed me to login and type (without seeing the typed text)
  shutdown -r now
  at which point the netbook restarted, and everything I was doing was gone.

  I recently installed cpulimit to address the ongoing xapian index
  retrieval resource hogging bug mentioned here,

  https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/830333

  but after that I installed a bunch of updates that were due through
  the update manager, including the latest kernel.

  For now, I have told the power manager to not sleep the screen.

  Cheers,

  Erich

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Mon Aug  4 15:16:26 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1537458] Re: [REGRESSION] Kernel from Willy in 14.04 doesn't detect key shortcuts to change brightness

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

Title:
  [REGRESSION] Kernel from Willy in 14.04 doesn't detect key shortcuts
  to change brightness

Status in linux package in Ubuntu:
  Expired

Bug description:
  Kernel from Willy in 14.04 doesn't detect key shortcuts to change
  brightness. Before that it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jan 24 09:04:38 2016
  InstallationDate: Installed on 2016-01-23 (0 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1535521] Re: kernel stack trace

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

Title:
  kernel stack trace

Status in linux package in Ubuntu:
  Expired

Bug description:
  When I booted into 3.19.0.43 from Ubuntu 14.04.3 .   The kernel
  stopped during boot.  I checked dmesg. There was a stack trace.  The
  motherboard I used is a ASRock H170M Pro4  Bios p1.8.  The following
  is the stack trace.

   [8.484935] [drm] Replacing VGA console driver
  [8.489503] Console: switching to colour dummy device 80x25
  [8.492850] usbcore: registered new interface driver btusb
  [8.503446] audit: type=1400 audit(1453175142.377:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=600 comm="apparmor_parser"
  [8.503654] audit: type=1400 audit(1453175142.377:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=600 
comm="apparmor_parser"
  [8.504798] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [8.504800] [drm] Driver supports precise vblank timestamp query.
  [8.506398] BUG: unable to handle kernel NULL pointer dereference at 
0060
  [8.506403] IP: [] ddi_get_encoder_port+0x5/0x70 
[i915_bpo]
  [8.506428] PGD 274ff3067 PUD 274494067 PMD 0
  [8.506430] Oops:  [#1] SMP
  [8.506432] Modules linked in: snd_seq(+) snd_seq_device snd_timer snd 
btusb soundcore i915_bpo(+) intel_ips drm_kms_helper drm i2c_algo_bit shpchp 
8250_fintek wmi video i2c_hid mac_hid acpi_pad parport_pc ppdev coretemp 
hwmon_vid rfcomm lp parport bnep bluetooth nfsd auth_rpcgss nfs_acl nfs 
binfmt_misc lockd grace sunrpc fscache hid_generic hid_logitech_dj usbhid hid 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
megaraid_sas psmouse e1000e ptp ahci pps_core libahci raid6_pq raid1 raid0 
multipath linear dm_mirror dm_region_hash dm_log
  [8.506457] CPU: 0 PID: 634 Comm: systemd-udevd Not tainted 
3.19.0-43-generic #49~14.04.1-Ubuntu
  [8.506459] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./H170M Pro4, BIOS P1.80 11/10/2015
  [8.506461] task: 880275f6f5c0 ti: 8802751c8000 task.ti: 
8802751c8000
  [8.506463] RIP: 0010:[]  [] 
ddi_get_encoder_port+0x5/0x70 [i915_bpo]
  [8.506482] RSP: 0018:8802751cb750  EFLAGS: 00010286
  [8.506483] RAX:  RBX: 88007180 RCX: 
8802755c1800
  [8.506484] RDX: 8802751cb7a4 RSI: 8802751cb7b0 RDI: 
fff8
  [8.506485] RBP: 8802751cb7e8 R08: 8802751c8000 R09: 
0246
  [8.506487] R10: 0004 R11: 0005 R12: 
8802755c1800
  [8.506488] R13: c0760770 R14: fffee35b R15: 
0001
  [8.506489] FS:  7f4aa208d880() GS:880280c0() 
knlGS:
  [8.506491] CS:  0010 DS:  ES:  CR0: 80050033
  [8.506492] CR2: 0060 CR3: 000274ff2000 CR4: 
003407f0
  [8.506493] DR0:  DR1:  DR2: 

  [8.506494] DR3:  DR6: fffe0ff0 DR7: 
0400
  [8.506495] Stack:
  [8.506496]  c0706fe1 880280d8e4c0  
027a
  [8.506499]  817b677c 0246 8802755c1b60 
8802755c1800
  [8.506501]  fff8  88007180 

  [8.506503] Call Trace:
  [8.506522]  [] ? intel_prepare_ddi+0x71/0x390 [i915_bpo]
  [8.506527]  [] ? 
schedule_hrtimeout_range_clock+0xac/0x160
  [8.506541]  [] skl_set_power_well+0x421/0xae0 [i915_bpo]
  [8.506555]  [] skl_power_well_enable+0x13/0x20 
[i915_bpo]
  [8.506568]  [] intel_display_power_get+0xa6/0x100 
[i915_bpo]
  [8.506578]  [] intel_display_set_init_power+0x45/0x50 
[i915_bpo]
  [8.506587]  [] intel_power_domains_init_hw+0x204/0x340 
[i915_bpo]
  [8.506606]  [] i915_driver_load+0x7d4/0xeb0 [i915_bpo]
  [8.506608]  [] ? cleanup_uevent_env+0x10/0x10
  [8.506610]  [] ? kobject_uevent_env+0x178/0x690
  [8.506614]  [] ? devtmpfs_create_node+0x100/0x130
  [8.506616]  [] ? get_device+0x17/0x30
  [8.506618]  [] ? klist_class_dev_get+0x15/0x20
  [8.506620]  [] ? klist_node_init+0x38/0x50
  [8.506622]  [] ? klist_add_tail+0x46/0x50
  [8.506624]  [] ? device_add+0x289/0x650
  [8.506632]  [] drm_dev_register+0xb5/0x110 [drm]
  [8.506638]  [] drm_get_pci_dev+0x8f/0x200 [drm]
  [8.506649]  [] i915_pci_probe+0x3b/0x60 [i915_bpo]
  [8.506653]  [] local_pci_probe+0x45/0xa0
  [8.506655]  [] ? pci_match_device+0xe5/0x110
  [8.506657]  [] pci_device_probe+0xd9/0

[Kernel-packages] [Bug 1532756] Re: Nvidia 780 GTX not recognized with lspci

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

Title:
  Nvidia 780 GTX not recognized with lspci

Status in linux package in Ubuntu:
  Expired

Bug description:
  Dear Support,

  I purchased a 3 MSI Z170A M7 mainboard. 2 are installed with Windows10 and a  
Geforce 980 GTX Titan and they
  work just fine. Now i'm configuring my workstation with ubuntu 140.04.3 LTS. 
everything is working now except the 
  video card is not detected by Ubuntu? 

  
  jaime@yb-wks1-linux:~/Downloads$ lspci -v | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 06) (prog-if 00 [VGA controller])
  jaime@yb-wks1-linux:~/Downloads$ lspci -nn | grep '\[03'
  00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake 
Integrated Graphics [8086:1912] (rev 06)

  
  Please assist.

  Best regards and thanks in advance

  Jaime de Ruijter

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Jan 11 11:52:49 2016
  InstallationDate: Installed on 2016-01-08 (3 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1550621] Re: Latest kernel update broke Toshiba Chromebook 2 touchpad

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

Title:
  Latest kernel update broke Toshiba Chromebook 2 touchpad

Status in linux package in Ubuntu:
  Expired

Bug description:
  Latest kernel update broke Toshiba Chromebook 2 touchpad in Wily.
  Device not showing up in /proc/bus/input/devices

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

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

[Kernel-packages] [Bug 1548111] Re: Wifi don't work properly in ubuntu 15.10(ralink rt3290)

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

Title:
  Wifi don't work properly in ubuntu 15.10(ralink rt3290)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Before in ubuntu 15.10 , ralink rt3290 wifi driver worked good but now it  
down randomly.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=91d2ca2b-3098-49a9-83e1-d96fccf3da73
  InstallationDate: Installed on 2015-04-17 (310 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=UUID=6b9abcb6-a1cf-4a4c-871a-8364b0c7d8dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1001) is not owned by us (uid 1000), but by uid 1001! (This could e 
g happen if you try to connect to a non-root PulseAudio as a root user, over 
the native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 226E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 74.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn226E:rvr74.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097610405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1548850] Re: Suspend-Resume freezes the computer completely

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

Title:
  Suspend-Resume freezes the computer completely

Status in linux package in Ubuntu:
  Expired

Bug description:
  I’m using HP 250 G3 notebook. When closing the screen and reopening it, the 
system should suspend and resume. However, when I reopen the computer, the 
system is completely frozen. I can’t move the mouse, keyboard strokes don’t get 
recongnized, not even Ctrl+Alt+F1 to get to the rescue terminal where I could 
at least reboot the computer. Instead, the only solution I found was to press 
the power button for several seconds.
  Being able to suspend the computer is very important for me. What can I do 
about this?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-headers-4.2.0-30 4.2.0-30.35
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  babbl  1584 F pulseaudio
   /dev/snd/controlC1:  babbl  1584 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Feb 23 15:28:30 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=34ce0104-ddbf-4b6e-8f5b-2012550d55ef
  InstallationDate: Installed on 2015-10-17 (129 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  Lsusb:
   Bus 003 Device 003: ID 064e:9320 Suyin Corp. 
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=ce32a0c7-c1c0-4a26-90c2-6466918c1e3d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-02-23 (0 days ago)
  dmi.bios.date: 10/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.44
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd10/23/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.44:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1548984] Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000005c

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  005c

Status in linux package in Ubuntu:
  Expired

Bug description:
  System working fine until latest update

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-7-generic 4.4.0-7.22
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whb1779 F pulseaudio
   /dev/snd/controlC0:  whb1779 F pulseaudio
  Date: Tue Feb 23 10:21:11 2016
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: 0010:location  location radeon_pm_set_clocks+0x270/0x590 [radeon]
  Failure: oops
  HibernationDevice: RESUME=UUID=9d2bcb15-ad11-46ff-92b5-9f8ecdc94132
  InstallationDate: Installed on 2016-01-10 (44 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160103)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic 
root=UUID=bfefefbf-f125-46ce-845b-22a16f9d3520 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
005c
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1549272] Re: Couldn't enable Wi-Fi and touchpad is not being detected in Acer Aspire E5-511

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

Title:
  Couldn't enable Wi-Fi and touchpad is not being detected in Acer
  Aspire E5-511

Status in linux package in Ubuntu:
  Expired

Bug description:
  Couldn't enable Wi-Fi, and touchpad is not being detected in Acer Aspire 
E5-511
  I have installed Ubuntu 14.04 OS yesterday. Yesterday it was working fine, I 
installed java, eclipse with android sdk. And then today, Wi-Fi and my 
touch-pad not working. What to do??

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1 [modified: 
boot/vmlinuz-4.2.0-27-generic]
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 24 17:47:54 2016
  InstallationDate: Installed on 2016-02-23 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1552851] Re: syslog flooded with xhci_hcd warnings "WARN Event TRB for slot 1 ep 8 with no TDs queued?"

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

Title:
  syslog flooded with xhci_hcd warnings "WARN Event TRB for slot 1 ep 8
  with no TDs queued?"

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello

  I have the same problem that is reported in bug #1541997 when accessing an 
iphone from a kvm win8.1 vm.
  when itunes is doing work on the attached iphone I see at the same time lots 
of theses messages on the syslog :

  Mar 3 08:17:08 minipc kernel: [33225.434065] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.436941] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.439516] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.443396] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.443885] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.456807] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.457482] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.604472] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.605532] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:08 minipc kernel: [33225.605969] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:14 minipc kernel: [33232.287805] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:14 minipc kernel: [33232.288289] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:14 minipc kernel: [33232.290624] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:14 minipc kernel: [33232.291562] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:14 minipc kernel: [33232.316241] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:14 minipc kernel: [33232.317267] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:15 minipc kernel: [33232.484784] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?
  Mar 3 08:17:15 minipc kernel: [33232.485561] xhci_hcd :00:14.0: WARN 
Event TRB for slot 11 ep 10 with no TDs queued?

  itunes seems to be able to work with the iphone (sync, backup). But
  the syslog is flooded with theses warnings.

  My bios and version :
  sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
  RYBDWi35.86A.0350.2015.0812.1722
  08/12/2015

  PC is
  Manufacturer: Intel Corporation
  Product Name: NUC5i5RYB

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-lowlatency 4.2.0-30.36
  ProcVersionSignature: Ubuntu 4.2.0-30.36-lowlatency 4.2.8-ckt3
  Uname: Linux 4.2.0-30-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pascal 3919 F pulseaudio
   /dev/snd/pcmC1D0p:   pascal 3919 F...m pulseaudio
   /dev/snd/controlC1:  pascal 3919 F pulseaudio
   /dev/snd/controlC0:  pascal 3919 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Mar  3 19:23:54 2016
  InstallationDate: Installed on 2015-01-03 (425 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-lowlatency 
root=UUID=076b58d2-a51a-4802-a928-ddafdecc1b83 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-lowlatency N/A
   linux-backports-modules-4.2.0-30-lowlatency  N/A
   linux-firmware   1.149.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-22 (132 days ago)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

[Kernel-packages] [Bug 1548820] Re: usb keyboard does not work in debian installer

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

Title:
  usb keyboard does not work in debian installer

Status in linux package in Ubuntu:
  Expired

Bug description:
  in ubuntu 15.10 and 14.04 64bit server iso images, the installation
  with usb keyboard is impossible, because the keyboard stops working
  after grub (at language selection).

  i have replicated this behaviour on HP Microserver N36L, HP
  Microserver N40L, HP Microserver N54L, Gigabyte z87x-d3h and many
  others i tried.

  No bios/uefi settings can fix this. it does not matter whether they
  keyboards are connected to usb2 or usb3 ports.

  this behaviour does NOT happen on 14.04 ubuntu mini isos (MinimalCD),
  but these don't support uefi boot.

  it is possible this bug is the same as bug # 1244176 which is closed

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

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

[Kernel-packages] [Bug 1550367] Re: Ubuntu 15.10 Toshiba touchpad

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

Title:
  Ubuntu 15.10 Toshiba touchpad

Status in linux package in Ubuntu:
  Expired

Bug description:
  Yesterday I installed new ubuntu 15.10 desktop on my laptop and
  problem is with my touchpad. I tried install synaptiks, touchpad-
  indicator and It's still not working. When I type "toshiba satellite
  e55-a5114 ubuntu touchpad" in google search I saw a lot of bugs with
  touchpad in my laptop. Is possible to install some touchpad drivers
  and if yes, how? xinput

  
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ Logitech USB Receiver id=10   [slave  pointer  (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpad  id=13   [slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Power Button  id=8[slave  keyboard (3)]
  ↳ Logitech USB Receiver id=9[slave  keyboard (3)]
  ↳ TOSHIBA Web Camera - HD   id=11   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=12   [slave  keyboard (3)]
  ↳ Toshiba input device  id=14   [slave  keyboard (3)]

  
  xinput --list-props 11

  
  Device 'ETPS/2 Elantech Touchpad':
Device Enabled (139):   1
Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (266): 1
Device Accel Constant Deceleration (267):   2.50
Device Accel Adaptive Deceleration (268):   1.00
Device Accel Velocity Scaling (269):12.50
Synaptics Edges (270):  123, 2974, 96, 1697
Synaptics Finger (271): 1, 1, 0
Synaptics Tap Time (272):   180
Synaptics Tap Move (273):   157
Synaptics Tap Durations (274):  180, 100, 100
Synaptics ClickPad (275):   1
Synaptics Middle Button Timeout (276):  0
Synaptics Two-Finger Pressure (277):282
Synaptics Two-Finger Width (278):   7
Synaptics Scrolling Distance (279): 71, 71
Synaptics Edge Scrolling (280): 0, 0, 0
Synaptics Two-Finger Scrolling (281):   1, 1
Synaptics Move Speed (282): 1.00, 1.75, 0.055897, 0.00
Synaptics Off (283):2
Synaptics Locked Drags (284):   0
Synaptics Locked Drags Timeout (285):   5000
Synaptics Tap Action (286): 2, 3, 0, 0, 1, 3, 0
Synaptics Click Action (287):   1, 3, 0
Synaptics Circular Scrolling (288): 0
Synaptics Circular Scrolling Distance (289):0.10
Synaptics Circular Scrolling Trigger (290): 0
Synaptics Circular Pad (291):   0
Synaptics Palm Detection (292): 0
Synaptics Palm Dimensions (293):10, 200
Synaptics Coasting Speed (294): 20.00, 50.00
Synaptics Pressure Motion (295):30, 160
Synaptics Pressure Motion Factor (296): 1.00, 1.00
Synaptics Resolution Detect (297):  1
Synaptics Grab Event Device (298):  0
Synaptics Gestures (299):   1
Synaptics Capabilities (300):   1, 0, 0, 1, 1, 1, 1
Synaptics Pad Resolution (301): 31, 31
Synaptics Area (302):   0, 0, 0, 0
Synaptics Soft Button Areas (303):  1548, 0, 1470, 0, 0, 0, 0, 0
Synaptics Noise Cancellation (304): 17, 17
Device Product ID (259):2, 14
Device Node (260):  "/dev/input/event5"

  
  After install latest mainline kernels touchpad still not working.

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

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

[Kernel-packages] [Bug 1548317] Re: kernel: [some.number] Bluetooth: hci0 ACL packet for unknown connection handle ##

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

Title:
  kernel: [some.number] Bluetooth: hci0 ACL packet for unknown
  connection handle ##

Status in linux package in Ubuntu:
  Expired

Bug description:
  Bluetooth receiver doesn't connect with kernel after sleep/boot-up. The 
receiver is awake because "kernel: [339132.269449] Bluetooth: hci0 ACL packet 
for unknown connection handle ##" appears in the system log because I'm shaking 
the mouse.
  Sometimes it takes over 4 minutes of shaking to reconnect the mouse.

  I do not know where to report this bug.

  Is it the kernel? Because it's the kernel that report that something is 
happening on the bluetooth receiver.
  Is it HCI? Because if I reset hci0, I have to shake the mouse again.
  Is it the hardware driver that enter sleep mode incorrectly?
  And finally, is it the bluetooth stack?

  This machine runs Ubuntu 16.04 but I've had this  problem as long as I've had 
this computer. It's a Lenovo G50-45 with a Realtek 8723BE Wifi/Bluetooth combo 
HARDCODED into the BIOS (It will not boot if you change the network card to 
something else, like Intel 7260).
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fredrik1894 F pulseaudio
   /dev/snd/controlC1:  fredrik1894 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9ec0fd10-34c8-49e3-b061-5a4ead3a24a9
  InstallationDate: Installed on 2015-01-22 (395 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic 
root=UUID=fce91e77-dd20-4685-92a5-d75cd06ff8b6 ro persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  Tags:  xenial
  Uname: Linux 4.4.0-6-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2015-05-26 (272 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1548961] Re: BUG: unable to handle kernel paging request at ffffc90005459200

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

Title:
  BUG: unable to handle kernel paging request at c90005459200

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've been led to believe this bug is related to my pc's bios.  Perhaps a 
conflict with GRUB?  I don't know enough to say.  If you come across this bug 
report and understand what the problem might be, PLEASE send me a note to 
briefly explain and suggest what the logical remedy is.  I have had this 
problem ongoing for over a year, it only is a problem some times, I suspect 
whenever the update process tries to update the bootloader?
  Thank you.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  don2100 F pulseaudio
   /dev/snd/controlC0:  don2100 F pulseaudio
  Date: Sat Feb 20 16:03:05 2016
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location memcpy+0xd/0x110
  Failure: oops
  HibernationDevice: RESUME=UUID=ffd2b5a3-0e8e-4f9b-9288-cff133a90145
  InstallationDate: Installed on 2011-12-18 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=9f13b409-27bd-4e42-99c0-59fccdb87241 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at c90005459200
  UpgradeStatus: Upgraded to trusty on 2014-08-18 (554 days ago)
  dmi.bios.date: 07/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1548895] Re: kernel BUG at /build/linux-KZRqSQ/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:10243!

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

Title:
  kernel BUG at /build/linux-
  KZRqSQ/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:10243!

Status in linux package in Ubuntu:
  Expired

Bug description:
  in update error and reboot system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hernan 2538 F pulseaudio
  Date: Tue Feb 23 11:24:32 2016
  Failure: oops
  InstallationDate: Installed on 2015-04-24 (304 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Intel Corporation Crestline & ICH8M Chipset
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic 
root=UUID=a29f3c46-7cd0-4448-a8fb-be79c03a967c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-KZRqSQ/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:10243!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: SROSA001.86C.0046.D.0710121416
  dmi.board.name: SANTA ROSA CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrSROSA001.86C.0046.D.0710121416:bd10/12/2007:svnIntelCorporation:pnCrestline&ICH8MChipset:pvrNotApplicable:rvnIntelCorporation:rnSANTAROSACRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Crestline & ICH8M Chipset
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1548896] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 35s! [sbcl:12933]

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 35s! [sbcl:12933]

Status in linux package in Ubuntu:
  Expired

Bug description:
  Nothing

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fila   9860 F pulseaudio
  Date: Tue Feb 23 11:14:43 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=343abcbb-2c24-4340-84fd-e2cae839f116
  InstallationDate: Installed on 2014-02-24 (728 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic 
root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 35s! [sbcl:12933]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1548521] Re: kernel BUG at /build/linux-tSJmM_/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:10243!

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

Title:
  kernel BUG at /build/linux-
  tSJmM_/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:10243!

Status in linux package in Ubuntu:
  Expired

Bug description:
  lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 4.4.0.6.7
Candidate: 4.4.0.6.7
Version table:
   *** 4.4.0.6.7 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erelesse   1229 F pulseaudio
  Date: Tue Feb 23 00:10:18 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=63ef6815-2fd1-44e8-b1b3-09bcb51f585c
  InstallationDate: Installed on 2016-02-22 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160222)
  MachineType: Sony Corporation VGN-FE770G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic 
root=UUID=c86d5044-62e5-4dd9-a13e-358d76afb64b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-tSJmM_/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:10243!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0173J3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: 7R2L34eb42975aead93c
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: C3LMWGAC
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0173J3:bd09/21/2006:svnSonyCorporation:pnVGN-FE770G:pvrC3LMWGAC:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrC3LMWGAC:
  dmi.product.name: VGN-FE770G
  dmi.product.version: C3LMWGAC
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1553044] Re: Ethernet Connection randomly disconnects after transmit queue 0 timed out

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

Title:
  Ethernet Connection randomly disconnects after transmit queue 0 timed
  out

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description of problem:

  Ethernet connection gets disconnected at random apparently without any
  reason. I have tried the following command to restart my ethernet
  connection, `sudo service network-manager restart` though it never
  solved the issue. Every time I have to restart my system to get the
  connection back.

  see: `http://askubuntu.com/questions/615423/ethernet-connection-
  randomly-disconnects-after-transmit-queue-0-timed-out`

  OBSERVATION: It happens more frequently when I make calls in skype or
  hangout. It seems that heavy usage of Ethernet is causing the
  disconnection. It happens in both 32bit and 64bit.

  Debug steps tried so far:

  I tried to change from `r8169` to `r8168` but never solved the
  problem, ethernet connection is unstable as before.

  $ lspci -nnk | grep -iA2 net
  06:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network 
Adapter (PCI-Express) [168c:002b] (rev 01)
  Subsystem: Lenovo Device [17aa:30a1]
  Kernel driver in use: ath9k
  07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
  Subsystem: Lenovo Device [17aa:392e]
  Kernel driver in use: r8169

  $ dmesg -T | grep eth0
  [Sat May  2 19:52:37 2015] r8169 :07:00.0: eth0: RTL8102e at 
0xc9348000, 88:ae:1d:3a:ec:ff, XID 04e0 IRQ 41
  [Sat May  2 19:52:45 2015] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [Sat May  2 19:52:51 2015] r8169 :07:00.0: eth0: link down
  [Sat May  2 19:52:51 2015] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [Sat May  2 19:52:51 2015] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [Sat May  2 19:52:56 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 19:52:56 2015] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes 
ready
  [Sat May  2 20:09:01 2015] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 
timed out
  [Sat May  2 20:09:01 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:09:13 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:09:19 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:09:31 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:10:13 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:10:55 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:12:07 2015] r8169 :07:00.0: eth0: link up
  [Sat May  2 20:13:49 2015] r8169 :07:00.0: eth0: link up

  After the event as shown in dmesg output my connection is lost.

  NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

  As a Solution to the problem:

  I installed kernel version `3.2.0-83-generic` manually, it solved the
  problem and ethernet connection is perfect.

  Other kernels in which ethernet connection is stable: 3.2.0-98-generic, 
3.2.0-83-generic
  Other kernels in which ethernet connection is not stable: 4.2.0-27-generic, 
4.2.0-30-generic, 3.13.0-33-generic, 3.13.0-36-generic, 3.5.0-27-generic

  So it seems to be related to the kernel not with my hardware nor the
  driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Mar  4 11:55:30 2016
  InstallationDate: Installed on 2016-02-29 (3 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1551566] Re: gnome-session logs out with Fatal IO error 11

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

Title:
  gnome-session logs out with Fatal IO error 11

Status in linux package in Ubuntu:
  Expired

Bug description:
  My desktop just froze and I could not press any keys.

  When I tried CTRL+ALT+F1 I got logged out from my gnome session and
  the graphical (!) login window appeared.

  There's some messages in my syslog, e.g. gdk-warning gnome-session
  fatal io error 11 (resource temporarily unavailable) on x server

  Plus, the syslog indicates that dbus service has gone ("Unable to
  contact D-Bus").

  Processor: Intel i5 520M
  Display: 
  *-display
   Beschreibung: VGA compatible controller
   Produkt: Core Processor Integrated Graphics Controller
   Hersteller: Intel Corporation
   Physische ID: 2
   Bus-Informationen: pci@:00:02.0
   Version: 02
   Breite: 64 bits
   Takt: 33MHz
   Fähigkeiten: msi pm vga_controller bus_master cap_list rom
   Konfiguration: driver=i915 latency=0
   Ressourcen: irq:26 memory:f000-f03f 
memory:e000-efff ioport:8080(Größe=8)

  
  May be related: https://bugs.freedesktop.org/show_bug.cgi?id=92505

  Mar  1 07:05:55 lat61 gnome-session[3946]: Gdk-WARNING: gnome-session: Fatal 
IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.#012
  Mar  1 07:05:55 lat61 bluetoothd[1931]: Endpoint unregistered: sender=:1.62 
path=/MediaEndpoint/HFPAG
  Mar  1 07:05:55 lat61 bluetoothd[1931]: Endpoint unregistered: sender=:1.62 
path=/MediaEndpoint/HFPHS
  Mar  1 07:05:55 lat61 bluetoothd[1931]: Endpoint unregistered: sender=:1.62 
path=/MediaEndpoint/A2DPSource
  Mar  1 07:05:55 lat61 bluetoothd[1931]: Endpoint unregistered: sender=:1.62 
path=/MediaEndpoint/A2DPSink
  Mar  1 07:05:55 lat61 bluetoothd[1931]: hci0: Remove UUID (0x0011) failed: 
Busy (0x0a)
  Mar  1 07:05:55 lat61 colord: device removed: xrandr-eDP1
  Mar  1 07:05:55 lat61 colord: Profile removed: 
icc-e45d9840cbe35d110970eaeda5e0962a
  Mar  1 07:05:55 lat61 colord: Profile removed: 
icc-c84991a3ae2b0aeec63c6e75ebdeff52
  Mar  1 07:05:55 lat61 colord: Profile removed: 
icc-54e2f468d87b8e30fdd2bd2a278fd0bc
  Mar  1 07:05:55 lat61 acpid: client 2681[0:0] has disconnected
  Mar  1 07:05:55 lat61 kernel: [540289.175127] dell_wmi: Unknown WMI event 
type 0x11: 0xffd0
  Mar  1 07:05:56 lat61 pulseaudio[19042]: [pulseaudio] client-conf-x11.c: 
xcb_connection_has_error() liefert »true«
  Mar  1 07:05:56 lat61 rtkit-daemon[3048]: Successfully made thread 19047 of 
process 19047 (n/a) owned by '1000' high priority at nice level -11.
  Mar  1 07:05:56 lat61 rtkit-daemon[3048]: Supervising 1 threads of 1 
processes of 1 users.
  Mar  1 07:05:56 lat61 pulseaudio[19047]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mar  1 07:05:56 lat61 rtkit-daemon[3048]: Successfully made thread 19051 of 
process 19047 (n/a) owned by '1000' RT at priority 5.
  Mar  1 07:05:56 lat61 rtkit-daemon[3048]: Supervising 2 threads of 1 
processes of 1 users.
  Mar  1 07:05:56 lat61 rtkit-daemon[3048]: Successfully made thread 19052 of 
process 19047 (n/a) owned by '1000' RT at priority 5.
  Mar  1 07:05:56 lat61 rtkit-daemon[3048]: Supervising 3 threads of 1 
processes of 1 users.
  Mar  1 07:05:56 lat61 pulseaudio[19047]: [pulseaudio] server-lookup.c: Unable 
to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
socket /tmp/dbus-a4J0kF4Rxq: Verbindungsaufbau abgelehnt
  Mar  1 07:05:56 lat61 pulseaudio[19047]: [pulseaudio] main.c: Unable to 
contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket 
/tmp/dbus-a4J0kF4Rxq: Verbindungsaufbau abgelehnt
  Mar  1 07:05:56 lat61 bluetoothd[1931]: Endpoint registered: sender=:1.228 
path=/MediaEndpoint/HFPAG
  Mar  1 07:05:56 lat61 bluetoothd[1931]: Endpoint registered: sender=:1.228 
path=/MediaEndpoint/HFPHS
  Mar  1 07:05:56 lat61 bluetoothd[1931]: Endpoint registered: sender=:1.228 
path=/MediaEndpoint/A2DPSource
  Mar  1 07:05:56 lat61 bluetoothd[1931]: Endpoint registered: sender=:1.228 
path=/MediaEndpoint/A2DPSink
  Mar  1 07:05:56 lat61 pulseaudio[19047]: [pulseaudio] 
module-bluetooth-device.c: Default profile not connected, selecting off profile
  Mar  1 07:05:57 lat61 kernel: [540290.346424] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  Mar  1 07:05:57 lat61 kernel: [540290.346455] 
[drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO 
underrun
  Mar  1 07:05:57 lat61 acpid: input device has been disconnected, fd 13
  Mar  1 07:05:57 lat61 kernel: [540290.703007] dell_wmi: Unknown WMI event 
type 0

[Kernel-packages] [Bug 1248289] Re: Missing libunwind support in perf

[Dmitry Rekman]

Does this problem not affect Canonical developers working on, say, Mir
(which is written in C++)?  It is way more painful to profile
applications on stock Ubuntu.

This can mean that Mir developers are not interested in performance of
their server, which I hope is a wrong conclusion to draw.

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

Title:
  Missing libunwind support in perf

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm trying to use perf's libunwind support in 13.04 with kernel
  3.11.0-12-generic on amd64.  Typically you can do this by using the
  "-g dwarf" flag, but it appears the perf command included in linux-
  tools-3.11.0-12-generic was not compiled with libunwind.  This may be
  as simple as the build machine didn't have libunwind installed.
  Having dwarf support in perf with default Ubuntu kernels would be very
  useful as it provides a way to get profiling information when
  -fomitframepointer is used.

  Relevant upstream code:

  https://github.com/torvalds/linux/blob/v3.11/tools/perf/Makefile#L459
  https://github.com/torvalds/linux/blob/v3.11/tools/perf/builtin-record.c#L758

  Let me know if I can provide any other information.

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

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

[Kernel-packages] [Bug 1571241] Re: ZFS initrd script does not import zpool using /dev/disk/by-id device paths

[Richard Laager]

@svde-tech: Can you please test from this PPA:
https://launchpad.net/~rlaager/+archive/ubuntu/zfs

Here's what I think should happen. Right now, you're seeing /dev/sdX
names. If you reboot with this package, you'll still see /dev/sdX names.
Reboot again and edit your GRUB command line (at boot, not permanently)
and change the pool name to be wrong. When the initrd fails to import
it, import it manually with: zpool import -d /dev/disk/by-id -f -R / -N
POOLNAME Then export it with: zpool export POOLNAME Finally: reboot At
that point, the system should come up normally.

I tested this and it works for me.

If you do test from my PPA, please remove it from your APT sources when
you're done testing. I don't want some future experiment I upload to
break your system.

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

Title:
  ZFS initrd script does not import zpool using /dev/disk/by-id device
  paths

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 includes initrd zfs support, but the provided script does
  not allow zpools to be imported using the /dev/disk/by-id paths. As a
  result, the pool will be imported using "/dev/sdX" device names, which
  is not the preferred way.

  Tested and validated solution/proof of concept:

   - extract system generated initrd
   - edit scripts/zfs file: replace "zpool import -o readonly=on -N" with 
"zpool import -o readonly=on -d /dev/disk/by-id -N"
   - manually generate initrd using the altered script (using cpio)
   - replace system generated initrd with altered one

  I'd suggest adding a variable to /etc/default/zfs that would be
  reflected in the initrd zfs script, but perhaps the ZoL folks are
  better suited to give advice on this.

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

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

[Kernel-packages] [Bug 1567558] Re: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac

[Richard Laager]

@stgraber: If this is something you can reproduce (e.g. in a VM) using zfs-dkms 
rather than the pre-compiled zfs.ko from linux-image, can you please test from 
this PPA:
https://launchpad.net/~rlaager/+archive/ubuntu/zfs

The package there has the patch from upstream.

If you do test from my PPA, please remove it from your APT sources when
you're done testing. I don't want some future experiment I upload to
break your system.

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

Title:
  ZFS is confused by user namespaces (uid/gid mapping) when used with
  acltype=posixac

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

Bug description:
  This report is copy/paste from the following upstream issue:
  https://github.com/zfsonlinux/zfs/issues/4177

  I was asked to file a matching Ubuntu bug for tracking.

  
  Hello,

  # First a quick introduction to the world of containers

  I'm the project leader for LXC and LXD, working on containers on
  Linux. We now extensively use the user namespaces to provide an extra
  layer of security in Linux containers.

  The user namespace allows one to map a range of uid and gid from the
  host or parent namespace into another range of uid and gid of a new
  namespace.

  Typically what's done is that 65536 uids and gids are set aside per
  non-system users on the host. Those users through a couple of setuid
  helpers (newuidmap and newgidmap) can then setup a uid and gid map for
  their processes. Their 65536 allocation is therefore mapped from
  uid/gid 0 to 65536 of the new namespace, providing a POSIX-compatible
  environment.

  That means that given a user on the host with uid and gid range 10
  through 165536, uid 100 in their container will be mapped to uid
  100100 outside of it.

  # The problem with ZFS

  When using ZFS with acltype=posixacl and an ACL entry on the host set
  for a uid (or gid) that's then mapped into the container, the
  container doesn't see the right mapped value when querying the acl
  from inside the namespace.

  # Example with zfs (broken)

  root@dakara:~# zfs create lxd/test -o mountpoint=/tmp/test
  root@dakara:~# zfs set acltype=posixacl lxd/test
  root@dakara:~# cd /tmp/test/
  root@dakara:/tmp/test# mkdir a
  root@dakara:/tmp/test# setfacl -m default:user:100100:rwX a
  root@dakara:/tmp/test# setfacl -m user:100100:rwX a
  root@dakara:/tmp/test# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536 
-- /bin/bash
  root@dakara:/tmp/test (in userns)# ls -lh
  total 512
  drwxrwxr-x+ 2 nobody nogroup 2 Jan  7 22:19 a

  root@dakara:/tmp/test (in userns)# getfacl -n a
  # file: a
  # owner: nobody
  # group: nogroup
  user::rwx
  user:4294967295:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:4294967295:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Example with ext4 (working)

  root@dakara:/tmp/test.ext4# mkdir a

  root@dakara:/tmp/test.ext4# setfacl -m default:user:100100:rwX a

  root@dakara:/tmp/test.ext4# setfacl -m user:100100:rwX a

  root@dakara:/tmp/test.ext4# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test.ext4# lxc-usernsexec -m u:0:10:65536 -m 
g:0:10:65536 -- /bin/bash
  root@dakara:/tmp/test.ext4 (in userns)# ls -lh
  total 4.0K
  drwxrwxr-x+ 2 nobody nogroup 4.0K Jan  7 22:22 a

  root@dakara:/tmp/test.ext4 (in userns)# getfacl -n a
  # file: a
  # owner: 65534
  # group: 65534
  user::rwx
  user:100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Environment

  This was noticed on Ubuntu 14.04 using the zfs stable PPA. I first
  found it in production environments first with file servers
  misbehaving due to the problem, then reproduced it on my development
  systems.

  The zfs version here is 0.6.5.3-1~trusty and I've seen this on 3.13,
  3.16, 3.19 and 4.2 kernels (not that it should matter, the dkms code
  was the same). zfs-dkms is at 2.53-zfs1.

  The lxc-usernsexec helper tool I'm using there comes from the LXC
  package in Ubuntu. It essentially causes a call to fork() followed by
  a call to unshare(CLONE_NEWUSER), then calls the newuidmap and
  newgidmap setuid helpers with the provided map so that the namespace
  can be configured properly.

  You could reproduce something similar using the simple unshare tool
  and manu

[Kernel-packages] [Bug 1532198] Re: [MIR] zfs-linux

[Richard Laager]

It turns out that this is still necessary. zfsutils-linux installs
/usr/share/man/man8/zed.8.gz, which is also installed by zfs-zed. That
needs to be fixed at the same time the Replaces is versioned. If I'm
understanding correctly, Policy says a versioned Breaks should be added
too.

I've made these changes (along with other bug fixes) here:
https://launchpad.net/~rlaager/+archive/ubuntu/zfs

If you do test from my PPA, please remove it from your APT sources when
you're done testing. I don't want some future experiment I upload to
break your system.

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

Title:
  [MIR] zfs-linux

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Following the process documented at
  https://wiki.ubuntu.com/MainInclusionProcess , the following template
  needs to be filled in to start the MIR for zfs-linux in 16.04

  Below are my answers to the various main inclusion requirements,
  marked by a * prefix:

  [Availability]:

"The package must already be in the Ubuntu universe, and must
build for the architectures it is designed to work on."

* http://packages.ubuntu.com/xenial/admin/zfsutils-linux
* Yes - built for 64 bit arches only, because ZFS is designed to run
  well only on 64 bit architectures.

  [Rationale]:

"There must be a certain level of demand for the package, for example:
The package is useful for a large part of our user base."

* Yes - there is a lot of interest in ZFS in the server space and for
  users wanting to use a file system that supports huge collections of
  disks with excellent reliable features such as checksummed raid,
mirroring
  striping with easy configuration and also simple data sanity checking and
  fixing.
* Being requested by Kiko

"The package is a new build dependency or dependency of a package that we
already support (additionally, the official image builder requires all
used packages be in main)."

* Yes, already in Wily as a technology demo.

"The package helps meet a specific Blueprint goal."

* No blueprint goal.

"The package replaces another package we currently support and promises
higher quality and/or better features, so that we can drop the old
package from the supported set."

* Not applicable


  [Security]:
"The security history and the current state of security issues in
the package must allow us to support the package for at least 18 months
without exposing its users to an inappropriate level of security risks.
This requires checking of several things that are explained in detail in
the subsection Security checks."

"Check how many vulnerabilities the package had in the past and how they
were handled by upstream and the Debian/Ubuntu package:"

"http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability
 Database using the package as a keyword"

NO ZFS Linux CVEs found, here is the complete list from Mitre:

  CVE-2015-1415
The bsdinstall installer in FreeBSD 10.x before 10.1 p9, when configuring
full disk encrypted ZFS, uses world-readable permissions for the GELI
keyfile (/boot/encryption.key), which allows local users to obtain sensitive
key information by reading the file.

  CVE-2015-0448
Unspecified vulnerability in Oracle Sun Solaris 11.2 allows local users to
affect confidentiality, integrity, and availability via vectors related to
ZFS File system.

  CVE-2013-3266
The nfsrvd_readdir function in sys/fs/nfsserver/nfs_nfsdport.c in the new
NFS server in FreeBSD 8.0 through 9.1-RELEASE-p3 does not verify that a
READDIR request is for a directory node, which allows remote attackers to
cause a denial of service (memory corruption) or possibly execute arbitrary
code by specifying a plain file instead of a directory.

  CVE-2011-2313
Unspecified vulnerability in Oracle Solaris 10 allows local users to affect
availability, related to ZFS.

  CVE-2011-2312
Unspecified vulnerability in Oracle Solaris 10 allows local users to affect
confidentiality, related to ZFS.

  CVE-2011-2311
Unspecified vulnerability in Oracle Solaris 10 allows local users to affect
availability, related to ZFS.

  CVE-2011-2286
Unspecified vulnerability in Oracle Solaris 10 and 11 Express allows remote
authenticated users to affect availability, related to ZFS.

  CVE-2010-4458
Unspecified vulnerability in Oracle Solaris 11 Express allows local users
to affect availability, related to ZFS.

  CVE-2010-3540
Unspecified vulnerability in Oracle Solaris 10 and OpenSolaris allows local
users to affect availability, related to ZFS.

  CVE-2010-2392
Unspecified vulnerability in Oracle Solaris 10 and OpenSolaris allows local
users to affect integrity and availability, rel

[Kernel-packages] [Bug 1577057] Re: zfs initrd script fails when rootdelay boot option is set

[Richard Laager]

@svde-tech: Can you please test from this PPA:
https://launchpad.net/~rlaager/+archive/ubuntu/zfs

The init script is slightly different from my last iteration. I removed
one unrelated change. I also applied your fix, but stopped suppressing
stdout (since that's probably unnecessary). Besides making sure it works
with rootdelay, please watch the terminal and confirm you're not seeing
any spurious output from zpool commands.

If you do test from my PPA, please remove it from your APT sources when
you're done testing. I don't want some future experiment I upload to
break your system.

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

Title:
  zfs initrd script fails when rootdelay boot option is set

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  It looks like that, when booting off zfs (zfs holds /boot) with the
  rootdelay boot option set, the boot process fails in the initrd fase,
  asking to manually import the pool using zpool import -f -R / -N. I
  only had one system with that parameter set, which I seldom reboot.

  I did not find an upstream reference of this bug or behavior.

  The error is caused by the fact the pool is already imported: "zpool
  status" executed on the initramfs prompt will correctly list the pool
  and all devices online. To continue, one has to export the pool, re-
  import it and exit the initramfs prompt after which regular booting
  continues. Not exporting and reimporting it leaves the pool readonly
  leading to boot errors further down the road (systemd units failing).

  I noticed zfs_autoimport_disable is set to 1 in the initramfs
  environment, so looking at /usr/share/initramfs-tools/scripts/zfs this
  section might be the issue (zpool import succeeding, but $ZFS_HEALTH
  never returning with the correct status (I'm not a programmer but
  perhaps ZFS_HEALTH is a local variable in the zfs_test_import
  function)):

   delay=${ROOTDELAY:-0}

   if [ "$delay" -gt 0 ]
   then
    # Try to import the pool read-only.  If it does not import with
    # the ONLINE status, wait and try again.  The pool could be
    # DEGRADED because a drive is really missing, or it might just
    # be slow to be detected.
    zfs_test_import
    retry_nr=0
    while [ "$retry_nr" -lt "$delay" ] && [ "$ZFS_HEALTH" != "ONLINE" ]
    do
     [ "$quiet" != "y" ] && log_begin_msg "Retrying ZFS read-only import"
     /bin/sleep 1
     zfs_test_import
     retry_nr=$(( $retry_nr + 1 ))
     [ "$quiet" != "y" ] && log_end_msg
    done
    unset retry_nr
    unset ZFS_HEALTH
   fi
   unset delay

  
  Edit: to be clear: I removed the rootdelay parameter, regenerated the initrd, 
and was able to boot successfully afterwards.

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

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

[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers

[Phillip Susi]

It seems that there were other changes to grub that require the fix to
be adjusted to apply properly, and nobody has done so yet ( I've been
rather busy at work and with second child lately, but still hope to
update this soon ).

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

Title:
  Please use dpkg-triggers

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

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

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

[Kernel-packages] [Bug 1567558] Re: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac

[Richard Laager]

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

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

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

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

Title:
  ZFS is confused by user namespaces (uid/gid mapping) when used with
  acltype=posixac

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

Bug description:
  This report is copy/paste from the following upstream issue:
  https://github.com/zfsonlinux/zfs/issues/4177

  I was asked to file a matching Ubuntu bug for tracking.

  
  Hello,

  # First a quick introduction to the world of containers

  I'm the project leader for LXC and LXD, working on containers on
  Linux. We now extensively use the user namespaces to provide an extra
  layer of security in Linux containers.

  The user namespace allows one to map a range of uid and gid from the
  host or parent namespace into another range of uid and gid of a new
  namespace.

  Typically what's done is that 65536 uids and gids are set aside per
  non-system users on the host. Those users through a couple of setuid
  helpers (newuidmap and newgidmap) can then setup a uid and gid map for
  their processes. Their 65536 allocation is therefore mapped from
  uid/gid 0 to 65536 of the new namespace, providing a POSIX-compatible
  environment.

  That means that given a user on the host with uid and gid range 10
  through 165536, uid 100 in their container will be mapped to uid
  100100 outside of it.

  # The problem with ZFS

  When using ZFS with acltype=posixacl and an ACL entry on the host set
  for a uid (or gid) that's then mapped into the container, the
  container doesn't see the right mapped value when querying the acl
  from inside the namespace.

  # Example with zfs (broken)

  root@dakara:~# zfs create lxd/test -o mountpoint=/tmp/test
  root@dakara:~# zfs set acltype=posixacl lxd/test
  root@dakara:~# cd /tmp/test/
  root@dakara:/tmp/test# mkdir a
  root@dakara:/tmp/test# setfacl -m default:user:100100:rwX a
  root@dakara:/tmp/test# setfacl -m user:100100:rwX a
  root@dakara:/tmp/test# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536 
-- /bin/bash
  root@dakara:/tmp/test (in userns)# ls -lh
  total 512
  drwxrwxr-x+ 2 nobody nogroup 2 Jan  7 22:19 a

  root@dakara:/tmp/test (in userns)# getfacl -n a
  # file: a
  # owner: nobody
  # group: nogroup
  user::rwx
  user:4294967295:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:4294967295:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Example with ext4 (working)

  root@dakara:/tmp/test.ext4# mkdir a

  root@dakara:/tmp/test.ext4# setfacl -m default:user:100100:rwX a

  root@dakara:/tmp/test.ext4# setfacl -m user:100100:rwX a

  root@dakara:/tmp/test.ext4# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test.ext4# lxc-usernsexec -m u:0:10:65536 -m 
g:0:10:65536 -- /bin/bash
  root@dakara:/tmp/test.ext4 (in userns)# ls -lh
  total 4.0K
  drwxrwxr-x+ 2 nobody nogroup 4.0K Jan  7 22:22 a

  root@dakara:/tmp/test.ext4 (in userns)# getfacl -n a
  # file: a
  # owner: 65534
  # group: 65534
  user::rwx
  user:100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Environment

  This was noticed on Ubuntu 14.04 using the zfs stable PPA. I first
  found it in production environments first with file servers
  misbehaving due to the problem, then reproduced it on my development
  systems.

  The zfs version here is 0.6.5.3-1~trusty and I've seen this on 3.13,
  3.16, 3.19 and 4.2 kernels (not that it should matter, the dkms code
  was the same). zfs-dkms is at 2.53-zfs1.

  The lxc-usernsexec helper tool I'm using there comes from the LXC
  package in Ubuntu. It essentially causes a call to fork() followed by
  a call to unshare(CLONE_NEWUSER), then calls the newuidmap and
  newgidmap setuid helpers with the provided map so that the namespace
  can be configured properly.

  You could reproduce something similar using the simple unshare tool
  and manual writes to /proc/PID/{u,g}id_map

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

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

[Kernel-packages] [Bug 1577057] Re: zfs initrd script fails when rootdelay boot option is set

[Richard Laager]

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

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

Title:
  zfs initrd script fails when rootdelay boot option is set

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  It looks like that, when booting off zfs (zfs holds /boot) with the
  rootdelay boot option set, the boot process fails in the initrd fase,
  asking to manually import the pool using zpool import -f -R / -N. I
  only had one system with that parameter set, which I seldom reboot.

  I did not find an upstream reference of this bug or behavior.

  The error is caused by the fact the pool is already imported: "zpool
  status" executed on the initramfs prompt will correctly list the pool
  and all devices online. To continue, one has to export the pool, re-
  import it and exit the initramfs prompt after which regular booting
  continues. Not exporting and reimporting it leaves the pool readonly
  leading to boot errors further down the road (systemd units failing).

  I noticed zfs_autoimport_disable is set to 1 in the initramfs
  environment, so looking at /usr/share/initramfs-tools/scripts/zfs this
  section might be the issue (zpool import succeeding, but $ZFS_HEALTH
  never returning with the correct status (I'm not a programmer but
  perhaps ZFS_HEALTH is a local variable in the zfs_test_import
  function)):

   delay=${ROOTDELAY:-0}

   if [ "$delay" -gt 0 ]
   then
    # Try to import the pool read-only.  If it does not import with
    # the ONLINE status, wait and try again.  The pool could be
    # DEGRADED because a drive is really missing, or it might just
    # be slow to be detected.
    zfs_test_import
    retry_nr=0
    while [ "$retry_nr" -lt "$delay" ] && [ "$ZFS_HEALTH" != "ONLINE" ]
    do
     [ "$quiet" != "y" ] && log_begin_msg "Retrying ZFS read-only import"
     /bin/sleep 1
     zfs_test_import
     retry_nr=$(( $retry_nr + 1 ))
     [ "$quiet" != "y" ] && log_end_msg
    done
    unset retry_nr
    unset ZFS_HEALTH
   fi
   unset delay

  
  Edit: to be clear: I removed the rootdelay parameter, regenerated the initrd, 
and was able to boot successfully afterwards.

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

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

[Kernel-packages] [Bug 1567558] Re: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac

[Richard Laager]

This is fixed upstream:
https://github.com/zfsonlinux/zfs/commit/874bd959f4f15b3d4b007160ee7ad3f4111dd341

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

Title:
  ZFS is confused by user namespaces (uid/gid mapping) when used with
  acltype=posixac

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

Bug description:
  This report is copy/paste from the following upstream issue:
  https://github.com/zfsonlinux/zfs/issues/4177

  I was asked to file a matching Ubuntu bug for tracking.

  
  Hello,

  # First a quick introduction to the world of containers

  I'm the project leader for LXC and LXD, working on containers on
  Linux. We now extensively use the user namespaces to provide an extra
  layer of security in Linux containers.

  The user namespace allows one to map a range of uid and gid from the
  host or parent namespace into another range of uid and gid of a new
  namespace.

  Typically what's done is that 65536 uids and gids are set aside per
  non-system users on the host. Those users through a couple of setuid
  helpers (newuidmap and newgidmap) can then setup a uid and gid map for
  their processes. Their 65536 allocation is therefore mapped from
  uid/gid 0 to 65536 of the new namespace, providing a POSIX-compatible
  environment.

  That means that given a user on the host with uid and gid range 10
  through 165536, uid 100 in their container will be mapped to uid
  100100 outside of it.

  # The problem with ZFS

  When using ZFS with acltype=posixacl and an ACL entry on the host set
  for a uid (or gid) that's then mapped into the container, the
  container doesn't see the right mapped value when querying the acl
  from inside the namespace.

  # Example with zfs (broken)

  root@dakara:~# zfs create lxd/test -o mountpoint=/tmp/test
  root@dakara:~# zfs set acltype=posixacl lxd/test
  root@dakara:~# cd /tmp/test/
  root@dakara:/tmp/test# mkdir a
  root@dakara:/tmp/test# setfacl -m default:user:100100:rwX a
  root@dakara:/tmp/test# setfacl -m user:100100:rwX a
  root@dakara:/tmp/test# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536 
-- /bin/bash
  root@dakara:/tmp/test (in userns)# ls -lh
  total 512
  drwxrwxr-x+ 2 nobody nogroup 2 Jan  7 22:19 a

  root@dakara:/tmp/test (in userns)# getfacl -n a
  # file: a
  # owner: nobody
  # group: nogroup
  user::rwx
  user:4294967295:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:4294967295:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Example with ext4 (working)

  root@dakara:/tmp/test.ext4# mkdir a

  root@dakara:/tmp/test.ext4# setfacl -m default:user:100100:rwX a

  root@dakara:/tmp/test.ext4# setfacl -m user:100100:rwX a

  root@dakara:/tmp/test.ext4# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test.ext4# lxc-usernsexec -m u:0:10:65536 -m 
g:0:10:65536 -- /bin/bash
  root@dakara:/tmp/test.ext4 (in userns)# ls -lh
  total 4.0K
  drwxrwxr-x+ 2 nobody nogroup 4.0K Jan  7 22:22 a

  root@dakara:/tmp/test.ext4 (in userns)# getfacl -n a
  # file: a
  # owner: 65534
  # group: 65534
  user::rwx
  user:100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Environment

  This was noticed on Ubuntu 14.04 using the zfs stable PPA. I first
  found it in production environments first with file servers
  misbehaving due to the problem, then reproduced it on my development
  systems.

  The zfs version here is 0.6.5.3-1~trusty and I've seen this on 3.13,
  3.16, 3.19 and 4.2 kernels (not that it should matter, the dkms code
  was the same). zfs-dkms is at 2.53-zfs1.

  The lxc-usernsexec helper tool I'm using there comes from the LXC
  package in Ubuntu. It essentially causes a call to fork() followed by
  a call to unshare(CLONE_NEWUSER), then calls the newuidmap and
  newgidmap setuid helpers with the provided map so that the namespace
  can be configured properly.

  You could reproduce something similar using the simple unshare tool
  and manual writes to /proc/PID/{u,g}id_map

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

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

[Kernel-packages] [Bug 1577971] Re: zfs module is not loading after a restart

[Richard Laager]

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

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

Title:
  zfs module is not loading after a restart

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  When shutting down a nova compute node with the lxd subordinate charm
  and zfs as the backend block storage, upon restart, the zfs module
  does not load, erroring out the lxd service. Connecting into the
  node(s) and executing a modprobe zfs loads the module and subsequently
  the lxd service starts after a few minutes.

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

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

[Kernel-packages] [Bug 1574612] Re: Random hangs

[Christopher M. Penalver]

Serrie, the next step is to fully reverse commit bisect from kernel 4.2
to 4.6-rc6 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?

Please note, finding adjacent kernel versions is not fully commit
bisecting.

After the fix commit (not kernel version) has been identified, then
please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags added: needs-reverse-bisect

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

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

Title:
  Random hangs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System hangs randomly. This mostly occurs anywhere between 15 minutes
  and a few hours after boot. Couldn't figure out the trigger. Happened
  while viewing YouTube, using Spotify switching to Eclipse etc. SSH
  still works, so I can get to the machine if the lockup occurs. That's
  how I submitted the bug. All screens freeze though, while audio keeps
  on working (like music from Spotify or sound from a YouTube video).
  The only thing that seems to keep working UI-wise is the mouse
  pointer.

  Had memtest running for half an hour without problems.

  The issue occurs multiple times a day. Issue doesn't seem to be
  triggered if I remove linux-image-4.2.0-35-generic and go back to
  linux-image-4.2.0-16-generic. Did use the linux-image-4.2.0-16-generic
  kernel for a few days without issues.

  The kern.log contains some stacktraces with the method being
  'schedule'. This is around the time the hang occurs.

  See extra debug information for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  serrie 1815 F pulseaudio
   /dev/snd/pcmC0D0c:   serrie 1815 F...m pulseaudio
   /dev/snd/controlC0:  serrie 1815 F pulseaudio
  Date: Mon Apr 25 13:56:48 2016
  InstallationDate: Installed on 2016-04-12 (13 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   docker0   no wireless extensions.
   
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=c15a8aa0-fb21-495c-bbc6-ea4f2018dc1f ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.149.3
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-04-22 (3 days ago)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0505
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M-A D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0505:bd01/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-AD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1553694] Re: Lenovo Y700-17ISK: Bluetooth issues

[Christopher M. Penalver]

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

Please feel free to subscribe me to it.

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

** Tags removed: cdcn30ww
** Tags added: bios-outdated-cdcn35ww

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

Title:
  Lenovo Y700-17ISK: Bluetooth issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing and updating Xenial, dmesg notes:
  [2.253211] Bluetooth: hci0: Failed to send firmware data (-38)
  [4.250058] Bluetooth: hci0 command 0xfc05 tx timeout
  [9.135505] Bluetooth: hci0: Reading Intel version information failed (-19)
  [   10.926411] Bluetooth: hci0: Setting Intel event mask failed (-16)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:31:12 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1553694] Re: Lenovo Y700-17ISK: Bluetooth issues

[Christopher M. Penalver]

aljosa, as per http://support.lenovo.com/us/en/products/Laptops-and-
netbooks/IdeaPad-Y-Series-
laptops/y700-17isk?tabName=Downloads&linkTrack=Mast:SubNav:Support:Drivers%20and%20Software|Drivers%20and%20Software&beta=false
an update to your computer's buggy, insecure, and outdated BIOS is
available (CDCN35WW). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

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

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

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

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed.

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

Thank you for your understanding.

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

Title:
  Lenovo Y700-17ISK: Bluetooth issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing and updating Xenial, dmesg notes:
  [2.253211] Bluetooth: hci0: Failed to send firmware data (-38)
  [4.250058] Bluetooth: hci0 command 0xfc05 tx timeout
  [9.135505] Bluetooth: hci0: Reading Intel version information failed (-19)
  [   10.926411] Bluetooth: hci0: Setting Intel event mask failed (-16)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:31:12 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

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

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

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

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

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

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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-snapdragon 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:
  In

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- usbnet: memory corruption triggered by invalid USB descriptor
+ Double free vulnerability in drivers/net/usb/cdc_ncm.c in the Linux
+ kernel before 4.5 allows physically proximate attackers to cause a
+ denial of service (system crash) or possibly have unspecified other
+ impact by inserting a USB device with an invalid USB descriptor.
  
  Break-Fix: - 4d06dd537f95683aba3651098ae288b7cbff8274
  Break-Fix: - 1666984c8625b3db19a9abc298931d35ab7bc64b

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1578493] Re: CVE-2016-4482

[Steve Beattie]

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

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

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

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

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

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

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

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

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

Title:
  CVE-2016-4482

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

[Kernel-packages] [Bug 1578496] Re: CVE-2016-4485

[Steve Beattie]

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

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

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

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

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

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

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

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

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

Title:
  CVE-2016-4485

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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-snapdragon 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:
  Inva

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- pipe: limit the per-user amount of pages allocated in pipes
+ fs/pipe.c in the Linux kernel before 4.5 does not limit the amount of
+ unread data in pipes, which allows local users to cause a denial of
+ service (memory consumption) by creating many pipes with non-default
+ sizes.
  
  Break-Fix: - 759c01142a5d0f364a462346168a56de28a80f52

-- 
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-snapdragon 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 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-snapdragon 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-snapdragon 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:
  N

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- crash on invalid USB device descriptors (ims-pcu driver)
+ The ims_pcu_parse_cdc_data function in drivers/input/misc/ims-pcu.c in
+ the Linux kernel before 4.5.1 allows physically proximate attackers to
+ cause a denial of service (system crash) via a USB device without both a
+ master and a slave interface.
  
  Break-Fix: - a0ad220c96692eda76b2e3fd7279f3dcd1d8a8ff

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

[Kernel-packages] [Bug 990129] Re: Suspend/Resume hangs and fails - Ubuntu 12.04LTS

[Christopher M. Penalver]

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

Please feel free to subscribe me to it.

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

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

Title:
  Suspend/Resume hangs and fails - Ubuntu 12.04LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend/Resume hangs on a black screen and a hard reset is needed to
  start system.

  System76 laptop
  Ubuntu 12.04LTS 64bit

  Hardware Profile:
  pst007x@pst007x-Serval-Professional:~$ lspci
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation Device 1211 (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio 
Controller (rev a1)
  02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 04)
  03:00.0 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express 
Gigabit Ethernet Controller (rev 05)
  03:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller 
(rev 90)
  03:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host 
Controller (rev 90)
  03:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 
90)
  04:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 (rev 
34)
  05:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host 
Controller (rev 30)
  pst007x@pst007x-Serval-Professional:~$

  Linux pst007x-Serval-Professional 3.2.0-24-generic #37-Ubuntu SMP Wed
  Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

  
  May have something to do with the gnome-power-manager and pm-utils

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

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

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

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

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

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

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

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

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

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

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

** Description changed:

- Linux digi_acceleport Nullpointer Dereference
+ The digi_port_init function in drivers/usb/serial/digi_acceleport.c in
+ the Linux kernel before 4.5.1 allows physically proximate attackers to
+ cause a denial of service (NULL pointer dereference and system crash)
+ via a crafted endpoints value in a USB device descriptor.
  
  Break-Fix: - 5a07975ad0a36708c6b0a5b9fea1ff811d0b0c1f

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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:
  Ne

[Kernel-packages] [Bug 1578497] Re: CVE-2016-4486

[Steve Beattie]

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

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

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

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

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

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

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

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

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

Title:
  CVE-2016-4486

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

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- USB: visor: fix null-deref at probe
+ The treo_attach function in drivers/usb/serial/visor.c in the Linux
+ kernel before 4.5 allows physically proximate attackers to cause a
+ denial of service (NULL pointer dereference and system crash) or
+ possibly have unspecified other impact by inserting a USB device that
+ lacks a (1) bulk-in or (2) interrupt-in endpoint.
  
  Break-Fix: - cac9b50b0d75a1d50d6c056ff65c005f3224c8e0

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- cypress_m8 USB driver crash
+ drivers/usb/serial/cypress_m8.c in the Linux kernel before 4.5.1 allows
+ physically proximate attackers to cause a denial of service (NULL
+ pointer dereference and system crash) via a USB device without both an
+ interrupt-in and an interrupt-out endpoint descriptor, related to the
+ cypress_generic_port_probe and cypress_open functions.
  
  Break-Fix: - c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754

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

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- It was discovered that Linux incorrectly accounted the number of in-
- flight fds over a unix domain socket to the original opener of the file-
- descriptor. This allows another process to arbitrary deplete the
- original file-openers resource limit for the maximum of open files.
- Instead the sending processes and its struct cred should be credited.
+ The Linux kernel before 4.5 allows local users to bypass file-descriptor
+ limits and cause a denial of service (memory consumption) by leveraging
+ incorrect tracking of descriptor ownership and sending each descriptor
+ over a UNIX socket before closing it. NOTE: this vulnerability exists
+ because of an incorrect fix for CVE-2013-4312.
  
  Break-Fix: 712f4aad406bb1ed67f3f98d04c044191f0ff593
  415e3d3e90ce9e18727e8843ae343eda5a58fad6

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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:
  Ne

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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-keystone source package in Vivid:
  Invalid
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:
  Invalid
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
Stat

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Kernel crashes on invalid USB device descriptors (mct_u232 driver)
+ The mct_u232_msr_to_state function in drivers/usb/serial/mct_u232.c in
+ the Linux kernel before 4.5.1 allows physically proximate attackers to
+ cause a denial of service (NULL pointer dereference and system crash)
+ via a crafted USB device without two interrupt-in endpoint descriptors.
  
  Break-Fix: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
  4e9a0b05257f29cf4b75f3209243ed71614d062e

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

** Description changed:

- [AUFS Xattr Setgid Privilege Escalation]
+ The aufs module for the Linux kernel 3.x and 4.x does not properly
+ maintain POSIX ACL xattr data, which allows local users to gain
+ privileges by leveraging a group-writable setgid directory.

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source pa

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- [Unlimiting the stack not longer disables ASLR]
+ The arch_pick_mmap_layout function in arch/x86/mm/mmap.c in the Linux
+ kernel through 4.5.2 does not properly randomize the legacy base
+ address, which makes it easier for local users to defeat the intended
+ restrictions on the ADDR_NO_RANDOMIZE flag, and bypass the ASLR
+ protection mechanism for a setuid or setgid program, by disabling stack-
+ consumption resource limits.
  
  Break-Fix: - 8b8addf891de8a00e4d39fc32f93f7c5eb8feceb

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Local denial of service to network
+ The IPv4 implementation in the Linux kernel before 4.5.2 mishandles
+ destruction of device objects, which allows guest OS users to cause a
+ denial of service (host OS networking outage) by arranging for a large
+ number of IP addresses.
  
  Break-Fix: - fbd40ea0180a2d328c5adc61414dc8bab9335ce2

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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 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 Released
Status in linux-snapdragon source package in Wily:
  Invalid
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source packa

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

[Steve Beattie]

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

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

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

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

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

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

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

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

** Description changed:

- Kernel crashes on invalid USB device descriptors (wacom driver)
+ The wacom_probe function in drivers/input/tablet/wacom_sys.c in the
+ Linux kernel before 3.17 allows physically proximate attackers to cause
+ a denial of service (NULL pointer dereference and system crash) via a
+ crafted endpoints value in a USB device descriptor.

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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-snapdragon source package i

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Kernel crashes on invalid USB device descriptors (cdc_acm driver)
+ The acm_probe function in drivers/usb/class/cdc-acm.c in the Linux
+ kernel before 4.5.1 allows physically proximate attackers to cause a
+ denial of service (NULL pointer dereference and system crash) via a USB
+ device without both a control and a data endpoint descriptor.
  
  Break-Fix: - 8835ba4a39cf53f705417b3b3a94eb067673f2c9

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

[Kernel-packages] [Bug 1542716] Re: [Fujitsu LIFEBOOK S935] Touchpad doesn't work

[Christopher M. Penalver]

mauribera, could you also please post the following:
cat /proc/bus/input/devices

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

Title:
  [Fujitsu LIFEBOOK S935] Touchpad doesn't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad is recognized, e.g., xinput but does not respond at all.
  It worked under the original win7 installation.

  WORKAROUND: Use kernel boot parameters:
  i8042.nomux=1 i8042.reset

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.19
  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
  Date: Sat Feb  6 21:36:22 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:1896]
  InstallationDate: Installed on 2016-01-30 (7 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: FUJITSU LIFEBOOK S935
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic.efi.signed 
root=UUID=b2e8253b-e0f4-4300-b611-ab33856023ba ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2015
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.11
  dmi.board.name: FJNB284
  dmi.board.vendor: FUJITSU
  dmi.board.version: C3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: LIFEBOOK S935
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.11:bd06/02/2015:svnFUJITSU:pnLIFEBOOKS935:pvr1060173:rvnFUJITSU:rnFJNB284:rvrC3:cvnFUJITSU:ct10:cvrLIFEBOOKS935:
  dmi.product.name: LIFEBOOK S935
  dmi.product.version: 1060173
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb  6 15:28:02 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5138
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3~trusty1

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

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

[Kernel-packages] [Bug 1572901] Re: i915: No HDMI output with 4.4

[Bug Watch Updater]

Launchpad has imported 13 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=92685.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-10-27T01:43:10+00:00 Eric Biggers wrote:

Created attachment 119210
dmesg.gz

Running Linux 4.3-rc7 on a laptop with Intel Skylake integrated
graphics, I encountered warnings in the kernel log and a several second
hang during boot. Furthermore, an external monitor attached to the HDMI
input did not work.  The problems occur every boot.  The full dmesg
output with drm.debug=14 is attached; some highlights are shown below:

[1.401196] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout 
(has irq: 1)!
[1.414508] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout 
(has irq: 1)!
[1.427851] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout 
(has irq: 1)!
[1.427853] [drm:intel_dp_aux_ch] *ERROR* dp_aux_ch not done status 
0xad40001f
[1.447865] [ cut here ]

[1.447867] WARNING: CPU: 1 PID: 6 at drivers/gpu/drm/i915/intel_dp.c:854 
intel_dp_aux_ch+0x10f/0x6a0()
[1.447867] dp_aux_ch not started status 0xad40001f
...
[8.043643] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
...
[   32.571277] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
...
[   32.608835] i915 :00:02.0: HDMI-A-1: EDID block 0 invalid.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/0


On 2015-10-28T14:30:48+00:00 Timo Aaltonen wrote:

seeing same on SKL21-SDS, with the added fun that eDP stays blank until
drm-intel-next-2015-09-28-merged.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/1


On 2015-10-28T14:35:55+00:00 Timo Aaltonen wrote:

..until the first DPMS cycle, returning from it makes things work

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/2


On 2015-11-13T14:24:56+00:00 Ander Conselvan de Oliveira wrote:

Created attachment 119641
Fix SKL DP AUX CH clock divider

Could you give this patch a try?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/3


On 2015-11-13T14:35:08+00:00 Ander Conselvan de Oliveira wrote:

Created attachment 119642
Fix SKL DP AUX CH clock divider

There was a typo on the previous patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/4


On 2015-11-14T01:21:35+00:00 Eric Biggers wrote:

I tested Linux 4.3 with your patch applied, but it did not solve the
problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/5


On 2015-11-23T03:20:49+00:00 Eric Biggers wrote:

Update: with Linux 4.4-rc2, the "dp_aux_ch not started" warning is gone,
and there is no longer a several second hang on boot or when changing
the screen resolution.

However, the HDMI output continues to be broken, and the log messages
about the EDID checksum being invalid still appear.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/6


On 2015-11-25T05:51:20+00:00 Eric Biggers wrote:

I updated the bug title to reflect the fact that the HDMI output not
working (because of the invalid EDID checksum) is now the only problem
for me.  So there must have been two separate problems originally, one
of which was solved by the 4.4 merges.

I tried hacking the i915 driver code in a few different ways but none of
them solved the problem:

- always setting force_bit=1 on the 'struct intel_gmbus'
- changing the drm_i915_private hotplug_work to a delayed_work and scheduling 
it with delay 400 ms
- increasing the number of retries in drm_do_get_edid() from 4 to 32
- increasing the number of retries of the "live status" check in 
intel_hdmi_detect() from 3 to 30

Also, I verified that the same monitor and VGA->HDMI adapter works on a
Raspberry Pi.  So that leaves the Skylake hardware and/or the i915
driver as the source of the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572901/comments/7


On 2015-11-25T08:11:39+00:00 Jani-nikula wrote:

Please add drm.debug=14 module parameter, and

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

[Steve Beattie]

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

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

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

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

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

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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 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:
  New
Status in linux-snapdragon source package in Wily:
  Invalid
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source pack

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- A slave timer instance might be still accessible in a racy way while
- operating the master instance as it lacks of locking. Since the master
- operation is mostly protected with timer->lock, we should cope with it
- while changing the slave instance, too.
+ sound/core/timer.c in the Linux kernel before 4.4.1 employs a locking
+ approach that does not consider slave timer instances, which allows
+ local users to cause a denial of service (race condition, use-after-
+ free, and system crash) via a crafted ioctl call.
  
  Break-Fix: - b5a663aa426f4884c71cd8580adae73f33570f0d

-- 
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-snapdragon 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 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-snapdragon 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-snapdragon 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 1549189] Re: CVE-2016-2546

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- ALSA timer ioctls have an open race and this may lead to a use-after-
- free of timer instance object.
+ sound/core/timer.c in the Linux kernel before 4.4.1 uses an incorrect
+ type of mutex, which allows local users to cause a denial of service
+ (race condition, use-after-free, and system crash) via a crafted ioctl
+ call.
  
  Break-Fix: - af368027a49a751d6ff4ee9e3f9961f35bb4fede

-- 
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-snapdragon 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 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-snapdragon 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-snapdragon 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:
  N

[Kernel-packages] [Bug 1542716] Re: [Fujitsu LIFEBOOK S935] Touchpad doesn't work

[Christopher M. Penalver]

** Description changed:

- the touchpad is recognized, e.g., xinput but does not respond at all. It 
worked under the original win7 installaion
- thanks for your help
+ The touchpad is recognized, e.g., xinput but does not respond at all. It
+ worked under the original win7 installation.
+ 
+ WORKAROUND: Use kernel boot parameters:
+ i8042.nomux=1 i8042.reset
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.19
  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
  Date: Sat Feb  6 21:36:22 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
-Subsystem: Fujitsu Limited. Device [10cf:1896]
+  Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
+    Subsystem: Fujitsu Limited. Device [10cf:1896]
  InstallationDate: Installed on 2016-01-30 (7 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: FUJITSU LIFEBOOK S935
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic.efi.signed 
root=UUID=b2e8253b-e0f4-4300-b611-ab33856023ba ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2015
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.11
  dmi.board.name: FJNB284
  dmi.board.vendor: FUJITSU
  dmi.board.version: C3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: LIFEBOOK S935
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.11:bd06/02/2015:svnFUJITSU:pnLIFEBOOKS935:pvr1060173:rvnFUJITSU:rnFJNB284:rvrC3:cvnFUJITSU:ct10:cvrLIFEBOOKS935:
  dmi.product.name: LIFEBOOK S935
  dmi.product.version: 1060173
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb  6 15:28:02 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5138 
-  vendor SHP
+  product id5138
+  vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3~trusty1

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

Title:
  [Fujitsu LIFEBOOK S935] Touchpad doesn't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad is recognized, e.g., xinput but does not respond at all.
  It worked under the original win7 installation.

  WORKAROUND: Use kernel boot parameters:
  i8042.nomux=1 i8042.reset

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.19
  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
  Date: Sat Feb  6 21:36:22 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:1896]
  InstallationDate: Installed on 2016-01-30 (7 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: FUJITSU LIFEBOOK S935
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic.efi.signed 
root=UUID=b2e8253b-e0f4-4300-b611-ab33856023ba ro quiet splash nomdmonddf 
nomdmonisw

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- Some linked lists (active_list and ack_list) of slave instances aren't
- unlinked immediately at stopping or closing, and this may lead to
- unexpected accesses.
+ sound/core/timer.c in the Linux kernel before 4.4.1 retains certain
+ linked lists after a close or stop action, which allows local users to
+ cause a denial of service (system crash) via a crafted ioctl call,
+ related to the (1) snd_timer_close and (2) _snd_timer_stop functions.
  
  Break-Fix: - b5a663aa426f4884c71cd8580adae73f33570f0d

-- 
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-snapdragon 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 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-snapdragon 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-snapdragon 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 1549200] Re: CVE-2016-2549

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- hrtimer_cancel() waits for the completion from the callback, thus it
- must not be called inside the callback itself. This was already a
- problem in the past with ALSA hrtimer driver, and the early commit
- [fcfdebe70759: ALSA: hrtimer - Fix lock-up] tried to address it.
- However, the previous fix is still insufficient: it may still cause a
- lockup when the ALSA timer instance reprograms itself in its callback.
- Then it invokes the start function even in snd_timer_interrupt() that is
- called in hrtimer callback itself, results in a CPU stall. This is no
- hypothetical problem but actually triggered by syzkaller fuzzer.
+ sound/core/hrtimer.c in the Linux kernel before 4.4.1 does not prevent
+ recursive callback access, which allows local users to cause a denial of
+ service (deadlock) via a crafted ioctl call. However, the previous fix
+ is still insufficient: it may still cause a lockup when the ALSA timer
+ instance reprograms itself in its callback. Then it invokes the start
+ function even in snd_timer_interrupt() that is called in hrtimer
+ callback itself, results in a CPU stall. This is no hypothetical problem
+ but actually triggered by syzkaller fuzzer.
  
  Break-Fix: - 2ba1fe7a06d3624f9a7586d672b55f08f7c670f3

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

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- snd_seq_ioctl_remove_events() calls snd_seq_fifo_clear() unconditionally
- even if there is no FIFO assigned, and this leads to an Oops due to NULL
- dereference.
+ The snd_seq_ioctl_remove_events function in
+ sound/core/seq/seq_clientmgr.c in the Linux kernel before 4.4.1 does not
+ verify FIFO assignment before proceeding with FIFO clearing, which
+ allows local users to cause a denial of service (NULL pointer
+ dereference and OOPS) via a crafted ioctl call.
  
  Break-Fix: - 030e2c78d3a91dd0d27fef37e91950dde333eba1

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

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- Double-free in snd-usbmidi-lib triggered by invalid USB descriptor
+ Double free vulnerability in the snd_usbmidi_create function in
+ sound/usb/midi.c in the Linux kernel before 4.5 allows physically
+ proximate attackers to cause a denial of service (panic) or possibly
+ have unspecified other impact via vectors involving an invalid USB
+ descriptor.
  
  Break-Fix: - 07d86ca93db7e5cdf4743564d98292042ec21af7

-- 
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-snapdragon 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-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-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package i

[Kernel-packages] [Bug 1549184] Re: CVE-2016-2545

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- ALSA timer instance object has a couple of linked lists and they are
- unlinked unconditionally at snd_timer_stop(). Meanwhile
- snd_timer_interrupt() unlinks it, but it calls list_del() which leaves
- the element list itself unchanged. This ends up with unlinking twice,
- and it was caught by syzkaller fuzzer.
+ The snd_timer_interrupt function in sound/core/timer.c in the Linux
+ kernel before 4.4.1 does not properly maintain a certain linked list,
+ which allows local users to cause a denial of service (race condition
+ and system crash) via a crafted ioctl call.
  
  Break-Fix: - ee8413b01045c74340aa13ad5bdf905de32be736

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

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- ALSA sequencer code has an open race between the timer setup ioctl and
- the close of the client. This was triggered by syzkaller fuzzer, and a
- use-after-free was caught there as a result.
+ Race condition in the queue_delete function in
+ sound/core/seq/seq_queue.c in the Linux kernel before 4.4.1 allows local
+ users to cause a denial of service (use-after-free and system crash) by
+ making an ioctl call at a certain time.
  
  Break-Fix: - 3567eb6af614dac436c4b16a8d426f9faed639b3

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

[Kernel-packages] [Bug 1561411] Re: CVE-2016-2186

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Kernel panic on invalid USB device descriptor (powermate driver)
+ The powermate_probe function in drivers/input/misc/powermate.c in the
+ Linux kernel before 4.5.1 allows physically proximate attackers to cause
+ a denial of service (NULL pointer dereference and system crash) via a
+ crafted endpoints value in a USB device descriptor.
  
  Break-Fix: - 9c6ba456711687b794dcf285856fc14e2c76074f

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

[Kernel-packages] [Bug 1546173] Re: CVE-2016-2383

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- Incorrect branch fixups for eBPF allow arbitrary read
+ The adjust_branches function in kernel/bpf/verifier.c in the Linux
+ kernel before 4.5 does not consider the delta in the backward-jump case,
+ which allows local users to obtain sensitive information from kernel
+ memory by creating a packet filter and then loading crafted BPF
+ instructions.
  
  Break-Fix: 9bac3d6d548e5cc925570b263f35b70a00a00ffd
  a1b14d27ed0965838350f1377ff97c93ee383492

-- 
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-snapdragon 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-snapdragon 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 linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  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 Com

[Kernel-packages] [Bug 1546162] Re: CVE-2016-2085

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- Timing side-channel in EVM
+ The evm_verify_hmac function in security/integrity/evm/evm_main.c in the
+ Linux kernel before 4.5 does not properly copy data, which makes it
+ easier for local users to forge MAC values via a timing side-channel
+ attack.
  
  Break-Fix: - 613317bd212c585c20796c10afe5daaa95d4b0a1

-- 
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-snapdragon package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status

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

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Kernel panic on invalid USB device descriptor (ati_remote2 driver)
+ The ati_remote2_probe function in drivers/input/misc/ati_remote2.c in
+ the Linux kernel before 4.5.1 allows physically proximate attackers to
+ cause a denial of service (NULL pointer dereference and system crash)
+ via a crafted endpoints value in a USB device descriptor.
  
  Break-Fix: - 950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d

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

[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Kernel panic on invalid USB device descriptor (snd_usb_audio driver)
+ The create_fixed_stream_quirk function in sound/usb/quirks.c in the snd-
+ usb-audio driver in the Linux kernel before 4.5.1 allows physically
+ proximate attackers to cause a denial of service (NULL pointer
+ dereference or double free, and system crash) via a crafted endpoints
+ value in a USB device descriptor.
  
  Break-Fix: - 0f886ca12765d20124bd06291c82951fd49a33be
  Break-Fix: - 447d6275f0c21f6cc97a88b3a0c601436a4cdf2a

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

[Kernel-packages] [Bug 1556141] Re: s390/mm: four page table levels vs. fork

[Steve Beattie]

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

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

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

Title:
  s390/mm: four page table levels vs. fork

Status in linux package in Ubuntu:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  New
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-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:
  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-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  Invalid
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:
  Invalid
Status in linux-manta source package in Wily:
  Invalid
Status in linux-raspi2 source package in Wily:
  Invalid
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package in Xenial:
  Invalid
Status in linux-goldfish source package in Xenial:
  Invalid
Status in linux-lts-quantal source package in Xenial:
  Invalid
Status in linux-lts-raring source package in Xenial:
  Invalid
Status in linux-lts-saucy source package in Xenial:
  Invalid
Status in linux-lts-trusty source package in Xenial:
  Invalid
Status in linux-lts-utopic source package in Xenial:
  Invalid
Status in linux-lts-vivid source package in Xenial:
  Invalid
Status in linux-lts-wily source package in Xenial:
  Invalid
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux-mako source package in Xenial:
  Invalid
Status in linux-manta source package in Xenial:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Invalid
Status in linux-ti-omap4 source package in Xenial:
  Invalid

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-03-11 
08:30:57 ==
  Please backport:

  http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h
  =for-linus&id=3446c13b268af86391d06611327006b059b8bab1

  s390/mm: four page table levels vs. fork
  The fork of a process with four page table levels is broken since
  git commit 6252d702c5311ce9 "[S390] dynamic page tables."

  All new mm contexts are created with three page table levels and
  an asce limit of 4TB. If the parent has four levels dup_mmap will
  add vmas to the new context which are outside of the asce limit.
  The subsequent call to copy_page_range will walk the three level
  page table structure of the new process with non-zero pgd and pud
  indexes. T

[Kernel-packages] [Bug 1561403] Re: CVE-2016-2117

[Steve Beattie]

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

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

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

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

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

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

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

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

** Description changed:

- memory disclosure to ethernet due to unchecked scatter/gather IO
+ The atl2_probe function in drivers/net/ethernet/atheros/atlx/atl2.c in
+ the Linux kernel through 4.5.2 incorrectly enables scatter/gather I/O,
+ which allows remote attackers to obtain sensitive information from
+ kernel memory by reading packet data.
  
  Break-Fix: ec5f061564238892005257c83565a0b58ec79295
  f43bfaeddc79effbf3d0fcb53ca477cca66f3db8

-- 
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-snapdragon 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:
  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-snapdragon 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-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:
  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-snapdragon 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 sourc

[Kernel-packages] [Bug 1561414] Re: CVE-2016-2188

[Steve Beattie]

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

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

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

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

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

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

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

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

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

** Description changed:

- Kernel panic on invalid USB device descriptor (iowarrior driver)
+ The iowarrior_probe function in drivers/usb/misc/iowarrior.c in the
+ Linux kernel before 4.5.1 allows physically proximate attackers to cause
+ a denial of service (NULL pointer dereference and system crash) via a
+ crafted endpoints value in a USB device descriptor.
  
  Break-Fix: - 4ec0ef3a82125efc36173062a50624550a900ae0

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

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

[Steve Beattie]

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

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

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

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

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

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

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

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

** Description changed:

- Kernel panic on invalid USB device descriptor (gtco driver)
+ The gtco_probe function in drivers/input/tablet/gtco.c in the Linux
+ kernel through 4.5.2 allows physically proximate attackers to cause a
+ denial of service (NULL pointer dereference and system crash) via a
+ crafted endpoints value in a USB device descriptor.
  
  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-snapdragon 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-snapdragon 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:
  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-snapdragon 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 Vivi

[Kernel-packages] [Bug 1535150] Re: overlayfs over fuse should refuse copy_up of files if uid/gid not mapped

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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 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-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivi

[Kernel-packages] [Bug 1534961] Re: insecure overlayfs xattrs handling in copy_up

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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 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-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in 

[Kernel-packages] [Bug 1538428] Re: CVE-2016-2053

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- [Denial of service with specially crafted key file]
+ The asn1_ber_decoder function in lib/asn1_decoder.c in the Linux kernel
+ before 4.3 allows attackers to cause a denial of service (panic) via an
+ ASN.1 BER file that lacks a public key, leading to mishandling by the
+ public_key_verify_signature function in
+ crypto/asymmetric_keys/public_key.c.
  
  Break-Fix: 3d167d68e3805ee45ed2e8412fc03ed919c54c24
  0d62e9dd6da45bbf0f33a8617afc5fe774c8f45f

-- 
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-snapdragon 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-snapdragon 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 package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial

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

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- [x86 Linux TLB flush bug]
+ Race condition in arch/x86/mm/tlb.c in the Linux kernel before 4.4.1
+ allows local users to gain privileges by triggering access to a paging
+ structure by a different CPU.
  
  Break-Fix: - 71b3c126e61177eb693423f2e18a1914205b165e
  Break-Fix: - 4eaffdd5a5fe6ff9f95e1ab4de1ac904d5e0fa8b

-- 
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-snapdragon 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-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-snapdragon 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 linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in

[Kernel-packages] [Bug 1538449] Re: CVE-2016-2070

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

** Description changed:

- [division by zero in TCP code]
+ The tcp_cwnd_reduction function in net/ipv4/tcp_input.c in the Linux
+ kernel before 4.3.5 allows remote attackers to cause a denial of service
+ (divide-by-zero error and system crash) via crafted TCP traffic.
  
  Break-Fix: 3759824da87b30ce7a35b4873b62b0ba38905ef5
  8b8a321ff72c785ed5e8b4cf6eda20b35d427390

-- 
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-snapdragon 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-snapdragon 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 linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  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:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta sourc

[Kernel-packages] [Bug 1561399] Re: CVE-2016-0823

[Steve Beattie]

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

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

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

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

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

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

** Changed in: linux-snapdragon (Ubuntu Yakkety)
   Status: New => Invalid

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

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

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

-- 
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-snapdragon 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-snapdragon 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-snapdragon 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-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in