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

[bugproxy]

--- Comment From naveed...@in.ibm.com 2016-07-15 01:39 EDT---
(In reply to comment #96)
> I was able to reproduce with the ones in the path pointed before, but it
> uses an old 4.4.0-21.37 kernel, is it possible to get netboot files with the
> updated kernel mentioned?

(In reply to comment #100)
> (In reply to comment #99)
> > This issue is still reproducible with latest netboot images.
>
> Naveed, can you mention the exact version of netboot images used & their
> location?
>
> Thanks!

We still see the kernel version as 4.4.0-21.37, do we have latest netboot image 
?
We see this issue even on 14.04.5 which uses same kernel.

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

Title:
  console hung during Ubuntu 16.04 netboot install 4.4.0-12-generic
  [soft lockup]

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  FYI and reference only at this time.

  Details:
  ---Problem Description---
  IPMI Console gets hung for 15 to 30 mins, can not traverse when trying to 
install 
  latest copy of Ubuntu 16.04 on Habanero from 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  which is 4.4.0-12-generic 
   [   36.803240] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[swapper/2:0]
   
  ---uname output---
  4.4.0-12-generic 
   
  ---Additional Hardware Info---
  TN71-BP012  

   
  Machine Type = TN71-BP012  
   
  ---System Hang---
   we have to wait for 15 to 30 mins to regain the console access.

   
  ---Steps to Reproduce---
  use IPMI console for  petitboot on habanero, configure IP to a network 
device, make sure you have internet outbound BSO authenticated. 
  on petit shell run following commands 
  cd /tmp;
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
 ;
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
 ;
  kexec -l /tmp/vmlinux  -i /tmp/initrd.gz  ;
  kexec -e ;

   
  Stack trace output:
   [   36.803240] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[swapper/2:0]
  [   36.803425] Modules linked in: hid_generic(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) ttm
  ) usb_storage(E)
  [   36.803436] CPU: 2 PID: 0 Comm: swapper/2 Tainted: GE   
4.4.0-12-generic #28-Ubuntu
  [   36.803438] task: c03c8fe8e7b0 ti: c03c9753 task.ti: 
c03c9753
  [   36.803440] NIP: c0010a24 LR: c0010a24 CTR: 
c060c2f0
  [   36.803442] REGS: c03c97533510 TRAP: 0901   Tainted: GE
(4.4.0-12-generic)
  [   36.803443] MSR: 90019033   CR: 28002824  
XER: 
  [   36.803448] CFAR: c060c330 SOFTE: 1 
  [   36.803448] GPR00: c00db8b4 c03c97533790 c15a3b00 
0900 
  [   36.803448] GPR04: c03c8fef6e00 0001  
03ff 
  [   36.803448] GPR08:  c03ffb064605 0001 
0004 
  [   36.803448] GPR12: c060c2f0 cfb41300 
  [   36.803460] NIP [c0010a24] arch_local_irq_restore+0x74/0x90
  [   36.803462] LR [c0010a24] arch_local_irq_restore+0x74/0x90
  [   36.803463] Call Trace:
  [   36.803465] [c03c97533790] [c014b184] mod_timer+0x154/0x300 
(unreliable)
  [   36.803468] [c03c975337b0] [c00db8b4] queue_work_on+0x74/0xf0
  [   36.803471] [c03c975337f0] [c060c334] 
cursor_timer_handler+0x44/0x80
  [   36.803474] [c03c97533820] [c0149ebc] call_timer_fn+0x5c/0x1c0
  [   36.803476] [c03c975338b0] [c014a37c] 
run_timer_softirq+0x31c/0x3f0
  [   36.803480] [c03c97533980] [c00beaf8] __do_softirq+0x188/0x3e0
  [   36.803483] [c03c97533a70] [c00befc8] irq_exit+0xc8/0x100
  [   36.803487] [c03c97533a90] [c001f954] timer_interrupt+0xa4/0xe0
  [   36.803490] [c03c97533ac0] [c0002714] 
decrementer_common+0x114/0x180
  [   36.803494] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
  [   36.803494] LR = arch_local_irq_restore+0x74/0x90
  [   36.803497] [c03c97533db0] [c03ffc49d678] 0xc03ffc49d678 
(unreliable)
  [   36.803502] [c03c97533dd0] [c0900708] 
cpuidle_enter_state+0x1a8/0x410
  [   36.803504] [c03c97533e30] [c0119898] call_cpuidle+0x78/0xd0
  [   36.803506] [c03c97533e70] [c0119c6c] 
cpu_startup_entry+0x37c/0x490
  [   36.803509] [c03c97533f30] [c004565c] 
start_secondary+0x33c/0x360
  [   36.803511] [c03c97533f90] [c0008b6c] 
start_secondary_prolog+0x10/0x14
  [   36.803512] Instruction dump:
  [   36.803514] 994d02ca 2fa3 

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

The attachment, kernels.txt, are notes I took while manually bisecting ubuntu 
kernels listed here:
https://launchpad.net/ubuntu/xenial/+source/linux
and mainline kernels from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/

The attachment, bisect.txt, is an annotated "git bisect log" associating
commits from the linux-stable tree with the deb packages I built,
installed, and tested.

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

  These messages would be repeated several times a second, and then
  pause for several seconds, then start again. I believe they are the
  cause of more sluggish behavior than with the older *Buntu releases.

  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
  which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:

  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations

  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800

  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.

  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 

  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

  Both have Insyde UEFI firmware. The latest version for both is v2.06
  and have same release date, 11/11/2013, according to the Acer &
  Gateway support web sites, although the firmware reports an Oct date.

  I realize it's quite likely that the laptop's firmware is the root
  cause of the problem. However, since the problem did not exist on
  older kernels, I hope a patch or workaround can be identified that
  will allow me to make good use of this laptop.

  Since I can reproduce the problem with a kernel built from the linux-
  stable git tree, should this problem also be reported to
  bugzilla.kernel.org? Or, should I try to contact the author of the
  "first bad commit", Lv Zheng  with the info in
  this bug report?

  Is there more testing I should do? Starting with enabling
  CONFIG_ACPI_DEBUG?

  Would there be value in me reverting the "first bad commit" to the
  latest Linux-4.4 kernel or to the latest xenial kernel to see if that
  helps or hurts?

  Is there more info I should collect, like output from acpidump?
  (Something I've seen mentioned on bugzilla.kernel.org)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

** Attachment added: "kernels.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+attachment/4701218/+files/kernels.txt

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

  These messages would be repeated several times a second, and then
  pause for several seconds, then start again. I believe they are the
  cause of more sluggish behavior than with the older *Buntu releases.

  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
  which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:

  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations

  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800

  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.

  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 

  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

  Both have Insyde UEFI firmware. The latest version for both is v2.06
  and have same release date, 11/11/2013, according to the Acer &
  Gateway support web sites, although the firmware reports an Oct date.

  I realize it's quite likely that the laptop's firmware is the root
  cause of the problem. However, since the problem did not exist on
  older kernels, I hope a patch or workaround can be identified that
  will allow me to make good use of this laptop.

  Since I can reproduce the problem with a kernel built from the linux-
  stable git tree, should this problem also be reported to
  bugzilla.kernel.org? Or, should I try to contact the author of the
  "first bad commit", Lv Zheng  with the info in
  this bug report?

  Is there more testing I should do? Starting with enabling
  CONFIG_ACPI_DEBUG?

  Would there be value in me reverting the "first bad commit" to the
  latest Linux-4.4 kernel or to the latest xenial kernel to see if that
  helps or hurts?

  Is there more info I should collect, like output from acpidump?
  (Something I've seen mentioned on bugzilla.kernel.org)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware   

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

** Attachment added: "bisect.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+attachment/4701219/+files/bisect.txt

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

  These messages would be repeated several times a second, and then
  pause for several seconds, then start again. I believe they are the
  cause of more sluggish behavior than with the older *Buntu releases.

  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
  which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:

  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations

  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800

  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.

  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 

  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

  Both have Insyde UEFI firmware. The latest version for both is v2.06
  and have same release date, 11/11/2013, according to the Acer &
  Gateway support web sites, although the firmware reports an Oct date.

  I realize it's quite likely that the laptop's firmware is the root
  cause of the problem. However, since the problem did not exist on
  older kernels, I hope a patch or workaround can be identified that
  will allow me to make good use of this laptop.

  Since I can reproduce the problem with a kernel built from the linux-
  stable git tree, should this problem also be reported to
  bugzilla.kernel.org? Or, should I try to contact the author of the
  "first bad commit", Lv Zheng  with the info in
  this bug report?

  Is there more testing I should do? Starting with enabling
  CONFIG_ACPI_DEBUG?

  Would there be value in me reverting the "first bad commit" to the
  latest Linux-4.4 kernel or to the latest xenial kernel to see if that
  helps or hurts?

  Is there more info I should collect, like output from acpidump?
  (Something I've seen mentioned on bugzilla.kernel.org)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

** Tags removed: acpi
** Tags added: kernel-acpi

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

  These messages would be repeated several times a second, and then
  pause for several seconds, then start again. I believe they are the
  cause of more sluggish behavior than with the older *Buntu releases.

  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
  which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:

  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations

  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800

  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.

  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 

  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

  Both have Insyde UEFI firmware. The latest version for both is v2.06
  and have same release date, 11/11/2013, according to the Acer &
  Gateway support web sites, although the firmware reports an Oct date.

  I realize it's quite likely that the laptop's firmware is the root
  cause of the problem. However, since the problem did not exist on
  older kernels, I hope a patch or workaround can be identified that
  will allow me to make good use of this laptop.

  Since I can reproduce the problem with a kernel built from the linux-
  stable git tree, should this problem also be reported to
  bugzilla.kernel.org? Or, should I try to contact the author of the
  "first bad commit", Lv Zheng  with the info in
  this bug report?

  Is there more testing I should do? Starting with enabling
  CONFIG_ACPI_DEBUG?

  Would there be value in me reverting the "first bad commit" to the
  latest Linux-4.4 kernel or to the latest xenial kernel to see if that
  helps or hurts?

  Is there more info I should collect, like output from acpidump?
  (Something I've seen mentioned on bugzilla.kernel.org)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

** Description changed:

  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  
  These messages would be repeated several times a second, and then pause
  for several seconds, then start again. I believe they are the cause of
  more sluggish behavior than with the older *Buntu releases.
  
  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
- which lead me to doing "git bisect" on the linux-stable tree. The result lead 
me to this commit:
+ which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:
  
  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations
  
  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800
  
  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations
  
  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.
  
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 
  
  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911
  
  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001
  
  Both have Insyde UEFI firmware. The latest version for both is v2.06 and
  have same release date, 11/11/2013, according to the Acer & Gateway
  support web sites, although the firmware reports an Oct date.
  
  I realize it's quite likely that the laptop's firmware is the root cause
  of the problem. However, since the problem did not exist on older
  kernels, I hope a patch or workaround can be identified that will allow
  me to make good use of this laptop.
  
- I assume this should also be reported to bugzilla.kernel.org. It is
- convenient to have the ubuntu-bug command do initial data collection.
+ Since I can reproduce the problem with a kernel built from the linux-
+ stable git tree, should this problem also be reported to
+ bugzilla.kernel.org? Or, should I try to contact the author of the
+ "first bad commit", Lv Zheng  with the info in this
+ bug report?
+ 
+ Is there more testing I should do? Starting with enabling
+ CONFIG_ACPI_DEBUG?
+ 
+ Would there be value in me reverting the "first bad commit" to the
+ latest Linux-4.4 kernel or to the latest xenial kernel to see if that
+ helps or hurts?
+ 
+ Is there more info I should collect, like output from acpidump?
+ (Something I've seen mentioned on bugzilla.kernel.org)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

** Description changed:

  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  
  These messages would be repeated several times a second, and then pause
  for several seconds, then start again. I believe they are the cause of
  more sluggish behavior than with the older *Buntu releases.
  
  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
- which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:
+ which lead me to doing "git bisect" on the linux-stable tree. The result lead 
me to this commit:
  
  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations
  
  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800
  
  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations
  
  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.
  
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 
  
  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911
  
  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001
  
  Both have Insyde UEFI firmware. The latest version for both is v2.06 and
  have same release date, 11/11/2013, according to the Acer & Gateway
  support web sites, although the firmware reports an Oct date.
  
  I realize it's quite likely that the laptop's firmware is the root cause
  of the problem. However, since the problem did not exist on older
  kernels, I hope a patch or workaround can be identified that will allow
  me to make good use of this laptop.
  
  I assume this should also be reported to bugzilla.kernel.org. It is
  convenient to have the ubuntu-bug command do initial data collection.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_CX
  dmi.board.vendor: Gateway
  dmi.board.version: V2.06
  dmi.chassis.asset.tag: Acer Asset Tag String
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06:
  dmi.product.name: NE570
  dmi.product.version: V2.06
  dmi.sys.vendor: Gateway

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

[Kernel-packages] [Bug 1603283] Re: REGRESSION: resume fails on recent 4.4.0-31, works on -28

[Reece]

Please advise how to proceed


snafu$ apport-collect 1603283
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
dpkg-query: no packages found matching linux


Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 594, in 
app.run_argv()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 573, in 
run_update_report
attachment_comment='apport information')
  File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/launchpad.py", 
line 406, in update
bug.lp_save()
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/resource.py", line 
778, in lp_save
URI(self.self_link), representation, headers)
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/_browser.py", line 
484, in patch
'PATCH', extra_headers=extra_headers)
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/_browser.py", line 
426, in _request
raise error
lazr.restfulclient.errors.ServerError: HTTP Error 503: Service Unavailable
Response headers:
---
-content-encoding: gzip
connection: close
content-length: 9039

...


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

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The
  machine appears to suspend, and this is confirmed in syslog. However,
  when attempting resume, the screen is black and there is no indication
  of resumption. The machine automatically reboots within ~15 seconds. I
  did this three times with -31.  Reverting to the -28 kernel restored
  suspend/resume.

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

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

[Kernel-packages] [Bug 1603289] [NEW] package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before instal

[David]

Public bug reported:

Install attempted by Ubuntu Mate included Update Manager along with
Grub2 update. The Grub2 update failed and according to the pop-up
announcement by the Update Manager it also caused the linux-
image-4.4.0-31-generic installation failure.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  david  2162 F pulseaudio
 /dev/snd/controlC0:  david  2162 F pulseaudio
Date: Thu Jul 14 20:27:23 2016
DuplicateSignature:
 package:linux-image-4.4.0-31-generic:(not installed)
 Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
  unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
InstallationDate: Installed on 2016-05-23 (53 days ago)
InstallationMedia: It
MachineType: GizmoSphere Gizmo2
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2014
dmi.bios.vendor: coreboot
dmi.bios.version: SageBios_Gizmo2-121
dmi.chassis.type: 3
dmi.chassis.vendor: GizmoSphere
dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
dmi.product.name: Gizmo2
dmi.product.version: 1.0
dmi.sys.vendor: GizmoSphere

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


** Tags: amd64 apport-package need-duplicate-check 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/1603289

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  New

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another 

[Kernel-packages] [Bug 1603288] [NEW] package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before instal

[David]

Public bug reported:

Install attempted by Ubuntu Mate included Update Manager along with
Grub2 update. The Grub2 update failed and according to the pop-up
announcement by the Update Manager it also caused the  linux-
image-4.4.0-31-generic installation failure.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  david  2162 F pulseaudio
 /dev/snd/controlC0:  david  2162 F pulseaudio
Date: Thu Jul 14 20:27:23 2016
DuplicateSignature:
 package:linux-image-4.4.0-31-generic:(not installed)
 Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
  unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
InstallationDate: Installed on 2016-05-23 (53 days ago)
InstallationMedia: It
MachineType: GizmoSphere Gizmo2
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2014
dmi.bios.vendor: coreboot
dmi.bios.version: SageBios_Gizmo2-121
dmi.chassis.type: 3
dmi.chassis.vendor: GizmoSphere
dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
dmi.product.name: Gizmo2
dmi.product.version: 1.0
dmi.sys.vendor: GizmoSphere

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


** Tags: amd64 apport-package need-duplicate-check 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/1603288

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  New

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing 

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

[Brad Figg]

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

apport-collect 1603283

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

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

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

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

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The
  machine appears to suspend, and this is confirmed in syslog. However,
  when attempting resume, the screen is black and there is no indication
  of resumption. The machine automatically reboots within ~15 seconds. I
  did this three times with -31.  Reverting to the -28 kernel restored
  suspend/resume.

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

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

[Kernel-packages] [Bug 1603283] [NEW] REGRESSION: resume fails on recent 4.4.0-31, works on -28

[Reece]

Public bug reported:

Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The
machine appears to suspend, and this is confirmed in syslog. However,
when attempting resume, the screen is black and there is no indication
of resumption. The machine automatically reboots within ~15 seconds. I
did this three times with -31.  Reverting to the -28 kernel restored
suspend/resume.

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1603283/+attachment/4701132/+files/lspci-vnvn.log

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  New

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The
  machine appears to suspend, and this is confirmed in syslog. However,
  when attempting resume, the screen is black and there is no indication
  of resumption. The machine automatically reboots within ~15 seconds. I
  did this three times with -31.  Reverting to the -28 kernel restored
  suspend/resume.

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

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

[Kernel-packages] [Bug 1596643] onza (i386) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-15_00-29-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

4.4.0-32-generic-51~lp1573062.1 failed.

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

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

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

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

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

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

[Kernel-packages] [Bug 1603137] Re: libbfd changed name without transition

[Steve Langasek]

** Description changed:

+ [SRU Justification]
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.
  
  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.
+ 
+ [Test case]
+ 1. Install eztrace on 16.04.
+ 2. Install binutils from xenial-updates.
+ 3. Run 'eztrace'.  Confirm that this fails with a library error.
+ 4. Install binutils from xenial-proposed.
+ 5. Run 'eztrace'.  Confirm that this gives usage output instead of failing 
with a library error.
+ 
+ [Regression potential]
+ Packages which depend on libbfd-2.26-system.so are currently broken with the 
binutils in xenial-updates.  No packages appear to have been built yet against 
the libbfd-2.26.1-system.so soname.  Therefore the regression potential is 
minimal.  The solution is intended to be compatible with both upstream sonames, 
so that any future packages which do rebuild against the 2.26.1 soname will 
have a versioned dependency on binutils (>= 2.26.1), binutils (<= 2.27).

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

  [Test case]
  1. Install eztrace on 16.04.
  2. Install binutils from xenial-updates.
  3. Run 'eztrace'.  Confirm that this fails with a library error.
  4. Install binutils from xenial-proposed.
  5. Run 'eztrace'.  Confirm that this gives usage output instead of failing 
with a library error.

  [Regression potential]
  Packages which depend on libbfd-2.26-system.so are currently broken with the 
binutils in xenial-updates.  No packages appear to have been built yet against 
the libbfd-2.26.1-system.so soname.  Therefore the regression potential is 
minimal.  The solution is intended to be compatible with both upstream sonames, 
so that any future packages which do rebuild against the 2.26.1 soname will 
have a versioned dependency on binutils (>= 2.26.1), binutils (<= 2.27).

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

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

[Kernel-packages] [Bug 1603137] Re: libbfd changed name without transition

[Steve Langasek]

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

** Changed in: binutils (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Invalid

Bug description:
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

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

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

[Kernel-packages] [Bug 1603137] Re: libbfd changed name without transition

[Steve Langasek]

The only change to the symbols in 2.26.1 is one dropped internal symbol
(_bfd_*) and the soname change itself.  It's appropriate to restore
binary compatibility by providing both -2.26.1- and -2.26- names on
disk.

I've uploaded this to yakkety as 2.26.1-1ubuntu2 and will do the same
for xenial-updates - we definitely don't want to do an soname transition
in SRU.

** Changed in: binutils (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

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

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

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

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

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

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-14_23-14-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised

[CraigFoote]

I have 16.04 installed on my laptop and my media center PC. The USB3.0
external hard drive works when plugged into the laptop but not the media
center PC. Any ideas?

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

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

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

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

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-14_21-26-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

  These messages would be repeated several times a second, and then
  pause for several seconds, then start again. I believe they are the
  cause of more sluggish behavior than with the older *Buntu releases.

  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
  which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:

  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations

  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800

  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.

  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 

  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

  Both have Insyde UEFI firmware. The latest version for both is v2.06
  and have same release date, 11/11/2013, according to the Acer &
  Gateway support web sites, although the firmware reports an Oct date.

  I realize it's quite likely that the laptop's firmware is the root
  cause of the problem. However, since the problem did not exist on
  older kernels, I hope a patch or workaround can be identified that
  will allow me to make good use of this laptop.

  I assume this should also be reported to bugzilla.kernel.org. It is
  convenient to have the ubuntu-bug command do initial data collection.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_CX
  dmi.board.vendor: Gateway
  dmi.board.version: V2.06
  dmi.chassis.asset.tag: Acer Asset Tag String
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.06
  dmi.modalias: 

[Kernel-packages] [Bug 1603230] [NEW] acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

[H Buus]

Public bug reported:

I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

These messages would be repeated several times a second, and then pause
for several seconds, then start again. I believe they are the cause of
more sluggish behavior than with the older *Buntu releases.

I followed the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection
which lead me to doing "git bisect" on the linux-stable kernel. The result lead 
me to this commit:

# first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
EC: Fix an issue caused by the serialized _Qxx evaluations

commit 02b771b64b73226052d6e731a0987db3b47281e9
Author: Lv Zheng 
Date:   Wed Aug 12 11:12:02 2015 +0800

ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

It is proven that Windows evaluates _Qxx handlers in a parallel way. This
patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
form a separate queue, so that _Qxx evaluations can be queued up on
different CPUs rather than being queued up on a CPU0 bound queue.
Event handling related callbacks are also renamed and sorted in this patch.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
Reported-and-tested-by: Gabriele Mazzotta 
Signed-off-by: Lv Zheng 
Signed-off-by: Rafael J. Wysocki 

The laptop was purchased from tigerdirect. Here's link to specs:
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

The laptop appears to be a re-branded Acer Aspire E1-570:
http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

Both have Insyde UEFI firmware. The latest version for both is v2.06 and
have same release date, 11/11/2013, according to the Acer & Gateway
support web sites, although the firmware reports an Oct date.

I realize it's quite likely that the laptop's firmware is the root cause
of the problem. However, since the problem did not exist on older
kernels, I hope a patch or workaround can be identified that will allow
me to make good use of this laptop.

I assume this should also be reported to bugzilla.kernel.org. It is
convenient to have the ubuntu-bug command do initial data collection.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  buus   1830 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 14 18:11:02 2016
HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
InstallationDate: Installed on 2016-07-01 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gateway NE570
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic  N/A
 linux-firmware1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_CX
dmi.board.vendor: Gateway
dmi.board.version: V2.06
dmi.chassis.asset.tag: Acer Asset Tag String
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06:
dmi.product.name: NE570
dmi.product.version: V2.06
dmi.sys.vendor: Gateway

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


** Tags: amd64 apport-bug xenial

** Description changed:

- I found what I believe is a regression on my Gateway ne570 laptop. It was 
running
- mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed
- ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like 
this:
- Jul 10 17:01:10 

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

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onibi__3.19.0-65.73~14.04.1__2016-07-14_21-07-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[bugproxy]

--- Comment From jhop...@us.ibm.com 2016-07-14 17:43 EDT---
I updated to:  linux-image-4.4.0-31-generic   4.4.0-31.50

and remeasured performance, still looks good. Thanks! We can close this
bug now.

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

Title:
  Restore irqfd fast path for PPC

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

Bug description:
  Dear Canonical,

  A patch is now upstream to restore the irqfd fast path for Power, can
  this be pulled into a 16.04.1? It was found to significantly help
  guest small msg rate networking performance by ~30%.

  Commit id:
  b1a4286b8f3393857a205ec89607683161b75f90

KVM: PPC: Book3S HV: Re-enable XICS fast path for irqfd-generated
  interrupts

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

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

[Kernel-packages] [Bug 1476393] Re: Installer initrd missing kernels for Intel X710 Adapter

[Cindy Quach]

Hi, are there any updates on when the Trusty fix will be released?

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

Title:
  Installer initrd missing kernels for Intel X710 Adapter

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

Bug description:
  The installer initrd is missing the i40e modules for ethernet cards
  like the Intel X710.  I was able to grab the latest from Intel's site,
  compile the driver, respin the initrd, and get the installer to work:

  https://downloadcenter.intel.com/download/24411/Network-Adapter-
  Driver-for-PCI-E-40-Gigabit-Network-Connections-under-Linux-

  Can we include the i40e module into nic-modules so that the debian-
  installer netboot kernels will work on this card?

  Thanks,

  Ant

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

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

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

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-14_19-36-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1596643] onibi (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onibi__3.19.0-65.73~14.04.1__2016-07-14_20-08-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1596643] onibi (i386) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onibi__3.19.0-65.73~14.04.1__2016-07-14_18-23-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.13.0-92.139~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597060
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 14. July 2016 20:01 UTC

** Description changed:

  This bug is for tracking the 3.13.0-92.139~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597060
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 14. July 2016 20:01 UTC

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1597109] Re: linux: 3.2.0-106.147 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-106.147 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 14. July 2016 20:02 UTC

** Description changed:

  This bug is for tracking the 3.2.0-106.147 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 14. July 2016 20:02 UTC

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

Title:
  linux: 3.2.0-106.147 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597127] Re: linux-ti-omap4: 3.2.0-1484.111 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1484.111 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 14. July 2016 20:03 UTC

** Description changed:

  This bug is for tracking the 3.2.0-1484.111 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 14. July 2016 20:03 UTC

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1597128] Re: linux-armadaxp: 3.2.0-1669.95 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1669.95 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 14. July 2016 20:03 UTC

** Description changed:

  This bug is for tracking the 3.2.0-1669.95 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 14. July 2016 20:03 UTC

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

Title:
  linux-armadaxp: 3.2.0-1669.95 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1592481] Re: VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

[Paulo F. Smorigo]

Verified. Working fine. Thanks!

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

Title:
  VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

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

Bug description:
  ---Problem Description---
  Pre-sales customer with loaner P8 observes slow performance of 
VMX-accelerated kernel crypto, multiple times slower then Haswell.
   
  ---uname output---
  Linux crimini9 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = unknown 
   
  ---Steps to Reproduce---
   Run cryptsetup benchmark with the VMX crypto module modprobed.
   
  Original customer cryptsetup benchmark results on Ubuntu 16.04:
   
  Intel i5 core 2500k overclocked at 4.5 GHz w/ 4 cores:
  aes-xts   256b  1884,2 MiB/s  1952,0 MiB/s
  aes-cbc  256b   509,1 MiB/s  1724,2 MiB/s
   
  Results for xeon e5-2680 at 2.80 Ghz:
   aes-cbc   256b   392.6 MiB/s  2062.0 MiB/s
   aes-xts   256b  3853.0 MiB/s  4793.0 MiB/s
   
  Results from intel i7 3770 at 3.40 GHz:
  aes-xts?? 256b??7787.0 MiB/s??7962.0 MiB/s
  aes-cbc?? 256b?? 662.0 MiB/s??3779.0 MiB/s
   
  Power 8 at 4.15Ghz and vmx-crypto loaded (s822L, 16c, powervm)
  aes-xts   256b   410.7 MiB/s   413.9 MiB/s
  aes-cbc   256b   300.6 MiB/s   358.7 MiB/s

  Mirroring to Canonical for their awareness as IBM purses a fix for
  inclusion in a 16.04 SRU.

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

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

[Kernel-packages] [Bug 1477466] Re: Low performance when using vlan over VxLan

[Dragan S.]

Hi Talat-

The bug was filed against vivid which is no longer maintained. The
original submitter had requested certain patches be back-ported to vivid
because they supposedly fixed an issue.

The requested patches were back-ported and they didn't fix the issue the
submitter purported that they fix.

So I wanted to know two things:
1. Does the reported issue still appear in latest releases such as xenial(16.04)
2. If so does this issue appear in the mainline kernel as well?

This will determine if the reported issue is an Ubuntu specific issue or
if the general mainline linux kernel needs fixing.

If you can re-run the tests on 1 & 2 that would be very helpful, but it
would also help if you could provide the exact configuration and steps
you use so that I can try and reproduce your tests.

Thanks.

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

Title:
  Low performance when using vlan over VxLan

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

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

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

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

[Kernel-packages] [Bug 1592481] Re: VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

[Breno Leitão]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1592481

Title:
  VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

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

Bug description:
  ---Problem Description---
  Pre-sales customer with loaner P8 observes slow performance of 
VMX-accelerated kernel crypto, multiple times slower then Haswell.
   
  ---uname output---
  Linux crimini9 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = unknown 
   
  ---Steps to Reproduce---
   Run cryptsetup benchmark with the VMX crypto module modprobed.
   
  Original customer cryptsetup benchmark results on Ubuntu 16.04:
   
  Intel i5 core 2500k overclocked at 4.5 GHz w/ 4 cores:
  aes-xts   256b  1884,2 MiB/s  1952,0 MiB/s
  aes-cbc  256b   509,1 MiB/s  1724,2 MiB/s
   
  Results for xeon e5-2680 at 2.80 Ghz:
   aes-cbc   256b   392.6 MiB/s  2062.0 MiB/s
   aes-xts   256b  3853.0 MiB/s  4793.0 MiB/s
   
  Results from intel i7 3770 at 3.40 GHz:
  aes-xts?? 256b??7787.0 MiB/s??7962.0 MiB/s
  aes-cbc?? 256b?? 662.0 MiB/s??3779.0 MiB/s
   
  Power 8 at 4.15Ghz and vmx-crypto loaded (s822L, 16c, powervm)
  aes-xts   256b   410.7 MiB/s   413.9 MiB/s
  aes-cbc   256b   300.6 MiB/s   358.7 MiB/s

  Mirroring to Canonical for their awareness as IBM purses a fix for
  inclusion in a 16.04 SRU.

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Leann Ogasawara]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1596643] onza (i386) - tests ran: 4, failed: 0

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-14_19-18-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-14_19-01-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-64.72~14.04.1/onza__3.19.0-64.72~14.04.1__2016-07-14_17-55-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1384969] Re: Writing large amounts of data to exFAT formatted micro sdcards with Ubuntu causes kernel errors and permanent sdcard failure.

[Bas van den Heuvel]

Got the same problem with Ubuntu 16.04 with 4.4.0-28 kernel (64bit).

Tried to copy about 60GB, stuck after a few minutes:


Jul 14 18:47:41 patsy kernel: [ 6840.370388] INFO: task mount.exfat:19269 
blocked for more than 120 seconds.
Jul 14 18:47:41 patsy kernel: [ 6840.370392]   Tainted: P   OE   
4.4.0-28-generic #47-Ubuntu
Jul 14 18:47:41 patsy kernel: [ 6840.370394] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 14 18:47:41 patsy kernel: [ 6840.370397] mount.exfat D 88080c403a08 
0 19269  1 0x
Jul 14 18:47:41 patsy kernel: [ 6840.370403]  88080c403a08 0100 
88080b1dac40 88072da9
Jul 14 18:47:41 patsy kernel: [ 6840.370408]  88080c404000 880836d96d00 
7fff 81823db0
Jul 14 18:47:41 patsy kernel: [ 6840.370413]  88080c403b60 88080c403a20 
818235b5 
Jul 14 18:47:41 patsy kernel: [ 6840.370418] Call Trace:
Jul 14 18:47:41 patsy kernel: [ 6840.370425]  [] ? 
bit_wait+0x60/0x60
Jul 14 18:47:41 patsy kernel: [ 6840.370430]  [] 
schedule+0x35/0x80
Jul 14 18:47:41 patsy kernel: [ 6840.370436]  [] 
schedule_timeout+0x1b5/0x270
Jul 14 18:47:41 patsy kernel: [ 6840.370443]  [] ? 
ktime_get+0x3c/0xb0
Jul 14 18:47:41 patsy kernel: [ 6840.370449]  [] ? 
bit_wait+0x60/0x60
Jul 14 18:47:41 patsy kernel: [ 6840.370454]  [] 
io_schedule_timeout+0xa4/0x110
Jul 14 18:47:41 patsy kernel: [ 6840.370460]  [] 
bit_wait_io+0x1b/0x70
Jul 14 18:47:41 patsy kernel: [ 6840.370466]  [] 
__wait_on_bit+0x5d/0x90
Jul 14 18:47:41 patsy kernel: [ 6840.370471]  [] ? 
submit_bio+0x76/0x170
Jul 14 18:47:41 patsy kernel: [ 6840.370476]  [] ? 
bit_wait+0x60/0x60
Jul 14 18:47:41 patsy kernel: [ 6840.370482]  [] 
out_of_line_wait_on_bit+0x82/0xb0
Jul 14 18:47:41 patsy kernel: [ 6840.370489]  [] ? 
autoremove_wake_function+0x40/0x40
Jul 14 18:47:41 patsy kernel: [ 6840.370494]  [] 
__block_write_begin+0x263/0x480
Jul 14 18:47:41 patsy kernel: [ 6840.370499]  [] ? 
I_BDEV+0x20/0x20
Jul 14 18:47:41 patsy kernel: [ 6840.370504]  [] ? 
I_BDEV+0x20/0x20
Jul 14 18:47:41 patsy kernel: [ 6840.370508]  [] 
block_write_begin+0x46/0x80
Jul 14 18:47:41 patsy kernel: [ 6840.370514]  [] 
blkdev_write_begin+0x23/0x30
Jul 14 18:47:41 patsy kernel: [ 6840.370521]  [] 
generic_perform_write+0xce/0x1c0
Jul 14 18:47:41 patsy kernel: [ 6840.370527]  [] 
__generic_file_write_iter+0x1a2/0x1e0
Jul 14 18:47:41 patsy kernel: [ 6840.370532]  [] 
blkdev_write_iter+0x8f/0x130
Jul 14 18:47:41 patsy kernel: [ 6840.370539]  [] 
new_sync_write+0x9b/0xe0
Jul 14 18:47:41 patsy kernel: [ 6840.370545]  [] 
__vfs_write+0x26/0x40
Jul 14 18:47:41 patsy kernel: [ 6840.370551]  [] 
vfs_write+0xa9/0x1a0
Jul 14 18:47:41 patsy kernel: [ 6840.370556]  [] ? 
vfs_read+0x114/0x130
Jul 14 18:47:41 patsy kernel: [ 6840.370563]  [] 
SyS_pwrite64+0x95/0xb0
Jul 14 18:47:41 patsy kernel: [ 6840.370567]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
Jul 14 18:48:34 patsy kernel: [ 6893.695042] sd 6:0:0:0: timing out command, 
waited 180s


Tried it with 4.7.0-rc7, same problem. 

Someone tried it with smaller buffers or less memory ?

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

Title:
  Writing large amounts of data to exFAT formatted micro sdcards with
  Ubuntu causes kernel errors and permanent sdcard failure.

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've now confirmed 3 cases where writing large volumes of data causes
  kernel errors:

  System: linux Kubuntu 12.04.5 LTS,  
  Package: udev 175-0ubuntu9.6 

  STEPS: 
  1) Insert new 64G microsd card (either via built-in card reader or with USB 
style adapter)
  2) Create and write fresh partition with fdisk (full card, 1 primary 
partition, type 7, exFAT)
  3) mkfs.exfat /dev/sdi1
  4) mount partition using device manager gui (process shows as 
/sbin/mount.exfat /dev/sdi1 /media//6FED-20E6 -o 
rw,nosuid,nodev,uhelper=udisks2)
  5) Attempt to copy a large amount (20G+) of data to drive using Dolphin gui, 
or in the most recent case, rsync.
  $ rsync -rltsihv --delete --progress --stats /home/user/syncfolder/  
/media//6FED-20E6/

  Somewhere during the middle of the operation the process will hang and
  provide the dmesg output below.  Once this happens, the card will go
  into internal failsafe mode and become permanently read-only.  The
  card is now non-recoverable using any software method (fsck, hdpart,
  windows chkdsk, or the sdcard.org formatter).

  This originally occurred for me on a new G.Skill 32gb card, then on a
  Sandisk Ultra Plus 64g card.  Both cards were returned to the
  manufacturers which confirmed the cards as permanently failed (and
  replaced under warranty).

  Today I tried again with the replacement Sandisk card using a micro
  sdcard usb adapter instead of the built in card reader, and received
  the same result - another failed 

[Kernel-packages] [Bug 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04

[Jason Couture]

Here you go

root@ContainerHost1:~# cat /proc/meminfo 
MemTotal:8328584 kB
MemFree:  130152 kB
MemAvailable:3530108 kB
Buffers:  273056 kB
Cached:  3071076 kB
SwapCached:   598656 kB
Active:  3785684 kB
Inactive:3125476 kB
Active(anon):2047484 kB
Inactive(anon):  2241632 kB
Active(file):1738200 kB
Inactive(file):   883844 kB
Unevictable:3660 kB
Mlocked:3660 kB
SwapTotal:   2097148 kB
SwapFree:1293344 kB
Dirty: 32316 kB
Writeback: 0 kB
AnonPages:   3010444 kB
Mapped:   404308 kB
Shmem:719664 kB
Slab: 959700 kB
SReclaimable: 820980 kB
SUnreclaim:   138720 kB
KernelStack:   17200 kB
PageTables:33148 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit: 6261440 kB
Committed_AS:7291440 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   0 kB
VmallocChunk:  0 kB
HardwareCorrupted: 0 kB
AnonHugePages:   1992704 kB
CmaTotal:  0 kB
CmaFree:   0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
DirectMap4k:  202152 kB
DirectMap2M: 8183808 kB

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

Title:
  Hyper-V Memory Ballooning re-broken in 16.04

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

Bug description:
  Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but
  the bug has returned in 16.04.

  
  Steps to reproduce:

  1. Create Gen2 Hyper-V VM
  2. Install Ubuntu 16.04
  3. modprobe hv_balloon
  Memory usage according to Hyper-V Manager will not change

  
  This has been reproduced on 2 fresh Ubuntu Server 16.04 instances.

  I installed linux-generic-xenial on a 14.04 instance, rebooted,
  modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to
  the correct level.

  Environment:
  Host: Windows NanoServer 2016

  Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6`
  Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 
4.4.8`

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

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

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

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-07-14 14:12 EDT---
Closing this bug and working the updated patch via IBM bug 136437 (to be 
mirrored to new LP bug to avoid confusion with this one).

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

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

Title:
  Predictable naming mechanism is leading to issues in DLPAR operations
  of NICs

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

Bug description:
  Recent kernels are using predictable naming for network interfaces, so
  the network stack is more tied to PCI naming. This can be a problem in
  hotplug scenarios, because PCI addresses will change if devices are
  removed and then re-added. This situation seems unusual, but it can
  happen if a user wants to replace a NIC without rebooting the machine,
  for example.

  The patch attached here should deal with this situation, since it makes 
PHB/domain number fixed based on device-tree properties.
   
  The problem can be reproduced by removing and re-adding a PCI network 
adapter, so its address will change and, per predictable naming scheme, so is 
the interface name.

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

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

[Kernel-packages] [Bug 1596631] Re: linux: 3.19.0-65.73 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-65.73 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 14. July 2016 18:08 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.19.0-65.73 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 14. July 2016 18:08 UTC
- kernel-stable-phase:Released

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

Title:
  linux: 3.19.0-65.73 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597047] Re: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 14. July 2016 18:13 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 14. July 2016 18:13 UTC
- kernel-stable-phase:Released

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

Title:
  linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597053] Re: linux: 4.2.0-42.49 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 4.2.0-42.49 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 14. July 2016 18:15 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.2.0-42.49 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 14. July 2016 18:15 UTC
- kernel-stable-phase:Released

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

Title:
  linux: 4.2.0-42.49 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596643] onibi (amd64) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onibi__3.19.0-65.73~14.04.1__2016-07-14_16-39-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT---
Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please 
promote to xenial now.

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

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr 

[Kernel-packages] [Bug 1590985] Re: Wifi non-functional after suspend (Intel 6205)

[Juraj]

I can confirm same behavior as James Ferguson on a Thinkpad W520 with
Intel Wireless Centrino 6205 Advanced-N. Network manager fails to
display any signal strength and visible networks, but I am actually
connected and internet works. This didn't happen on Ubuntu 14.04.

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

Title:
  Wifi non-functional after suspend (Intel 6205)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Often, but not always, on resume from suspend my wifi does not
  connect.  In the networking tray drop-down I can see one single wifi
  network listed (out of the many within range), and it can't reconnect
  to my network.

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

  I'm not sure what would be more appropriate, but that works.  Then my
  laptop auto-connects to the right network, as expected.

  Turning on/off the hardware wireless switch on the thinkpad does not
  clear the problem.

  Just before running ubuntu-bug to submit this, I had the problem, then
  reloaded the iwldvm module.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1934 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun  9 18:57:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2325KZ5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325KZ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 518896
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325KZ5
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1597060] Re: linux: 3.13.0-92.139 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.13.0-92.139 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 14. July 2016 18:06 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.13.0-92.139 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 14. July 2016 18:06 UTC
- kernel-stable-phase:Released

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

Title:
  linux: 3.13.0-92.139 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596643] Re: linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 14. July 2016 18:04 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 14. July 2016 18:04 UTC
- kernel-stable-phase:Released

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1602449] Re: linux: 4.4.0-31.50 -proposed tracker

[Brad Figg]

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


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

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

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

** Description changed:

  This bug is for tracking the 4.4.0-31.50 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 14. July 2016 18:03 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.4.0-31.50 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 14. July 2016 18:03 UTC
- kernel-stable-phase:Released

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

Title:
  linux: 4.4.0-31.50 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596643] dwalin (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/dwalin__3.19.0-65.73~14.04.1__2016-07-14_17-09-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: 

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

[Brad Figg]

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/onza__3.19.0-65.73~14.04.1__2016-07-14_16-14-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[bugproxy]

--- Comment From gpicc...@br.ibm.com 2016-07-14 13:34 EDT---
(In reply to comment #8)
> https://lists.ubuntu.com/archives/kernel-team/2016-July/078752.html

Tim, I'm not really sure about in which release of Xenial's kernel those
patches will be available. I mean...in 4.4.0-28 they are not merged, but
in the next release they will be there?

Can you help me understand better? Thanks in advance,

Guilherme

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

Title:
  Hotplug device addition issue - missing patches on Xenial kernel

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

Bug description:
  == Comment: #0 - Guilherme Guaglianoni Piccoli - 2016-06-29 18:09:04 ==
  When performing hotplug device addition to LPAR/guest with Ubuntu 16.04 
(kernel 4.4.0-28) we can observe a kernel oops if device makes use of 64-bit 
DDW DMA. The following stack trace was observed with QLogic NIC (bnx2x driver):

  
  [  131.52] --- interrupt: 300 at enable_ddw+0x254/0x7c0
 LR = enable_ddw+0x238/0x7c0
  [  131.52] [c001fbc67480] [c0089b88] 
dma_set_mask_pSeriesLP+0x208/0x290
  [  131.52] [c001fbc67510] [c00246b8] dma_set_mask+0x58/0xf0
  [  131.52] [c001fbc67540] [d387a654] bnx2x_init_one+0x504/0x10f0 
[bnx2x]
  [  131.52] [c001fbc67620] [c05e4eac] local_pci_probe+0x6c/0x140
  [  131.52] [c001fbc676b0] [c05e5d58] pci_device_probe+0x168/0x200
  [  131.52] [c001fbc67710] [c06d2530] 
driver_probe_device+0x1f0/0x610
  [  131.52] [c001fbc677a0] [c06d2a6c] __driver_attach+0x11c/0x120
  [  131.52] [c001fbc677e0] [c06ceeac] bus_for_each_dev+0x9c/0x110
  [  131.52] [c001fbc67830] [c06d198c] driver_attach+0x3c/0x60
  [  131.52] [c001fbc67860] [c06d1278] bus_add_driver+0x2d8/0x390
  [  131.52] [c001fbc678f0] [c06d39dc] driver_register+0x9c/0x180
  [  131.52] [c001fbc67960] [c05e401c] 
__pci_register_driver+0x6c/0x90

  
  This issue is solved upstream, by the following 3 patches (SHA-1 from Linus 
tree):

  c2078d9ef60 ("Revert \"powerpc/eeh: Fix crash in eeh_add_device_early() on 
Cell\"")
  8445a87f709 ("powerpc/iommu: Remove the dependency on EEH struct in DDW 
mechanism")
  8a934efe943 ("powerpc/pseries: Fix PCI config address for DDW")

  
  So, we want to request the addition of these fixes in Ubuntu Xenial kernel.
  Besides, an old and obsolete non-upstream patch related to this issue can be 
removed (SHA-1 from Ubuntu xenial tree):

  623aabd5d68 ("UBUNTU: SAUCE: powerpc/eeh: Validate arch in
  eeh_add_device_early()")

  
  Thanks,

  Guilherme

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

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

[Kernel-packages] [Bug 1597109] Re: linux: 3.2.0-106.147 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 3.2.0-106.147 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-trusty -
3.13.0-92.139~precise1

---
linux-lts-trusty (3.13.0-92.139~precise1) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597106

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

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

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

Title:
  CVE-2016-3070

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

[Kernel-packages] [Bug 1597128] Re: linux-armadaxp: 3.2.0-1669.95 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-armadaxp - 3.2.0-1669.95

---
linux-armadaxp (3.2.0-1669.95) precise; urgency=low

  [ Ike Panhc ]

  * Release Tracking Bug
- LP: #1597128
  * Rebase to Ubuntu-3.2.0-106.147

  [ Ubuntu: 3.2.0-106.147 ]

  * Release Tracking Bug
- LP: #1597109
  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Ike Panhc   Thu, 30 Jun 2016 14:12:04 +0800

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: In Progress => Fix Released

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: In Progress => Fix Released

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

Title:
  linux-armadaxp: 3.2.0-1669.95 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597127] Re: linux-ti-omap4: 3.2.0-1484.111 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1484.111

---
linux-ti-omap4 (3.2.0-1484.111) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597127

  [ Ubuntu: 3.2.0-106.147 ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Kamal Mostafa   Thu, 30 Jun 2016 08:46:31 -0700

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

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597060
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-trusty -
3.13.0-92.139~precise1

---
linux-lts-trusty (3.13.0-92.139~precise1) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597106

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

Title:
  CVE-2016-3070

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

[Kernel-packages] [Bug 1597128] Re: linux-armadaxp: 3.2.0-1669.95 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux-armadaxp: 3.2.0-1669.95 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.2.0-106.147

---
linux (3.2.0-106.147) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597109

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Kamal Mostafa   Tue, 28 Jun 2016 14:09:30 -0700

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

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

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  

[Kernel-packages] [Bug 1603137] Re: libbfd changed name without transition

[dann frazier]

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

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-trusty -
3.13.0-92.139~precise1

---
linux-lts-trusty (3.13.0-92.139~precise1) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597106

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597060
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1597127] Re: linux-ti-omap4: 3.2.0-1484.111 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1484.111

---
linux-ti-omap4 (3.2.0-1484.111) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597127

  [ Ubuntu: 3.2.0-106.147 ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Kamal Mostafa   Thu, 30 Jun 2016 08:46:31 -0700

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.2.0-106.147

---
linux (3.2.0-106.147) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597109

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Kamal Mostafa   Tue, 28 Jun 2016 14:09:30 -0700

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 

[Kernel-packages] [Bug 1597109] Re: linux: 3.2.0-106.147 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.2.0-106.147

---
linux (3.2.0-106.147) precise; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597109

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Kamal Mostafa   Tue, 28 Jun 2016 14:09:30 -0700

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

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

Title:
  linux: 3.2.0-106.147 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1597127] Re: linux-ti-omap4: 3.2.0-1484.111 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597128] Re: linux-armadaxp: 3.2.0-1669.95 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-armadaxp - 3.2.0-1669.95

---
linux-armadaxp (3.2.0-1669.95) precise; urgency=low

  [ Ike Panhc ]

  * Release Tracking Bug
- LP: #1597128
  * Rebase to Ubuntu-3.2.0-106.147

  [ Ubuntu: 3.2.0-106.147 ]

  * Release Tracking Bug
- LP: #1597109
  * HID: core: prevent out-of-bound readings
- LP: #1579190

 -- Ike Panhc   Thu, 30 Jun 2016 14:12:04 +0800

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

Title:
  linux-armadaxp: 3.2.0-1669.95 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1597109
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-utopic -
3.16.0-77.99~14.04.1

---
linux-lts-utopic (3.16.0-77.99~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597047

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587087
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587087

 -- Kamal Mostafa   Tue, 28 Jun 2016 11:43:10 -0700

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

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

Title:
  CVE-2016-3070

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

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-vivid - 3.19.0-65.73~14.04.1

---
linux-lts-vivid (3.19.0-65.73~14.04.1) trusty; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1596643

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070

 -- Benjamin M Romer   Mon, 27 Jun 2016
12:37:48 -0400

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

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

Title:
  CVE-2016-3070

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

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

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT---
Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please 
promote to xenial now.

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

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-wily - 4.2.0-42.49~14.04.1

---
linux-lts-wily (4.2.0-42.49~14.04.1) trusty; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1597108

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * Revert "scsi: fix soft lockup in scsi_remove_target() on module
removal"
- LP: #1592552
  * ath10k: fix firmware assert in monitor mode
- LP: #1592552
  * drm/i915: Fix race condition in intel_dp_destroy_mst_connector()
- LP: #1592552
  * ath10k: fix debugfs pktlog_filter write
- LP: #1592552
  * drm/i915: Call intel_dp_mst_resume() before resuming displays
- LP: #1592552
  * ARM: mvebu: fix GPIO config on the Linksys boards
- LP: #1592552
  * ath5k: Change led pin configuration for compaq c700 laptop
- LP: #1592552, #972604
  * xfs: disallow rw remount on fs with unknown ro-compat features
- LP: #1592552
  * xfs: Don't wrap growfs AGFL indexes
- LP: #1592552
  * rtlwifi: rtl8723be: Add antenna select module parameter
- LP: #1592552
  * rtlwifi: btcoexist: Implement antenna selection
- LP: #1592552
  * drm/gma500: Fix possible out of bounds read
- LP: #1592552
  * Bluetooth: vhci: fix open_timeout vs. hdev race
- LP: #1592552
  * Bluetooth: vhci: purge unhandled skbs
- LP: #1592552
  * cpuidle: Indicate when a device has been unregistered
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Use clkdev_create()
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Remove clock tree on error path
- LP: #1592552
  * [media] media: v4l2-compat-ioctl32: fix missing reserved field copy in
put_v4l2_create32
- LP: #1592552
  * scsi: Add intermediate STARGET_REMOVE state to scsi_target_state
- LP: #1592552
  * drm/i915/dsi: fix CHV dsi encoder hardware state readout on port C
- LP: #1592552
  * usb: f_mass_storage: test whether thread is running before starting
another
- LP: #1592552
  * hwmon: (ads7828) Enable internal reference
- LP: #1592552
  * ath10k: fix rx_channel during hw reconfigure
- LP: #1592552
  * Bluetooth: vhci: Fix race at creating hci device
- LP: #1592552
  * powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- LP: #1592552
  * PM / Runtime: Fix error path in pm_runtime_force_resume()
- LP: #1592552
  * crypto: s5p-sss - Fix missed interrupts when working with 8 kB blocks
- LP: #1592552
  * ath9k: Add a module parameter to invert LED polarity.
- LP: #1592552
  * ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- LP: #1592552
  * pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- LP: #1592552
  * btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
btrfs_ioctl
- LP: #1592552
  * serial: 8250_pci: fix divide error bug if baud rate is 0
- LP: #1592552
  * TTY: n_gsm, fix false positive WARN_ON
- LP: #1592552
  * staging: comedi: das1800: fix possible NULL dereference
- LP: #1592552
  * arm/arm64: KVM: Enforce Break-Before-Make on Stage-2 page tables
- LP: #1592552
  * KVM: x86: fix ordering of cr0 initialization code in vmx_cpu_reset
- LP: #1592552
  * aacraid: Relinquish CPU during timeout wait
- LP: #1592552
  * aacraid: Fix for aac_command_thread hang
- LP: #1592552
  * aacraid: Fix for KDUMP driver hang
- LP: #1592552
  * ext4: fix hang when processing corrupted orphaned 

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-vivid - 3.19.0-65.73~14.04.1

---
linux-lts-vivid (3.19.0-65.73~14.04.1) trusty; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1596643

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070

 -- Benjamin M Romer   Mon, 27 Jun 2016
12:37:48 -0400

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

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

Title:
  CVE-2016-3070

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

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-wily - 4.2.0-42.49~14.04.1

---
linux-lts-wily (4.2.0-42.49~14.04.1) trusty; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1597108

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * Revert "scsi: fix soft lockup in scsi_remove_target() on module
removal"
- LP: #1592552
  * ath10k: fix firmware assert in monitor mode
- LP: #1592552
  * drm/i915: Fix race condition in intel_dp_destroy_mst_connector()
- LP: #1592552
  * ath10k: fix debugfs pktlog_filter write
- LP: #1592552
  * drm/i915: Call intel_dp_mst_resume() before resuming displays
- LP: #1592552
  * ARM: mvebu: fix GPIO config on the Linksys boards
- LP: #1592552
  * ath5k: Change led pin configuration for compaq c700 laptop
- LP: #1592552, #972604
  * xfs: disallow rw remount on fs with unknown ro-compat features
- LP: #1592552
  * xfs: Don't wrap growfs AGFL indexes
- LP: #1592552
  * rtlwifi: rtl8723be: Add antenna select module parameter
- LP: #1592552
  * rtlwifi: btcoexist: Implement antenna selection
- LP: #1592552
  * drm/gma500: Fix possible out of bounds read
- LP: #1592552
  * Bluetooth: vhci: fix open_timeout vs. hdev race
- LP: #1592552
  * Bluetooth: vhci: purge unhandled skbs
- LP: #1592552
  * cpuidle: Indicate when a device has been unregistered
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Use clkdev_create()
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Remove clock tree on error path
- LP: #1592552
  * [media] media: v4l2-compat-ioctl32: fix missing reserved field copy in
put_v4l2_create32
- LP: #1592552
  * scsi: Add intermediate STARGET_REMOVE state to scsi_target_state
- LP: #1592552
  * drm/i915/dsi: fix CHV dsi encoder hardware state readout on port C
- LP: #1592552
  * usb: f_mass_storage: test whether thread is running before starting
another
- LP: #1592552
  * hwmon: (ads7828) Enable internal reference
- LP: #1592552
  * ath10k: fix rx_channel during hw reconfigure
- LP: #1592552
  * Bluetooth: vhci: Fix race at creating hci device
- LP: #1592552
  * powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- LP: #1592552
  * PM / Runtime: Fix error path in pm_runtime_force_resume()
- LP: #1592552
  * crypto: s5p-sss - Fix missed interrupts when working with 8 kB blocks
- LP: #1592552
  * ath9k: Add a module parameter to invert LED polarity.
- LP: #1592552
  * ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- LP: #1592552
  * pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- LP: #1592552
  * btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
btrfs_ioctl
- LP: #1592552
  * serial: 8250_pci: fix divide error bug if baud rate is 0
- LP: #1592552
  * TTY: n_gsm, fix false positive WARN_ON
- LP: #1592552
  * staging: comedi: das1800: fix possible NULL dereference
- LP: #1592552
  * arm/arm64: KVM: Enforce Break-Before-Make on Stage-2 page tables
- LP: #1592552
  * KVM: x86: fix ordering of cr0 initialization code in vmx_cpu_reset
- LP: #1592552
  * aacraid: Relinquish CPU during timeout wait
- LP: #1592552
  * aacraid: Fix for aac_command_thread hang
- LP: #1592552
  * aacraid: Fix for KDUMP driver hang
- LP: #1592552
  * ext4: fix hang when processing corrupted orphaned 

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-utopic -
3.16.0-77.99~14.04.1

---
linux-lts-utopic (3.16.0-77.99~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597047

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587087
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587087

 -- Kamal Mostafa   Tue, 28 Jun 2016 11:43:10 -0700

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

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

Title:
  CVE-2016-3070

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

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

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

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

Title:
  CVE-2016-3070

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

[Kernel-packages] [Bug 1587087] Re: OOM in guest Ubuntu with inflated balloon

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-utopic -
3.16.0-77.99~14.04.1

---
linux-lts-utopic (3.16.0-77.99~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597047

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587087
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587087

 -- Kamal Mostafa   Tue, 28 Jun 2016 11:43:10 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  OOM in guest Ubuntu with inflated balloon

Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest.
  Inside the Linux guest a balloon consumes memory in accordance with
  commands performed on the host side in QEMU. Rapid increases of memory 
consumption
  inside the guest may end up with guest OOMs
  since memory locked by balloon couldn’t be returned to the guest OS/vm in 
time.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5
  Author: Raushaniya Maksudova 
  Date: Mon Nov 10 09:36:29 2014 +1030
  virtio_balloon: free some memory from balloon on OOM

  Excessive virtio_balloon inflation can cause invocation of OOM-killer,
  when Linux is under severe memory pressure. Various mechanisms are
  responsible for correct virtio_balloon memory management. Nevertheless
  it is often the case that these control tools does not have enough time
  to react on fast changing memory load. As a result OS runs out of memory
  and invokes OOM-killer. The balancing of memory by use of the virtio
  balloon should not cause the termination of processes while there are
  pages in the balloon. Now there is no way for virtio balloon driver to
  free some memory at the last moment before some process will be get
  killed by OOM-killer.

  This does not provide a security breach as balloon itself is running
  inside guest OS and is working in the cooperation with the host. Thus
  some improvements from guest side should be considered as normal.

  To solve the problem, introduce a virtio_balloon callback which is
  expected to be called from the oom notifier call chain in out_of_memory()
  function. If virtio balloon could release some memory, it will make
  the system to return and retry the allocation that forced the out of
  memory killer to run.

  Allocate virtio feature bit for this: it is not set by default,
  the the guest will not deflate virtio balloon on OOM without explicit
  permission from host.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 

[Kernel-packages] [Bug 1596643] Re: linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-vivid - 3.19.0-65.73~14.04.1

---
linux-lts-vivid (3.19.0-65.73~14.04.1) trusty; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1596643

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070

 -- Benjamin M Romer   Mon, 27 Jun 2016
12:37:48 -0400

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597047] Re: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-utopic -
3.16.0-77.99~14.04.1

---
linux-lts-utopic (3.16.0-77.99~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597047

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587087
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587087

 -- Kamal Mostafa   Tue, 28 Jun 2016 11:43:10 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[Kernel-packages] [Bug 1596643] Re: linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-65.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597047] Re: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

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

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

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

[Kernel-packages] [Bug 1597060] Re: linux: 3.13.0-92.139 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 3.13.0-92.139 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

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

Title:
  linux: MokSBState is ignored

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

Bug description:
  Ubuntu-4.4.0-20.36 was released with signed module enforcement
  enabled, but contained no way of disabling secure boot for DKMS.
  Without these kernel patches it is possible to get your machine in an
  unbootable state, especially if you don't have a fallback kernel.

  This patch set implements the ability to disable secure boot on demand
  from user space (with some password shennaigans). If one boots in
  secure boot mode and then installs a third party module (such as
  DKMS), then a dialog is displayed giving the user an option to disable
  secure boot, thereby also disabling module signature verification.
  Patch 1/2 is a scaffold patch of which only the GUID macros are
  actually used. The rest of the code is fenced by
  CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series.
  Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3
  simply prints a bit more informative state information.

  Information regarding secure boot and signed module enforcement will
  appear in the kernel log thusly:

  'Secure boot enabled' - normal secure boot operation with signed module 
enforcement.
  'Secure boot MOKSBState disabled' - UEFI Secure boot state has been 
over-ridden by MOKSBState. No signed module enforcement.

  In the absense of a 'Secure boot' string assume that secure boot is
  disabled or does not exist.

To manage notifications about this bug go 

[Kernel-packages] [Bug 1572624] Re: Backport patch to abort syscalls in active transactions

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  Backport patch to abort syscalls in active transactions

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

Bug description:
  == Comment: #0 - Tulio Magno Quites Machado Filho - 2016-02-23 12:47:09 ==
  ---Problem Description---
  This is happening on Ubuntu 14.04.3.
  User is creating stack structure using C++ transactional memory extension:

  int Pop(int)
  {
  int ret = 0;
  __transaction_atomic
  {
  if(!stack_.empty())
  {
  ret = stack_.top();
  stack_.pop();
  } else
  ret = -1;
  }
  return ret;
  }

  While evaluating if(!stack_.empty()), this code calls a libitm function (GCC 
code), which calls malloc (glibc code) which ends up calling futex (a syscall).
  A syscall inside a transaction is forbidden by the kernel, but there is 
nothing the user can do to avoid this syscall.

  This will hang the user application inside the malloc(), which would
  be waiting for the futex to return.

  Ubuntu 14.04 provides glibc 2.19, which is too old to know about HTM.
  And this is probably happening with other libraries as well.

  Backporting commit b4b56f9e would solve this issue.

  ---uname output---
  Linux 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 16:06:09 UTC 2015 

[Kernel-packages] [Bug 1595628] Re: scsi-modules udeb should include pm80xx

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  scsi-modules udeb should include pm80xx

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The pm80xx kernel module, which is needed for my Adaptec PMC-Sierra PM8018 
SAS HBA controller, is not available in the trusty-update installer initrd.
  The trusy-update installer is running 3.13.0-85-generic and 
linux-image-extra-3.13.0-85-generic contains the module.

  Please add the kernel module to the initrd.

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

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

[Kernel-packages] [Bug 1592429] Re: trusty kernel crash in OOM killer related to cgroups

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  trusty kernel crash in OOM killer related to cgroups

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

Bug description:
  The trusty kernel can crash if the OOM killer kills processes which
  have reached a memory limit imposed by cgroups. More details can be
  found in this blog post:

  https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-
  bug

  The upstream patch series which ultimately landed in 3.14 is available
  at:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0

  One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is
  already part of the trusty kernel.

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

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

[Kernel-packages] [Bug 1587089] Re: Hide "ballooned" memory from /proc in guest Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  Hide "ballooned" memory from /proc in guest Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Wily:
  In Progress

Bug description:
  There is QEMU/KVM and a Linux guest running inside the guest. The amount
  of memory available for guest could be adjusted by balloon for better
  host scalability. The problem that this change is visible for end-user
  actually using the guest. This could (potentially) result in lawsuite
  from the end-user to hosting provides. 

  The problem is addressed in mainstream Linux with the following patch
  set:

  commit 997e120843e82609c8d99a9d5714e6cf91e14cbe
  Author: Denis V. Lunev 
  Date:   Thu Aug 20 00:49:49 2015 +0300
  virtio_balloon: do not change memory amount visible via /proc/meminfo
  
  Balloon device is frequently used as a mean of cooperative memory control
  in between guest and host to manage memory overcommitment. This is the
  typical case for any hosting workload when KVM guest is provided for
  end-user.
  
  Though there is a problem in this setup. The end-user and hosting provider
  have signed SLA agreement in which some amount of memory is guaranted for
  the guest. The good thing is that this memory will be given to the guest
  when the guest will really need it (f.e. with OOM in guest and with
  VIRTIO_BALLOON_F_DEFLATE_ON_OOM configuration flag set). The bad thing
  is that end-user does not know this.
  
  Balloon by default reduce the amount of memory exposed to the end-user
  each time when 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

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

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

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

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

Bug description:
  This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot

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

  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
  for platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:

  sudo mokutil --disable-validation
  sudo reboot

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

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

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

Bug description:
  This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot

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

  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
  for platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:

  sudo mokutil --disable-validation
  sudo reboot

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

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

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

[Launchpad Bug Tracker]

This bug was fixed in the package linux-raspi2 - 4.2.0-1034.44

---
linux-raspi2 (4.2.0-1034.44) wily; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597107

  [ Ubuntu: 4.2.0-42.49 ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691
  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221
  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628
  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * Revert "scsi: fix soft lockup in scsi_remove_target() on module
removal"
- LP: #1592552
  * ath10k: fix firmware assert in monitor mode
- LP: #1592552
  * drm/i915: Fix race condition in intel_dp_destroy_mst_connector()
- LP: #1592552
  * ath10k: fix debugfs pktlog_filter write
- LP: #1592552
  * drm/i915: Call intel_dp_mst_resume() before resuming displays
- LP: #1592552
  * ARM: mvebu: fix GPIO config on the Linksys boards
- LP: #1592552
  * ath5k: Change led pin configuration for compaq c700 laptop
- LP: #1592552, #972604
  * xfs: disallow rw remount on fs with unknown ro-compat features
- LP: #1592552
  * xfs: Don't wrap growfs AGFL indexes
- LP: #1592552
  * rtlwifi: rtl8723be: Add antenna select module parameter
- LP: #1592552
  * rtlwifi: btcoexist: Implement antenna selection
- LP: #1592552
  * drm/gma500: Fix possible out of bounds read
- LP: #1592552
  * Bluetooth: vhci: fix open_timeout vs. hdev race
- LP: #1592552
  * Bluetooth: vhci: purge unhandled skbs
- LP: #1592552
  * cpuidle: Indicate when a device has been unregistered
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Use clkdev_create()
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Remove clock tree on error path
- LP: #1592552
  * [media] media: v4l2-compat-ioctl32: fix missing reserved field copy in
put_v4l2_create32
- LP: #1592552
  * scsi: Add intermediate STARGET_REMOVE state to scsi_target_state
- LP: #1592552
  * drm/i915/dsi: fix CHV dsi encoder hardware state readout on port C
- LP: #1592552
  * usb: f_mass_storage: test whether thread is running before starting
another
- LP: #1592552
  * hwmon: (ads7828) Enable internal reference
- LP: #1592552
  * ath10k: fix rx_channel during hw reconfigure
- LP: #1592552
  * Bluetooth: vhci: Fix race at creating hci device
- LP: #1592552
  * powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- LP: #1592552
  * PM / Runtime: Fix error path in pm_runtime_force_resume()
- LP: #1592552
  * crypto: s5p-sss - Fix missed interrupts when working with 8 kB blocks
- LP: #1592552
  * ath9k: Add a module parameter to invert LED polarity.
- LP: #1592552
  * ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- LP: #1592552
  * pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- LP: #1592552
  * btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
btrfs_ioctl
- LP: #1592552
  * serial: 8250_pci: fix divide error bug if baud rate is 0
- LP: #1592552
  * TTY: n_gsm, fix false positive WARN_ON
- LP: #1592552
  * staging: comedi: das1800: fix possible NULL dereference
- LP: #1592552
  * arm/arm64: KVM: Enforce Break-Before-Make on Stage-2 page tables
- LP: #1592552
  * KVM: x86: fix ordering of cr0 initialization code in vmx_cpu_reset
- LP: #1592552
  * aacraid: Relinquish CPU during timeout wait
- LP: #1592552
  * aacraid: Fix for aac_command_thread hang
- LP: #1592552
  * aacraid: Fix for KDUMP driver hang
- LP: #1592552
  * ext4: fix hang when processing corrupted orphaned inode list
- LP: #1592552
  * MIPS: ath79: make bootconsole wait for both THRE and TEMT
- LP: 

[Kernel-packages] [Bug 1597060] Re: linux: 3.13.0-92.139 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-92.139

---
linux (3.13.0-92.139) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597060

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1566221, #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1566221, #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1566221, #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075
  * SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility
- LP: #1593075
  * [Config] CONFIG_EFI=n for arm64
- LP: #1566221

  [ Upstream Kernel Changes ]

  * powerpc/tm: Abort syscalls in active transactions
- LP: #1572624
  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * efi: Add separate 32-bit/64-bit definitions
- LP: #1566221
  * x86/efi: Build our own EFI services pointer table
- LP: #1566221
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070
  * oom_kill: change oom_kill.c to use for_each_thread()
- LP: #1592429
  * oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
- LP: #1592429
  * oom_kill: add rcu_read_lock() into find_lock_task_mm()
- LP: #1592429
  * virtio_balloon: return the amount of freed memory from leak_balloon()
- LP: #1587089
  * virtio_balloon: free some memory from balloon on OOM
- LP: #1587089
  * virtio_ballon: change stub of release_pages_by_pfn
- LP: #1587089
  * virtio_balloon: do not change memory amount visible via /proc/meminfo
- LP: #1587089

 -- Kamal Mostafa   Tue, 28 Jun 2016 12:40:49 -0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3070

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

Title:
  linux: 3.13.0-92.139 -proposed tracker

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.2.0-42.49

---
linux (4.2.0-42.49) wily; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1597053

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * Revert "scsi: fix soft lockup in scsi_remove_target() on module
removal"
- LP: #1592552
  * ath10k: fix firmware assert in monitor mode
- LP: #1592552
  * drm/i915: Fix race condition in intel_dp_destroy_mst_connector()
- LP: #1592552
  * ath10k: fix debugfs pktlog_filter write
- LP: #1592552
  * drm/i915: Call intel_dp_mst_resume() before resuming displays
- LP: #1592552
  * ARM: mvebu: fix GPIO config on the Linksys boards
- LP: #1592552
  * ath5k: Change led pin configuration for compaq c700 laptop
- LP: #1592552, #972604
  * xfs: disallow rw remount on fs with unknown ro-compat features
- LP: #1592552
  * xfs: Don't wrap growfs AGFL indexes
- LP: #1592552
  * rtlwifi: rtl8723be: Add antenna select module parameter
- LP: #1592552
  * rtlwifi: btcoexist: Implement antenna selection
- LP: #1592552
  * drm/gma500: Fix possible out of bounds read
- LP: #1592552
  * Bluetooth: vhci: fix open_timeout vs. hdev race
- LP: #1592552
  * Bluetooth: vhci: purge unhandled skbs
- LP: #1592552
  * cpuidle: Indicate when a device has been unregistered
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Use clkdev_create()
- LP: #1592552
  * mfd: intel_quark_i2c_gpio: Remove clock tree on error path
- LP: #1592552
  * [media] media: v4l2-compat-ioctl32: fix missing reserved field copy in
put_v4l2_create32
- LP: #1592552
  * scsi: Add intermediate STARGET_REMOVE state to scsi_target_state
- LP: #1592552
  * drm/i915/dsi: fix CHV dsi encoder hardware state readout on port C
- LP: #1592552
  * usb: f_mass_storage: test whether thread is running before starting
another
- LP: #1592552
  * hwmon: (ads7828) Enable internal reference
- LP: #1592552
  * ath10k: fix rx_channel during hw reconfigure
- LP: #1592552
  * Bluetooth: vhci: Fix race at creating hci device
- LP: #1592552
  * powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- LP: #1592552
  * PM / Runtime: Fix error path in pm_runtime_force_resume()
- LP: #1592552
  * crypto: s5p-sss - Fix missed interrupts when working with 8 kB blocks
- LP: #1592552
  * ath9k: Add a module parameter to invert LED polarity.
- LP: #1592552
  * ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- LP: #1592552
  * pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- LP: #1592552
  * btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
btrfs_ioctl
- LP: #1592552
  * serial: 8250_pci: fix divide error bug if baud rate is 0
- LP: #1592552
  * TTY: n_gsm, fix false positive WARN_ON
- LP: #1592552
  * staging: comedi: das1800: fix possible NULL dereference
- LP: #1592552
  * arm/arm64: KVM: Enforce Break-Before-Make on Stage-2 page tables
- LP: #1592552
  * KVM: x86: fix ordering of cr0 initialization code in vmx_cpu_reset
- LP: #1592552
  * aacraid: Relinquish CPU during timeout wait
- LP: #1592552
  * aacraid: Fix for aac_command_thread hang
- LP: #1592552
  * aacraid: Fix for KDUMP driver hang
- LP: #1592552
  * ext4: fix hang when processing corrupted orphaned inode list
- LP: #1592552
  * 

[Kernel-packages] [Bug 1596469] Re: [Bug]tpm initialization fails on x86

[Launchpad Bug Tracker]

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

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

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1602449

  * nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for supported chipset before booting fbdev off the hw

linux (4.4.0-30.49) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597897

  * FCP devices are not detected correctly nor deterministically (LP: #1567602)
- scsi_dh_alua: Disable ALUA handling for non-disk devices
- scsi_dh_alua: Use vpd_pg83 information
- scsi_dh_alua: improved logging
- scsi_dh_alua: sanitze sense code handling
- scsi_dh_alua: use standard logging functions
- scsi_dh_alua: return standard SCSI return codes in submit_rtpg
- scsi_dh_alua: fixup description of stpg_endio()
- scsi_dh_alua: use flag for RTPG extended header
- scsi_dh_alua: use unaligned access macros
- scsi_dh_alua: rework alua_check_tpgs() to return the tpgs mode
- scsi_dh_alua: simplify sense code handling
- scsi: Add scsi_vpd_lun_id()
- scsi: Add scsi_vpd_tpg_id()
- scsi_dh_alua: use scsi_vpd_tpg_id()
- scsi_dh_alua: Remove stale variables
- scsi_dh_alua: Pass buffer as function argument
- scsi_dh_alua: separate out alua_stpg()
- scsi_dh_alua: Make stpg synchronous
- scsi_dh_alua: call alua_rtpg() if stpg fails
- scsi_dh_alua: switch to scsi_execute_req_flags()
- scsi_dh_alua: allocate RTPG buffer separately
- scsi_dh_alua: Use separate alua_port_group structure
- scsi_dh_alua: use unique device id
- scsi_dh_alua: simplify alua_initialize()
- revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach 
should
  succeed while TPG is transitioning")
- scsi_dh_alua: move optimize_stpg evaluation
- scsi_dh_alua: remove 'rel_port' from alua_dh_data structure
- scsi_dh_alua: Use workqueue for RTPG
- scsi_dh_alua: Allow workqueue to run synchronously
- scsi_dh_alua: Add new blacklist flag 'BLIST_SYNC_ALUA'
- scsi_dh_alua: Recheck state on unit attention
- scsi_dh_alua: update all port states
- scsi_dh_alua: Send TEST UNIT READY to poll for transitioning
- scsi_dh_alua: do not fail for unknown VPD identification

linux (4.4.0-29.48) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597015

  * Wireless hotkey fails on Dell XPS 15 9550 (LP: #1589886)
- intel-hid: new hid event driver for hotkeys
- intel-hid: fix incorrect entries in intel_hid_keymap
- intel-hid: allocate correct amount of memory for private struct
- intel-hid: add a workaround to ignore an event after waking up from S4.
- [Config] CONFIG_INTEL_HID_EVENT=m

  * cgroupfs mounts can hang (LP: #1588056)
- Revert "UBUNTU: SAUCE: (namespace) mqueue: Super blocks must be owned by 
the
  user ns which owns the ipc ns"
- Revert "UBUNTU: SAUCE: kernfs: Do not match superblock in another user
  namespace when mounting"
- Revert "UBUNTU: SAUCE: cgroup: Use a new super block when mounting in a
  cgroup namespace"
- (namespace) bpf: Use mount_nodev not mount_ns to mount the bpf filesystem
- (namespace) bpf, inode: disallow userns mounts
- (namespace) ipc: Initialize ipc_namespace->user_ns early.
- (namespace) vfs: Pass data, ns, and ns->userns to mount_ns
- SAUCE: (namespace) Sync with upstream s_user_ns patches
- (namespace) kernfs: The cgroup filesystem also benefits from SB_I_NOEXEC
- (namespace) ipc/mqueue: The mqueue filesystem should never contain
  executables

  * KVM system crashes after starting guest (LP: #1596635)
- xhci: Cleanup only when releasing primary hcd

  * Upstream patch "crypto: vmx - IV size failing on skcipher API" for Ubuntu
16.04 (LP: #1596557)
- crypto: vmx - IV size failing on skcipher API

  * [Bug]tpm initialization fails on x86 (LP: #1596469)
- tpm_crb: drop struct resource res from struct crb_priv
- tpm_crb: fix mapping of the buffers

  * Device shutdown notification for CAPI Flash cards (LP: #1592114)
- cxlflash: Fix regression issue with re-ordering patch
- cxlflash: Fix to drain operations from previous reset
- cxlflash: Add device dependent flags
- cxlflash: Shutdown notify support for CXL Flash cards

  * scsi-modules udeb should include pm80xx (LP: #1595628)
- [Config] Add pm80xx scsi driver to d-i

  * Sync up latest relevant upstream bug fixes (LP: #1594871)
- SAUCE: (noup) Update zfs to 0.6.5.6-0ubuntu10

  * Cannot compile module tda10071 (LP: #1592531)
- [media] tda10071: Fix dependency to REGMAP_I2C

  * lsvpd doesn't show correct location code for devices attached to a CAPI card
(LP: #1594847)
- cxl: Make vPHB device node match adapter's

  * enable CRC32 and AES ARM64 by default or as module (LP: #1594455)
- [Config] Enable arm64 AES and CRC32 

[Kernel-packages] [Bug 1594847] Re: lsvpd doesn't show correct location code for devices attached to a CAPI card

[Launchpad Bug Tracker]

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

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

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1602449

  * nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for supported chipset before booting fbdev off the hw

linux (4.4.0-30.49) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597897

  * FCP devices are not detected correctly nor deterministically (LP: #1567602)
- scsi_dh_alua: Disable ALUA handling for non-disk devices
- scsi_dh_alua: Use vpd_pg83 information
- scsi_dh_alua: improved logging
- scsi_dh_alua: sanitze sense code handling
- scsi_dh_alua: use standard logging functions
- scsi_dh_alua: return standard SCSI return codes in submit_rtpg
- scsi_dh_alua: fixup description of stpg_endio()
- scsi_dh_alua: use flag for RTPG extended header
- scsi_dh_alua: use unaligned access macros
- scsi_dh_alua: rework alua_check_tpgs() to return the tpgs mode
- scsi_dh_alua: simplify sense code handling
- scsi: Add scsi_vpd_lun_id()
- scsi: Add scsi_vpd_tpg_id()
- scsi_dh_alua: use scsi_vpd_tpg_id()
- scsi_dh_alua: Remove stale variables
- scsi_dh_alua: Pass buffer as function argument
- scsi_dh_alua: separate out alua_stpg()
- scsi_dh_alua: Make stpg synchronous
- scsi_dh_alua: call alua_rtpg() if stpg fails
- scsi_dh_alua: switch to scsi_execute_req_flags()
- scsi_dh_alua: allocate RTPG buffer separately
- scsi_dh_alua: Use separate alua_port_group structure
- scsi_dh_alua: use unique device id
- scsi_dh_alua: simplify alua_initialize()
- revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach 
should
  succeed while TPG is transitioning")
- scsi_dh_alua: move optimize_stpg evaluation
- scsi_dh_alua: remove 'rel_port' from alua_dh_data structure
- scsi_dh_alua: Use workqueue for RTPG
- scsi_dh_alua: Allow workqueue to run synchronously
- scsi_dh_alua: Add new blacklist flag 'BLIST_SYNC_ALUA'
- scsi_dh_alua: Recheck state on unit attention
- scsi_dh_alua: update all port states
- scsi_dh_alua: Send TEST UNIT READY to poll for transitioning
- scsi_dh_alua: do not fail for unknown VPD identification

linux (4.4.0-29.48) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597015

  * Wireless hotkey fails on Dell XPS 15 9550 (LP: #1589886)
- intel-hid: new hid event driver for hotkeys
- intel-hid: fix incorrect entries in intel_hid_keymap
- intel-hid: allocate correct amount of memory for private struct
- intel-hid: add a workaround to ignore an event after waking up from S4.
- [Config] CONFIG_INTEL_HID_EVENT=m

  * cgroupfs mounts can hang (LP: #1588056)
- Revert "UBUNTU: SAUCE: (namespace) mqueue: Super blocks must be owned by 
the
  user ns which owns the ipc ns"
- Revert "UBUNTU: SAUCE: kernfs: Do not match superblock in another user
  namespace when mounting"
- Revert "UBUNTU: SAUCE: cgroup: Use a new super block when mounting in a
  cgroup namespace"
- (namespace) bpf: Use mount_nodev not mount_ns to mount the bpf filesystem
- (namespace) bpf, inode: disallow userns mounts
- (namespace) ipc: Initialize ipc_namespace->user_ns early.
- (namespace) vfs: Pass data, ns, and ns->userns to mount_ns
- SAUCE: (namespace) Sync with upstream s_user_ns patches
- (namespace) kernfs: The cgroup filesystem also benefits from SB_I_NOEXEC
- (namespace) ipc/mqueue: The mqueue filesystem should never contain
  executables

  * KVM system crashes after starting guest (LP: #1596635)
- xhci: Cleanup only when releasing primary hcd

  * Upstream patch "crypto: vmx - IV size failing on skcipher API" for Ubuntu
16.04 (LP: #1596557)
- crypto: vmx - IV size failing on skcipher API

  * [Bug]tpm initialization fails on x86 (LP: #1596469)
- tpm_crb: drop struct resource res from struct crb_priv
- tpm_crb: fix mapping of the buffers

  * Device shutdown notification for CAPI Flash cards (LP: #1592114)
- cxlflash: Fix regression issue with re-ordering patch
- cxlflash: Fix to drain operations from previous reset
- cxlflash: Add device dependent flags
- cxlflash: Shutdown notify support for CXL Flash cards

  * scsi-modules udeb should include pm80xx (LP: #1595628)
- [Config] Add pm80xx scsi driver to d-i

  * Sync up latest relevant upstream bug fixes (LP: #1594871)
- SAUCE: (noup) Update zfs to 0.6.5.6-0ubuntu10

  * Cannot compile module tda10071 (LP: #1592531)
- [media] tda10071: Fix dependency to REGMAP_I2C

  * lsvpd doesn't show correct location code for devices attached to a CAPI card
(LP: #1594847)
- cxl: Make vPHB device node match adapter's

  * enable CRC32 and AES ARM64 by default or as module (LP: #1594455)
- [Config] Enable arm64 AES and CRC32 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-65.73

---
linux (3.19.0-65.73) vivid; urgency=low

  [ Ben Romer ]

  * Release Tracking Bug
- LP: #1596631

  [ Josh Boyer ]

  * SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP: #1566221
  * SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI
- LP: #1566221
  * SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot
- LP: #1571691
  * SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode
- LP: #1571691

  [ Matthew Garrett ]

  * SAUCE: UEFI: Add secure_modules() call
- LP: #1566221
  * SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled
- LP: #1566221
  * SAUCE: UEFI: x86: Lock down IO port access when module security is
enabled
- LP: #1566221
  * SAUCE: UEFI: ACPI: Limit access to custom_method
- LP: #1566221
  * SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading
is restricted
- LP: #1566221
  * SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is
restricted
- LP: #1566221
  * SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module
loading restrictions
- LP: #1566221
  * SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted
- LP: #1566221
  * SAUCE: UEFI: Add option to automatically enforce module signatures when
in Secure Boot mode
- LP: #1566221

  [ Stefan Bader ]

  * [Config] Add pm80xx scsi driver to d-i
- LP: #1595628

  [ Tim Gardner ]

  * [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
  * SAUCE: UEFI: Display MOKSBState when disabled
- LP: #1571691
  * SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl
- LP: #1593075

  [ Upstream Kernel Changes ]

  * HID: core: prevent out-of-bound readings
- LP: #1579190
  * mm: migrate dirty page without clear_page_dirty_for_io etc
- LP: #1581865
- CVE-2016-3070

 -- Benjamin M Romer   Mon, 27 Jun 2016
12:37:48 -0400

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

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

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

Bug description:
  This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot

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

  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
  for platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:

  sudo mokutil --disable-validation
  sudo reboot

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

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