[Kernel-packages] [Bug 1690395] Re: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen

[Fabio Kung]

Nevermind, closing. I can't reproduce this anymore, so it was probably
not related to the kernel version.

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

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

Title:
  CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th
  gen

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Once the CPU fan is turned on, it never turns back down, even when
  things have already cooled down and CPU usage is low (<2%) for 5+
  minutes.

  The same cannot be reproduced with the previous kernel version
  (4.10.0.19.21), on the same machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fkung  2121 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri May 12 08:19:29 2017
  HibernationDevice: RESUME=UUID=8e5a26ba-3ea3-4831-88ba-66803bdf9d45
  InstallationDate: Installed on 2017-04-06 (35 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HR000FUS
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-04 (7 days ago)
  dmi.bios.date: 12/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET21W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR000FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET21W(1.06):bd12/26/2016:svnLENOVO:pn20HR000FUS:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR000FUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HR000FUS
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1690914] Re: [Regression] NUMA_BALANCING disabled on arm64

[dann frazier]

** Description changed:

  [Impact]
- CONFIG_NUMA_BALANCING and CONFIG_NUMA_BALANCING_DEFAULT_ENABLED were both set 
to =y in hwe-x/hwe-y. This changed to =n in hwe-z, unintentionally as far as I 
can tell. This can lead to performance degradation on NUMA-based arm64 systems 
when processes migrate, and their memory accesses now suffer additional latency.
+ CONFIG_NUMA_BALANCING and CONFIG_NUMA_BALANCING_DEFAULT_ENABLED were both set 
to =y in hwe-x/hwe-y. This changed to =n in hwe-z, unintentionally as far as I 
can tell. This can lead to performance degradation on NUMA-based arm64 systems 
when threads migrate, and their memory accesses now suffer additional latency.
  
  [Test Case]
  At a functional level:
  
- test -f /proc/sys/kernel/numabalancing
+ $ test -f /proc/sys/kernel/numabalancing
  
- Performance?
+ Performance:
+ 
+ $ perf bench numa -a
+ I didn't see any significant changes in the RAM-bw tests (expected).
+ For the convergence tests, I observed the following results, which appear to 
be all within reasonable variance.
+ 
+ Test | Balancing=n | Balancing=y
+ -
+ 1x3  | No-Converge | No-Converge
+ 1x4  | No-Converge | 0.576s
+ 1x6  | No-Converge | No-Converge
+ 2x3  | No-Converge | No-Converge
+ 3x3  | No-Converge | No-Converge
+ 4x4  | No-Converge | No-Converge
+ 4x4-NOTHP| No-Converge | No-Converge
+ 4x6  | No-Converge | No-Converge
+ 4x8  | No-Converge | No-Converge
+ 8x4  | No-Converge | No-Converge
+ 8x4-NOTHP| No-Converge | No-Converge
+ 3x1  | 0.848s  | 1.212s
+ 4x1  | 0.832s  | 0.712s
+ 8x1  | 0.792s  | 0.649s
+ 16x1 | 1.511s  | 1.485s
+ 32x1 | 0.750s  | 0.899s
+ 
+ Finally, for the bw tests, I see significant improvements across the board:
+ Test  | BW Improvement
+ -
+ === Process =
+ 2x1   |   2.2%
+ 3x1   |  61.4%
+ 4x1   |  25.0%
+ 8x1   | 104.6%
+ 8x1-NOTHP | 107.6%
+ 16x1  | 200.9%
+ === Thread ==
+ 4x1   |  10.9%
+ 8x1   | 107.4%
+ 16x1  | 230.7%
+ 32x1  | 239.7%
+ 2x3   |  13.5%
+ 4x4   |  69.2%
+ 4x6   |  84.4%
+ 4x8   |  79.7%
+ 4x8-NOTHP | 152.5%
+ 3x3   |  96.1%
+ 5x5   | 150.2%
+ 2x16  | 122.6%
+ 1x32  |  40.5%
  
  [Regression Risk]
+ This is changing a config only on arm64, so the regression risk will be 
limited to those platforms. The code we will be enabling on arm64 is already 
enabled on other architectures (!s390x), so has been tested within Ubuntu zesty 
already. This was previous also enabled on arm64 in hwe-x/hwe-y, so we can gain 
some confidence from that.
+ 
+ There is certainly a possibility that this negatively impacts
+ performance for certain workloads on NUMA/arm64 systems. If that occurs,
+ there is a sysctl that can be used to disable this feature.

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

Title:
  [Regression] NUMA_BALANCING disabled on arm64

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

Bug description:
  [Impact]
  CONFIG_NUMA_BALANCING and CONFIG_NUMA_BALANCING_DEFAULT_ENABLED were both set 
to =y in hwe-x/hwe-y. This changed to =n in hwe-z, unintentionally as far as I 
can tell. This can lead to performance degradation on NUMA-based arm64 systems 
when threads migrate, and their memory accesses now suffer additional latency.

  [Test Case]
  At a functional level:

  $ test -f /proc/sys/kernel/numabalancing

  Performance:

  $ perf bench numa -a
  I didn't see any significant changes in the RAM-bw tests (expected).
  For the convergence tests, I observed the following results, which appear to 
be all within reasonable variance.

  Test | Balancing=n | Balancing=y
  -
  1x3  | No-Converge | No-Converge
  1x4  | No-Converge | 0.576s
  1x6  | No-Converge | No-Converge
  2x3  | No-Converge | No-Converge
  3x3  | No-Converge | No-Converge
  4x4  | No-Converge | No-Converge
  4x4-NOTHP| No-Converge | No-Converge
  4x6  | No-Converge | No-Converge
  4x8  | No-Converge | No-Converge
  8x4  | No-Converge | No-Converge
  8x4-NOTHP| No-Converge | No-Converge
  3x1  | 0.848s  | 1.212s
  4x1  | 0.832s  | 0.712s
  8x1  | 0.792s  | 0.649s
  16x1 | 1.511s  | 1.485s
  32x1 | 0.750s  | 0.899s

  Finally, for the bw tests, I see significant improvements across the board:
  Test  | BW Improvement
  -
  === Process =
  2x1   |   2.2%
  3x1   |  61.4%
  4x1   |  25.0%
  8x1   | 104.6%
  8x1-NOTHP | 107.6%
  16x1  | 200.9%
  === Thread ==
  4x1   |  10.9%
  8x1   | 107.4%
  16x1  | 230.7%
  32x1  | 239.7%
  2x3   |  13.5%
  4x4   |  69.2%
  4x6 

[Kernel-packages] [Bug 1689359] Re: Target: Fix VERIFY_16, WRITE_VERIFY, VERIFY, and WRITE_VERIFY_16

[Manoj Iyer]

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

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

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

Title:
  Target: Fix VERIFY_16, WRITE_VERIFY, VERIFY, and WRITE_VERIFY_16

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  List of patches that is in regards to scsi commands.

  VERIFY_16 does not handle the returned CHECK_CONDITION properly
  resulting an in infinite loop.

  Fix VERIFY and WRITE VERIFY command parsing

  Use the value of the BYTCHK field to determine the size of the
  Data-Out buffer. For VERIFY, honor the VRPROTECT, DPO and FUA
  fields. This patch avoids that LIO complains about a mismatch
  between the expected transfer length and the SCSI CDB length
  if the value of the BYTCHK field is 0.

  WRITE_VERIFY_16 - Large volume groups such as AIX need this command. 
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 
   
  The target is for 16.04.02 Yakkety. Below are the links to the patches that 
need to be backported.

  target: Fix VERIFY_16 handling in sbc_parse_cdb
  https://patchwork.kernel.org/patch/9643687/

  target: Fix VERIFY and WRITE VERIFY command parsing
  https://patchwork.kernel.org/patch/9617875/

  target: Add WRITE_VERIFY_16
  https://patchwork.kernel.org/patch/9686085/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689359/+subscriptions

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

[Kernel-packages] [Bug 1689360] Re: TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly calculating base_command_size

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly
  calculating base_command_size

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  If there has BIDI data, its first iov[] will overwrite the last
  iov[] for se_cmd->t_data_sg.

  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
   Just have a system do workload using tcmu.
   
  Stack trace output:
   I have seen this in my environment:
  (gdb) print *((tcmulib_cmd->iovec)+0)
  $7 = {iov_base = 0x3fff7c3d, iov_len = 8192}
  (gdb) print *((tcmulib_cmd->iovec)+1)
  $3 = {iov_base = 0x3fff7c3da000, iov_len = 4096}
  (gdb) print *((tcmulib_cmd->iovec)+2)
  $4 = {iov_base = 0x3fff7c3dc000, iov_len = 16384}
  (gdb) print *((tcmulib_cmd->iovec)+3)
  $5 = {iov_base = 0x3fff7c3f7000, iov_len = 12288}
  (gdb) print *((tcmulib_cmd->iovec)+4)
  $6 = {iov_base = 0x1306e853c0028, iov_len = 128}  <--- bad pointer and length 
   
  cmu: Fix wrongly calculating of the base_command_size
  https://patchwork.kernel.org/patch/9687657/

  tcmu: Fix possible overwrite of t_data_sg's last iov[]
  https://patchwork.kernel.org/patch/9687565/

  tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI
  case

  https://patchwork.kernel.org/patch/9655423/

  This patch should also be a part of these fixes. WITH BIDI op fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689360/+subscriptions

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

[Kernel-packages] [Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

[Colin Ian King]

Good to see that it was a BIOS tweakable setting that could fix this.

BTW, the FADT is an ACPI table "Fixed ACPI Description Table" that
contains setting mainly for power management as well as other hardware
resources. See: http://wiki.osdev.org/FADT

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

Title:
  acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

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

Bug description:
  [0.183201] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-6-generic 3.16.0-6.11
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2878 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 29 04:47:24 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-04-27 (92 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=13144268-2374-4154-83f1-c35d81306190 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-6-generic N/A
   linux-backports-modules-3.16.0-6-generic  N/A
   linux-firmware1.132
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1691146] [NEW] linux: -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed block-proposed-zesty kernel-release-tracking-bug 
kernel-sru-cycle-2017.05.16-1 kernel-sru-master-kernel zesty

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

** Tags added: block-proposed

** Tags added: block-proposed-zesty

** Tags added: zesty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: 

[Kernel-packages] [Bug 1683277] Re: Mute key LED does not work on HP notebooks

[Steven H]

Hi Kai-Heng,

Unfortunately there was no change in the behavior. Thanks for the effort
though.

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

Title:
  Mute key LED does not work on HP notebooks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Envy 15 from 2015. HP Stream 11 from 2015 and HP Stream
  11 from 2016.

  Version-Release number of selected component (if applicable):

  
  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  
  Expected results:
  Mute state in software and LED in mute key toggle.

  
  Additional info:
  This happens on kernel 4.8, 4.9 and 4.10. I have not tested any other 
versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stevenh1659 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Apr 17 11:02:20 2017
  HibernationDevice: RESUME=UUID=2d246125-abf7-4945-9542-45b25fb8fcb2
  InstallationDate: Installed on 2016-09-13 (215 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81CC
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 60.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/13/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1645056] UdevDb.txt

[Taihsiang Ho]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1645056/+attachment/4877465/+files/UdevDb.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/1645056

Title:
  [Asus UX360UA] Unable to boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm unable to boot.

  With acpi=ht I get the following error at boot:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging 
request at 686d7e40

  WORKAROUND: Use kernel boot parameter:
  acpi=off

  ---
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mauro  2403 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7fd0455e-9721-4100-b1e6-8330040463c9
  InstallationDate: Installed on 2016-11-08 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical 
Mouse Controller (3-button)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi=off
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-11-26 (0 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 06/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1645056] Re: [Asus UX360UA] Unable to boot

[Taihsiang Ho]

The above are logs of my system booting with 4.4.0-75-generic. And the
kern.log shows something related to drm on skylake:


   1 May 16 08:26:41 mtlb kernel: [238539.431888] [ cut here 
]   
   
   2 May 16 08:26:41 mtlb kernel: [238539.431974] WARNING: CPU: 0 PID: 2319 at 
/build/linux-Hlembm/linux-4.4.0/ubuntu/i915/intel_pm.c:3675 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
   3 May 16 08:26:41 mtlb kernel: [238539.431980] WARN_ON(!wm_changed)
   4 May 16 08:26:41 mtlb kernel: [238539.431984] Modules linked in: 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nf_conntrack_netlink 
nfnetlink btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs  msdos jfs xfs 
libcrc32c cpuid hid_generic usbhid drbg ansi_cprng ctr ccm scsi_transport_iscsi 
veth pci_stub xfrm_user xfrm_algo xt_addrtype xt_conntrack br_netfilter rfcomm 
aufs ip6table_filter ip6_ tables xt_CHECKSUM iptable_mangle xt_tcpudp 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 
snd_hrtimer nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc ip
 table_filter ip_tables x_tables bnep binfmt_misc zfs(PO) zunicode(PO) 
zcommon(PO) znvpair(PO) spl(O) zavl(PO) r8712u(CE) joydev hid_multitouch arc4 
i2c_designware_platform i2c_designware_core asus_nb _wmi asus_wmi 
snd_soc_skl sparse_keymap snd_hda_codec_hdmi snd_soc_skl_ipc snd_hda_ext_core 
snd_hda_codec_conexant snd_soc_sst_ipc snd_hda_codec_generic snd_soc_sst_dsp 
snd_soc_core snd_compress ac97 _bus snd_pcm_dmaengine dw_dmac_core 
snd_hda_intel snd_hda_codec snd_hda_core iwlmvm uvcvideo videobuf2_vmalloc 
snd_hwdep mac80211 videobuf2_memops snd_pcm videobuf2_v4l2 videobuf2_core 
v4l2_common sn d_seq_midi snd_seq_midi_event videodev snd_rawmidi media 
snd_seq intel_rapl x86_pkg_temp_thermal intel_powerclamp btusb snd_seq_device 
coretemp btrtl iwlwifi snd_timer crct10dif_pclmul crc32_pclmul g 
hash_clmulni_intel cfg80211 aesni_intel aes_x86_64 lrw gf128mul snd glue_helper 
ablk_helper cryptd input_leds soundcore serio_raw processor_thermal_device 
mei_me intel_soc_dts_iosf idma64 shpchp mei  virt_dma intel_lpss_pci 
hci_uart int3403_thermal btbcm btqca btintel bluetooth int3402_thermal 
int3400_thermal intel_lpss_acpi intel_lpss tpm_crb int340x_thermal_zone 
acpi_thermal_rel acpi_pad mac_hi d kvm_intel kvm irqbypass parport_pc ppdev 
sunrpc lp parport autofs4 i915_bpo intel_ips i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi i2c_hid hid 
pinc trl_sunrisepoint pinctrl_intel video fjes [last unloaded: vboxdrv]
   5 May 16 08:26:41 mtlb kernel: [238539.432322] CPU: 0 PID: 2319 Comm: Xorg 
Tainted: PWC OE   4.4.0-75-generic #96-Ubuntu
   6 May 16 08:26:41 mtlb kernel: [238539.432327] Hardware name: ASUSTeK 
COMPUTER INC. UX360CA/UX360CA, BIOS UX360CA.202 02/17/2016
   7 May 16 08:26:41 mtlb kernel: [238539.432333]  0286 
a255aaa5 880078737920 813f8493
   8 May 16 08:26:41 mtlb kernel: [238539.432343]  880078737968 
c0246b58 880078737958 81081302
   9 May 16 08:26:41 mtlb kernel: [238539.432352]  88016a432000 
88016a44a148 88016a433000 88016e12c378
  10 May 16 08:26:41 mtlb kernel: [238539.432360] Call Trace:
  11 May 16 08:26:41 mtlb kernel: [238539.432377]  [] 
dump_stack+0x63/0x90
  12 May 16 08:26:41 mtlb kernel: [238539.432391]  [] 
warn_slowpath_common+0x82/0xc0
  13 May 16 08:26:41 mtlb kernel: [238539.432401]  [] 
warn_slowpath_fmt+0x5c/0x80
  14 May 16 08:26:41 mtlb kernel: [238539.432462]  [] 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
  15 May 16 08:26:41 mtlb kernel: [238539.432522]  [] 
skl_update_wm+0x185/0x610 [i915_bpo]
  16 May 16 08:26:41 mtlb kernel: [238539.432613]  [] ? 
intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo]
  17 May 16 08:26:41 mtlb kernel: [238539.432672]  [] 
intel_update_watermarks+0x1e/0x30 [i915_bpo]
  18 May 16 08:26:41 mtlb kernel: [238539.432761]  [] 
haswell_crtc_enable+0x761/0x8e0 [i915_bpo]
  19 May 16 08:26:41 mtlb kernel: [238539.432850]  [] 
intel_atomic_commit+0x5d6/0x14a0 [i915_bpo]
  20 May 16 08:26:41 mtlb kernel: [238539.432916]  [] ? 
drm_atomic_check_only+0x18e/0x590 [drm]
  21 May 16 08:26:41 mtlb kernel: [238539.432972]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  22 May 16 08:26:41 mtlb kernel: [238539.433003]  [] 
drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
  23 May 16 08:26:41 mtlb kernel: [238539.433051]  [] 
drm_mode_set_config_internal+0x62/0x100 [drm]
  24 May 16 08:26:41 mtlb kernel: [238539.433100]  [] 
drm_mode_setcrtc+0x3cc/0x4f0 [drm]
  25 May 16 08:26:41 mtlb kernel: [238539.433136]  [] 
drm_ioctl+0x152/0x540 [drm]
  26 May 16 08:26:41 mtlb kernel: [238539.433184]  [] ? 
drm_mode_setplane+0x1b0/0x1b0 [drm]
  27 May 16 08:26:41 mtlb kernel: [238539.433197]  [] 

[Kernel-packages] [Bug 1645056] WifiSyslog.txt

[Taihsiang Ho]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4877466/+files/WifiSyslog.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/1645056

Title:
  [Asus UX360UA] Unable to boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm unable to boot.

  With acpi=ht I get the following error at boot:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging 
request at 686d7e40

  WORKAROUND: Use kernel boot parameter:
  acpi=off

  ---
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mauro  2403 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7fd0455e-9721-4100-b1e6-8330040463c9
  InstallationDate: Installed on 2016-11-08 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical 
Mouse Controller (3-button)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi=off
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-11-26 (0 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 06/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Xenial)
 Assignee: Canonical Kernel (canonical-kernel) => Kleber Sacilotto de Souza 
(kleber-souza)

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+subscriptions

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

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  AACRAID for power9 platform

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689980/+subscriptions

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

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

[bugproxy]

--- Comment From b...@us.ibm.com 2017-05-16 10:48 EDT---
Can a test kernel be built for the two fixes that did get merged upstream?

target: Fix VERIFY_16 handling in sbc_parse_cdb
https://patchwork.kernel.org/patch/9643687/

target: Add WRITE_VERIFY_16
https://patchwork.kernel.org/patch/9686085/

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

Title:
  Target: Fix VERIFY_16, WRITE_VERIFY, VERIFY, and WRITE_VERIFY_16

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  List of patches that is in regards to scsi commands.

  VERIFY_16 does not handle the returned CHECK_CONDITION properly
  resulting an in infinite loop.

  Fix VERIFY and WRITE VERIFY command parsing

  Use the value of the BYTCHK field to determine the size of the
  Data-Out buffer. For VERIFY, honor the VRPROTECT, DPO and FUA
  fields. This patch avoids that LIO complains about a mismatch
  between the expected transfer length and the SCSI CDB length
  if the value of the BYTCHK field is 0.

  WRITE_VERIFY_16 - Large volume groups such as AIX need this command. 
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 
   
  The target is for 16.04.02 Yakkety. Below are the links to the patches that 
need to be backported.

  target: Fix VERIFY_16 handling in sbc_parse_cdb
  https://patchwork.kernel.org/patch/9643687/

  target: Fix VERIFY and WRITE VERIFY command parsing
  https://patchwork.kernel.org/patch/9617875/

  target: Add WRITE_VERIFY_16
  https://patchwork.kernel.org/patch/9686085/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689359/+subscriptions

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

[Kernel-packages] [Bug 1689661] Re: No PMU support for ACPI-based arm64 systems

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  No PMU support for ACPI-based arm64 systems

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

Bug description:
  [Impact]
  ACPI-based arm64 systems, such as the Qualcomm QDF2400 and the Hisilicon D05, 
do not currently have PMU support. This means that tools like perf are unable 
to use the built-in hardware event counters.

  [Test Case]
  On an ACPI-based arm64 system, run the following commands:

  sudo perf list pmu
  sudo perf list hw

  Without ACPI PMU support, these will be empty.

  [Regression Risk]
  The changes are restricted to ARM-specific code, other than an added enum 
value in linux/cpuhotplug.h. This reduces the non-negligible regression risk to 
the ARM architecture.

  For ACPI-based ARM platforms, regression risk is limited because they
  did not have PMU support previously. However, if this code is buggy,
  previously working commands that just made use of non-PMU events (e.g.
  perf top) might start causing problems. To mitigate this, I did a
  perf_fuzzer run on a QDF2400 (ACPI-based) and confirmed it survived
  (Note: this included a workaround for LP: #1689855, which will need to
  be fixed separately once upstreamed).

  For non-ACPI-based (i.e. devicetree) ARM platforms, there is a chance
  that the changes have broken PMU support. To mitigate that, I also did
  a perf_fuzzer run on a Cavium ThunderX system booted in DT mode, which
  it survived.

  Finally, the non-perf related changes in this series are restricted to
  a change in arch/arm64/kernel/smp.c that saves off pointers to each
  CPU's MADT GICC tables. The code is populating a static array with
  existing data - so pretty low risk (no pointer dereferences, etc).

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

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

[Kernel-packages] [Bug 1689856] Re: perf: qcom: Add L3 cache PMU driver

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  perf: qcom: Add L3 cache PMU driver

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

Bug description:
  [Impact]
  Without this driver, users of Qualcomm QDF2400 servers will be unable to 
profile L3 cache events.

  [Test case]
  ubuntu@ubuntu:~$ sudo perf list | grep l3cache | wc -l
  84

  Without this driver, there are 0.

  [Regression Risk]
  This is a new driver that is only used on these servers, so the regression 
risk is pretty isolated to this platform. To mitigate the risk there, I ran 
perf_fuzzer on that system and verified that it survived. Note: I did this 
testing w/ a workaround for LP: #1689855 applied, to avoid hangs caused by a 
hardware issue.

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

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

[Kernel-packages] [Bug 1688259] Re: kernel-wedge fails in artful due to leftover squashfs-modules d-i files

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  kernel-wedge fails in artful due to leftover squashfs-modules d-i
  files

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  We no longer produce a squashfs-modules udeb, but some of the d-i
  files remain in the tree, all of which include another file which has
  been removed. kernel-wedge in artful is choking on these files. Since
  we don't use them anymore they should be removed.

  We also need to tell consumers of squashfs-modules that this is
  provided by the kernel so they do not have to remove their
  dependencies on it.

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

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

[Kernel-packages] [Bug 1688132] Re: Support IPMI system interface on Cavium ThunderX

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  Support IPMI system interface on Cavium ThunderX

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Just loading the necessary modules is not enough to get a working IPMI system 
interface (/dev/ipmi0) on Cavium ThunderX CRBs, and other ThunderX-based 
Gigabyte servers. You have to do some magic:

  echo ipmi_ssif 0x12 >/sys/bus/i2c/devices/i2c-4/new_device
    or maybe:
  echo ipmi_ssif 0x12 >/sys/bus/i2c/devices/i2c-5/new_device

  Loading the modules should be enough.

  [Test Case]
  sudo modprobe ipmi_ssif
  sudo modprobe ipmi_devintf

  Do you have a working /dev/ipmi0?
  sudo ipmitool lan print

  [Regression Risk]
  The driver being fixed is only used on ThunderX-based systems, and is 
currently not usable w/o the above manual config.

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

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

[Kernel-packages] [Bug 1664312] Re: Update ENA driver to 1.1.2 from net-next

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  Update ENA driver to 1.1.2 from net-next

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

Bug description:
  "net/ena 1.1.2 changeset" recently merged into linux/net-next:
  http://marc.info/?l=linux-netdev=148664692122357=2

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-hwe-edge (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe-edge source package in Zesty:
  Fix Committed

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1691161] [NEW] package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nelson]

Public bug reported:

Not Provided

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-signed-image-4.8.0-52-generic 4.8.0-52.55
ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Tue May 16 12:03:34 2017
DuplicateSignature:
 package:linux-signed-image-4.8.0-52-generic:4.8.0-52.55
 Setting up linux-signed-image-4.8.0-52-generic (4.8.0-52.55) ...
 cp: error writing '/boot/vmlinuz-4.8.0-52-generic.efi.signed': No space left 
on device
 dpkg: error processing package linux-signed-image-4.8.0-52-generic 
(--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-02-18 (86 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: linux-signed
Title: package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Not Provided

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-signed-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue May 16 12:03:34 2017
  DuplicateSignature:
   package:linux-signed-image-4.8.0-52-generic:4.8.0-52.55
   Setting up linux-signed-image-4.8.0-52-generic (4.8.0-52.55) ...
   cp: error writing '/boot/vmlinuz-4.8.0-52-generic.efi.signed': No space left 
on device
   dpkg: error processing package linux-signed-image-4.8.0-52-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-18 (86 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Launchpad Bug Tracker]

This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.13

---
qemu (1:2.5+dfsg-5ubuntu10.13) xenial; urgency=medium

  * debian/patches/ubuntu/vvfat-fix-volume-name-assertion.patch:
Fix the volume name assertion in vvfat rw mode (LP: #1684239)

qemu (1:2.5+dfsg-5ubuntu10.12) xenial; urgency=medium

  * debian/patches/ubuntu/bug-1656112-POWER8NVL-[12]-*.patch:
Add PowerISA 2.07 compatibility mode to fix execution on POWER8NVL
processors such as in S822LC (8335-GTB) machines (LP: #1656112)

 -- Christian Ehrhardt   Tue, 25 Apr
2017 13:58:10 +0200

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

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC
    (8335-GTB)

   * This is a toleration change (no exploitation) for those HW releases
     following the SRU policy of "For Long Term Support releases we
     regularly want to enable new hardware. Such changes are appropriate
     provided that we can ensure not to affect upgrades on existing
     hardware."

   * Without the Fix that hardware won't run Xenial guests under current
     Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07
     compatibility mode (plus a few no-op changes as backport
     dependencies)

  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being
     affected.

  [Regression Potential]

   * I'd rate the potential to regress low for powerpc and next to 
 impossible for other architectures, reasons:
   * Changes are PPC only, so fallout should be contained to that
   * Patches and were created by IBM and in Upstream qemu since 2.6
   * The effective change is rather small, only allow to saner cpu model
 versions (drop some HW dev trash that was left) and add the new types.

  [Other Info]

   * Needed for certifying this Hardware for Ubuntu

  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. 

[Kernel-packages] [Bug 1656112] Update Released

[Andy Whitcroft]

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

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

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC
    (8335-GTB)

   * This is a toleration change (no exploitation) for those HW releases
     following the SRU policy of "For Long Term Support releases we
     regularly want to enable new hardware. Such changes are appropriate
     provided that we can ensure not to affect upgrades on existing
     hardware."

   * Without the Fix that hardware won't run Xenial guests under current
     Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07
     compatibility mode (plus a few no-op changes as backport
     dependencies)

  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being
     affected.

  [Regression Potential]

   * I'd rate the potential to regress low for powerpc and next to 
 impossible for other architectures, reasons:
   * Changes are PPC only, so fallout should be contained to that
   * Patches and were created by IBM and in Upstream qemu since 2.6
   * The effective change is rather small, only allow to saner cpu model
 versions (drop some HW dev trash that was left) and add the new types.

  [Other Info]

   * Needed for certifying this Hardware for Ubuntu

  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 

[Kernel-packages] [Bug 1691146] Re: linux: -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: 1691149,1691152
+ derivatives: 1691153

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

Title:
  linux:  -proposed tracker

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

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

  backports: 1691149,1691152
  derivatives: 1691153

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

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

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1

---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
  * New upstream snapshot.
- nova-lxd: read product_name from environment, not platform.
  (LP: #1685810)
- Fix yum repo config where keys contain array values [Dylan Perry]
- template: Update debian backports template [Joshua Powers]
- rsyslog: replace ~ with stop [Joshua Powers] (LP: #1367899)
- Doc: add additional RTD examples [Joshua Powers]
- Fix growpart for some cases when booted with root=PARTUUID.
  (LP: #1684869)
- pylint: update output style to parseable [Joshua Powers]
- pylint: fix all logging warnings [Joshua Powers]
- CloudStack: Add NetworkManager to list of supported DHCP lease dirs.
  [Syed Mushtaq Ahmed]
- net: kernel lies about vlans not stealing mac addresses, when they do
  [Dimitri John Ledkov] (LP: #1682871)
- ds-identify: Check correct path for "latest" config drive
  [Daniel Watkins] (LP: #1673637)
- doc: Fix example for resolv.conf configuration.  [Jon Grimm]
- Fix examples that reference upstream chef repository.  [Jon Grimm]
- doc: correct grammar and improve clarity in merging documentation.
  [David Tagatac]
- doc: Add missing doc link to snap-config module. [Ryan Harper]
- snap: allows for creating cloud-init snap [Joshua Powers]
- DigitalOcean: assign IPv4ll address to lowest indexed interface.
  [Ben Howard] (LP: #1676908)
- DigitalOcean: configure all NICs presented in meta-data.
  [Ben Howard] (LP: #1676908)
- Remove (and/or fix) URL shortener references [Jon Grimm]
- HACKING.rst: more info on filling out contributors agreement.
- util: teach write_file about copy_mode option
  [Lars Kellogg-Stedman] (LP: #1644064)
- DigitalOcean: bind resolvers to loopback interface.
  [Ben Howard] (LP: #1676908)
- tests: fix AltCloud tests to not rely on blkid (LP: #1636531)

 -- Scott Moser   Thu, 27 Apr 2017 13:38:40 -0400

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the 

[Kernel-packages] [Bug 1673250] Re: Internal HUAWEI Mobile Broadband Module not showing up as USB device

[Launchpad Bug Tracker]

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

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

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

Title:
  Internal HUAWEI Mobile Broadband Module not showing up as USB device

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,
  I am running an Acer P645 with internal USB UMTS modem.
  The modem works using a 16.04.1 live USB stick,
  but not on the installed on-disk 16.04.2.

  Below is the lsusb -v in from the live-USB where the UMTS modem works,
  first the USB Hub usb2, then the Huawei device. The information 
  from the running system where the modem does not show up is attached through 
apport.

  I also have access to dmesg on both systems, see further below
  for the successful case. I also tried to copy kernel and modules
  from the live-USB to the hadr disk, booted successfully,
  but still nothing in lsusb. I also tried a few times to use

  for i in /sys/bus/pci/drivers/[uoex]hci_hcd/*:*; do
    echo "${i##*/}" > "${i%/*}/unbind"
    echo "${i##*/}" > "${i%/*}/bind"
  done

  for resetting the bus, still the same.

  I would welcome some suggestions what to test, if there could be
  a firmware issue blocking the UMTS, if teh modem could be blacklisted
  (how do I check that ?) whether udev or systemd could be a problem,
  whether there could be a missing package in the HDD installation (which?!)
  or if UEFI in the boot chain ("sdhci: Secure Digital Host Controller 
Interface driver")
  could cause an issue.

  Or if it makes sense to manually run usb_modeswitch (how?)
  without the device even be in lsusb ?

  Yours,
  Steffen

  

  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 1 Single TT
    bMaxPacketSize064
    idVendor   0x1d6b Linux Foundation
    idProduct  0x0002 2.0 root hub
    bcdDevice4.04
    iManufacturer   3 Linux 4.4.0-31-generic xhci-hcd
    iProduct2 xHCI Host Controller
    iSerial 1 :00:14.0
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   25
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xe0
    Self Powered
    Remote Wakeup
  MaxPower0mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 9 Hub
    bInterfaceSubClass  0 Unused
    bInterfaceProtocol  0 Full speed (or root) hub
    iInterface  0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
    Transfer TypeInterrupt
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0004  1x 4 bytes
  bInterval  12
  Hub Descriptor:
    bLength  11
    bDescriptorType  41
    nNbrPorts 9
    wHubCharacteristic 0x000a
  No power switching (usb 1.0)
  Per-port overcurrent protection
  TT think time 8 FS bits
    bPwrOn2PwrGood   10 * 2 milli seconds
    bHubContrCurrent  0 milli Ampere
    DeviceRemovable0x88 0x00
    PortPwrCtrlMask0xff 0xff
   Hub Port Status:
     Port 1: .0503 highspeed power enable connect
     Port 2: .0100 power
     Port 3: .0100 power
     Port 4: .0100 power
     Port 5: .0503 highspeed power enable connect
     Port 6: .0503 highspeed power enable connect
     Port 7: .0103 power enable connect
     Port 8: .0103 power enable connect
     Port 9: .0100 power
  Device Status: 0x0001
    Self Powered

  Bus 002 Device 006: ID 12d1:1570 Huawei Technologies Co., Ltd.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass  255 Vendor Specific Class
    bDeviceSubClass 2
    bDeviceProtocol 1
    bMaxPacketSize064
    idVendor   0x12d1 Huawei Technologies Co., Ltd.
    idProduct  0x1570
    bcdDevice0.01
    iManufacturer   5 Huawei Technologies Co., Ltd.
    iProduct4 HUAWEI Mobile Broadband Module
    iSerial 0
    

[Kernel-packages] [Bug 1633634] Re: sr-iov not working on ubuntu 16.04 kvm

[Launchpad Bug Tracker]

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

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

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

Title:
  sr-iov not working on ubuntu 16.04 kvm

Status in linux package in Ubuntu:
  Expired

Bug description:
  The exact same set up (hardware and commands I have made) worked
  perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The
  only thing I have changed between the 2 setups is adding  to the network definition as the now default vfio also
  failed with

  qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 
0x7fa68770) = -14 (Bad address)
  qemu: hardware error: vfio: DMA mapping failed, unable to continue

  If I am doing something wrong I apologise, this is my first bug report
  and I'm still relatively new to Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 14 20:11 seq
   crw-rw 1 root audio 116, 33 Oct 14 20:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Oct 14 23:05:26 2016
  HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91
  InstallationDate: Installed on 2016-10-08 (6 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: FUJITSU PRIMERGY TX1310 M1
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on 
iommu=pt pci=assign-busses quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x
  dmi.board.name: D3219-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3219-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: TX1310M1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1:
  dmi.product.name: PRIMERGY TX1310 M1
  dmi.sys.vendor: FUJITSU

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

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was performing a sudo apt-get update in Terminix (Ubuntu Budgie) and
  this randomly popped up. Not sure what sparked the issue.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lane   1586 F pulseaudio
   /dev/snd/controlC0:  lane   1586 F pulseaudio
  Date: Tue May 16 21:05:19 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-15 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: ASUSTeK COMPUTER INC. G20AJ
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=89aa57de-f829-47bf-ae00-0937df0bfbed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G20AJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/29/2015:svnASUSTeKCOMPUTERINC.:pnG20AJ:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnG20AJ:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G20AJ
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1

---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed; 
urgency=medium

  * debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
  * New upstream snapshot.
- nova-lxd: read product_name from environment, not platform.
  (LP: #1685810)
- Fix yum repo config where keys contain array values [Dylan Perry]
- template: Update debian backports template [Joshua Powers]
- rsyslog: replace ~ with stop [Joshua Powers] (LP: #1367899)
- Doc: add additional RTD examples [Joshua Powers]
- Fix growpart for some cases when booted with root=PARTUUID.
  (LP: #1684869)
- pylint: update output style to parseable [Joshua Powers]
- pylint: fix all logging warnings [Joshua Powers]
- CloudStack: Add NetworkManager to list of supported DHCP lease dirs.
  [Syed Mushtaq Ahmed]
- net: kernel lies about vlans not stealing mac addresses, when they do
  [Dimitri John Ledkov] (LP: #1682871)
- ds-identify: Check correct path for "latest" config drive
  [Daniel Watkins] (LP: #1673637)
- doc: Fix example for resolv.conf configuration.  [Jon Grimm]
- Fix examples that reference upstream chef repository.  [Jon Grimm]
- doc: correct grammar and improve clarity in merging documentation.
  [David Tagatac]
- doc: Add missing doc link to snap-config module. [Ryan Harper]
- snap: allows for creating cloud-init snap [Joshua Powers]
- DigitalOcean: assign IPv4ll address to lowest indexed interface.
  [Ben Howard] (LP: #1676908)
- DigitalOcean: configure all NICs presented in meta-data.
  [Ben Howard] (LP: #1676908)
- Remove (and/or fix) URL shortener references [Jon Grimm]
- HACKING.rst: more info on filling out contributors agreement.
- util: teach write_file about copy_mode option
  [Lars Kellogg-Stedman] (LP: #1644064)
- DigitalOcean: bind resolvers to loopback interface.
  [Ben Howard] (LP: #1676908)
- tests: fix AltCloud tests to not rely on blkid (LP: #1636531)

 -- Scott Moser   Thu, 27 Apr 2017 12:51:04 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   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/1682871

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses 

[Kernel-packages] [Bug 1682871] Update Released

[Chris Halse Rogers]

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

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+subscriptions

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

[Kernel-packages] [Bug 1673635] Re: Touchpad doesn't work

[Launchpad Bug Tracker]

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

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

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  Dell Inspiron N4110
  Touchpad doesn't work at all; not even in the LiveCD.

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

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

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1

---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium

  * debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
  * New upstream snapshot.
- nova-lxd: read product_name from environment, not platform.
  (LP: #1685810)
- Fix yum repo config where keys contain array values [Dylan Perry]
- template: Update debian backports template [Joshua Powers]
- rsyslog: replace ~ with stop [Joshua Powers] (LP: #1367899)
- Doc: add additional RTD examples [Joshua Powers]
- Fix growpart for some cases when booted with root=PARTUUID.
  (LP: #1684869)
- pylint: update output style to parseable [Joshua Powers]
- pylint: fix all logging warnings [Joshua Powers]
- CloudStack: Add NetworkManager to list of supported DHCP lease dirs.
  [Syed Mushtaq Ahmed]
- net: kernel lies about vlans not stealing mac addresses, when they do
  [Dimitri John Ledkov] (LP: #1682871)
- ds-identify: Check correct path for "latest" config drive
  [Daniel Watkins] (LP: #1673637)
- doc: Fix example for resolv.conf configuration.  [Jon Grimm]
- Fix examples that reference upstream chef repository.  [Jon Grimm]
- doc: correct grammar and improve clarity in merging documentation.
  [David Tagatac]
- doc: Add missing doc link to snap-config module. [Ryan Harper]
- snap: allows for creating cloud-init snap [Joshua Powers]
- DigitalOcean: assign IPv4ll address to lowest indexed interface.
  [Ben Howard] (LP: #1676908)
- DigitalOcean: configure all NICs presented in meta-data.
  [Ben Howard] (LP: #1676908)
- Remove (and/or fix) URL shortener references [Jon Grimm]
- HACKING.rst: more info on filling out contributors agreement.
- util: teach write_file about copy_mode option
  [Lars Kellogg-Stedman] (LP: #1644064)
- DigitalOcean: bind resolvers to loopback interface.
  [Ben Howard] (LP: #1676908)
- tests: fix AltCloud tests to not rely on blkid (LP: #1636531)

 -- Scott Moser   Thu, 27 Apr 2017 15:09:31 -0400

** Changed in: cloud-init (Ubuntu Zesty)
   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/1682871

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN 

[Kernel-packages] [Bug 1668031] Re: Network adapter keeps on hanging up

[Kai-Heng Feng]

Can you use latest mainline list and latest linux-firmware? If this
issue still happens, please attach output of `journalctl -b`.

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

Title:
  Network adapter keeps on hanging up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every hour or so, I'm unable to access the internet through this
  laptop. dmesg usually reports errors related to the network adapter,
  but not always. Disconnecting from the current Wifi network and
  connecting to another, usually works. Immediately connecting to the
  original network after that does not cause the problem to reoccur. At
  least, not for another hour or so.

  I'm not sure how to better describe this bug.

  The network also provides a nfs drive that is mounted on the laptop,
  if that is significant.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-39-generic 4.8.0-39.42
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruud   2810 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 26 02:13:55 2017
  HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b
  InstallationDate: Installed on 2016-11-08 (109 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691169] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Crash

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivo1631 F pulseaudio
   /dev/snd/controlC1:  ivo1631 F pulseaudio
  Date: Tue May 16 15:27:54 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-11 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=76c85118-4df4-4a25-a5ab-3d4849422ac8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B25.1702171721
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B25.1702171721:bd02/17/2017:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1691169] [NEW] package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Ivo Xavier]

Public bug reported:

Crash

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ivo1631 F pulseaudio
 /dev/snd/controlC1:  ivo1631 F pulseaudio
Date: Tue May 16 15:27:54 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
InstallationDate: Installed on 2017-05-11 (4 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Apple Inc. MacBookPro11,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=76c85118-4df4-4a25-a5ab-3d4849422ac8 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/17/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B25.1702171721
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B25.1702171721:bd02/17/2017:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Crash

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivo1631 F pulseaudio
   /dev/snd/controlC1:  ivo1631 F pulseaudio
  Date: Tue May 16 15:27:54 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-11 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=76c85118-4df4-4a25-a5ab-3d4849422ac8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B25.1702171721
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B25.1702171721:bd02/17/2017:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1691180] [NEW] linux: -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

backports: 1691181
derivatives: 1691182,1691183,1691184,1691186

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-xenial kernel-release-tracking-bug 
kernel-sru-cycle-2017.05.16-1 kernel-sru-master-kernel xenial

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

** Tags added: block-proposed-xenial

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed

[Kernel-packages] [Bug 1689517] Re: Displayport daisy chained displays get recognized as the same

[Joseph Salisbury]

Thanks for the update.  It's probably best for us to perform a bisect to
identify the commit that introduced this.

It sounds like 4.4.0-72 did not exhibit the bug.  To perform the bisect,
we need to identify the last good version and the first bad version.
Can you test 4.4.0-75?  It can be downloaded from:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12451435

You would need to install both the linux-image and linux-image-extra
.deb packages.

** Tags added: performing-bisect

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

Title:
  Displayport daisy chained displays get recognized as the same

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

Bug description:
  Hi,

  I'm using Ubuntu 16.04.2 LTS.

  Since I upgraded to 4.4.0-77, my daisy chained displays seem to get
  recognized as the same. Before, I've been using 4.4.0-72. Booting the
  older Kernel using grub also still works.

  I'm using two Dell U2715H Displays daisy chained. (DP1-1 and DP1-8)
  Both with 2560x1440px. Simultaneously, I use my Notebook Display with
  1920x1080px. (eDP1) I have a script, which I run manually after
  startx, which sets up my environment. It does:

  xrandr --output DP1-1 --mode 2560x1440
  xrandr --output DP1-8 --mode 2560x1440
  xrandr --output DP1-8 --left-of eDP1
  xrandr --output DP1-1 --left-of DP1-8

  On 4.4.0-77 both, DP1-1 and DP1-8 show the same picture (left-of eDP1);
  whereas on 4.4.0-72,
  DP1-1 shows the picture left of DP1-8,
  and DP1-8 shows the picture left of eDP1
  as expected.

  If I take a screenshot using xfce4-screenshooter, everything seems
  fine.

  I attached the output from xrandr on both kernels, screenshots from
  both pictures and reference pictures taken with my camera for you to
  see what actually happens.

  Thanks.

  Screen 0: minimum 8 x 8, current 7040 x 1440, maximum 32767 x 32767
  eDP1 connected 1920x1080+5120+0 (normal left inverted right x axis y axis) 
309mm x 173mm
 1920x1080 60.05*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP1-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP1-8 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florian2980 F pulseaudio
   /dev/snd/pcmC1D0c:   florian2980 F...m pulseaudio
   /dev/snd/pcmC1D0p:   florian2980 F...m pulseaudio
   /dev/snd/controlC1:  florian2980 F pulseaudio
  Date: Tue May  9 11:27:40 2017
  HibernationDevice: RESUME=/dev/mapper/data-swap
  InstallationDate: 

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

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

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

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

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

[Kernel-packages] [Bug 1691180] Re: linux: -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: 1691181
+ derivatives: 1691182,1691183,1691184,1691186

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

Title:
  linux:  -proposed tracker

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

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

  backports: 1691181
  derivatives: 1691182,1691183,1691184,1691186

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

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

[Joseph Salisbury]

This has been fixed upstream by the following commit:

commit 62a6cfddcc0a5313e7da3e8311ba16226fe0ac10
Author: Sachin Prabhu 
Date:   Sun Apr 16 20:37:24 2017 +0100

cifs: Do not send echoes before Negotiate is complete

It has been cc'd to upstream stable and has landed in Xenial and Zesty
master-next via stable updates.

The Yakkety kernel is 4.8 based, which is not maintained upstream
anymore, so I'll submit an SRU request for it to be included in the
Ubuntu kernels.

** No longer affects: linux (Ubuntu Artful)

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

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1691174] Re: Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

[Hayden-haydentech]

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

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Crash

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivo1631 F pulseaudio
   /dev/snd/controlC1:  ivo1631 F pulseaudio
  Date: Tue May 16 15:27:54 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-11 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=76c85118-4df4-4a25-a5ab-3d4849422ac8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B25.1702171721
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B25.1702171721:bd02/17/2017:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1691161] Re: package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Not Provided

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-signed-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue May 16 12:03:34 2017
  DuplicateSignature:
   package:linux-signed-image-4.8.0-52-generic:4.8.0-52.55
   Setting up linux-signed-image-4.8.0-52-generic (4.8.0-52.55) ...
   cp: error writing '/boot/vmlinuz-4.8.0-52-generic.efi.signed': No space left 
on device
   dpkg: error processing package linux-signed-image-4.8.0-52-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-18 (86 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux-aws: 4.4.0-1017.26 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1686645
  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/1686651/+subscriptions

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

[Kernel-packages] [Bug 1691174] [NEW] Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

[Hayden-haydentech]

Public bug reported:

After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load my
Radeon card and I am presented with a low-res fallback desktop.
Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
Radeon driver.


I receive the following message in Xorg.0.log:

[ 36.346] (EE) open /dev/dri/card0: No such file or directory


lspci shows this card installed:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

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


** Tags: kernel-bug

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

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Joseph Salisbury]

@Andrey Vertexx, the Xenial kernel is now at 4.4.0-78.  Can you apply
the latest updates and see if the bug still exists?  Since you are the
original bug reporter, if the latest updates resolves the bug for you,
it might be best to open new bugs for others.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  

[Kernel-packages] [Bug 1691184] [NEW] linux-aws: -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1691180

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: block-proposed-trusty block-proposed-xenial 
kernel-release-tracking-bug kernel-sru-cycle-2017.05.16-1 
kernel-sru-derivative-of-1691180 xenial

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed-xenial

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** 

[Kernel-packages] [Bug 1691174] ProcInterrupts.txt

[Hayden-haydentech]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877693/+files/ProcInterrupts.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] CurrentDmesg.txt

[Hayden-haydentech]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877687/+files/CurrentDmesg.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] ProcEnviron.txt

[Hayden-haydentech]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877692/+files/ProcEnviron.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] Lspci.txt

[Hayden-haydentech]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1691174/+attachment/4877689/+files/Lspci.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] Lsusb.txt

[Hayden-haydentech]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1691174/+attachment/4877690/+files/Lsusb.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] JournalErrors.txt

[Hayden-haydentech]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877688/+files/JournalErrors.txt

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

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] Re: Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

[Hayden-haydentech]

apport information

** Tags added: apport-collected xenial

** Description changed:

  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load my
  Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.
  
  
  I receive the following message in Xorg.0.log:
  
  [ 36.346] (EE) open /dev/dri/card0: No such file or directory
  
  
  lspci shows this card installed:
  
- 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
- [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
+ 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
+ InstallationDate: Installed on 2014-01-31 (1200 days ago)
+ InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
+ IwConfig:
+  lono wireless extensions.
+  
+  eth2  no wireless extensions.
+ MachineType: Dell Inc. OptiPlex 990
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-64-generic N/A
+  linux-backports-modules-4.4.0-64-generic  N/A
+  linux-firmware1.157.8
+ RfKill:
+  
+ Tags:  xenial
+ Uname: Linux 4.4.0-64-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/10/2011
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A07
+ dmi.board.name: 06D7TR
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 6
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
+ dmi.product.name: OptiPlex 990
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877686/+files/AlsaInfo.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1691174] ProcCpuinfo.txt

[Hayden-haydentech]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877691/+files/ProcCpuinfo.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] ProcModules.txt

[Hayden-haydentech]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877694/+files/ProcModules.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

** Also affects: linux (Ubuntu Artful)
   Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1691174] WifiSyslog.txt

[Hayden-haydentech]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877697/+files/WifiSyslog.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] UdevDb.txt

[Hayden-haydentech]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1691174/+attachment/4877696/+files/UdevDb.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691174] PulseList.txt

[Hayden-haydentech]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1691174/+attachment/4877695/+files/PulseList.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/1691174

Title:
  Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load
  my Radeon card and I am presented with a low-res fallback desktop.
  Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
  Radeon driver.

  
  I receive the following message in Xorg.0.log:

  [ 36.346] (EE) open /dev/dri/card0: No such file or directory

  
  lspci shows this card installed:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7c82e9d2-2425-42ea-a16f-6cf5e923ff43
  InstallationDate: Installed on 2014-01-31 (1200 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (372 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

[slimbook]

Hello,
The problem continue.

How can add the tag?
kernel-bug-exists-upstream

Thanks,

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,


This is what I get now when I try the dev package from:

https://launchpad.net/ubuntu/zesty/amd64/gnome-settings-
daemon/3.24.2-0ubuntu0.1

sudo dpkg -i gnome-settings-daemon_3.24.2-0ubuntu0.1_amd64.deb 
[sudo] password for ubuntu: 
(Reading database ... 354908 files and directories currently installed.)
Preparing to unpack gnome-settings-daemon_3.24.2-0ubuntu0.1_amd64.deb ...
Unpacking gnome-settings-daemon (3.24.2-0ubuntu0.1) over (3.24.0-0ubuntu2) ...
dpkg: dependency problems prevent configuration of gnome-settings-daemon:
 gnome-settings-daemon depends on gnome-settings-daemon-schemas (= 
3.24.2-0ubuntu0.1); however:
  Version of gnome-settings-daemon-schemas on system is 3.24.0-0ubuntu2.

dpkg: error processing package gnome-settings-daemon (--install):
 dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
 gnome-settings-daemon

so I downloaded that from:
https://launchpad.net/ubuntu/zesty/amd64/gnome-settings-daemon-schemas/3.24.2-0ubuntu0.1
and installed it.

Then I rebooted but there is not difference in behaviour.

Note that I use Unity, not Gnome.

When I installed these packages:
http://people.canonical.com/~khfeng/lp1683445/
it worked.

Thank you all!

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Linux:
  Won't Fix
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  Fix Committed
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions

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

[Kernel-packages] [Bug 1690174] Re: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

[Marcelo Cerri]

We need to backport the patch for the kernels with older versions of the
driver. Can you please describe the steps to reproduce and test the
issue?

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

Title:
  [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

Status in linux package in Ubuntu:
  Triaged
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Azure hosts are not supporting non-TCP port numbers in vRSS hashing for
  now. For example, UDP packet loss rate will be high if port numbers are
  also included in vRSS hash.

  So, we created this patch to use only IP numbers for hashing in non-TCP
  traffic.

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=f72860afa2e32cdc674cbdd7f354f8fb62e908a6

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[buzuk56]

Here is a 4 steps procedures that worked on AB350 Gaming 3 Ryzen 1600
(F4 bios) to get 17.04 with all cores and threads

1)Ubuntu 17.04 install from usb bootable drive with acpi=off (press F6
when display menu)

2)log in and  install sudo dpk -i *deb the kernel compiled by nextized worked:
http://www.nextized.net/repo/linux/ubuntu-linux-4.10.3_ryzen01_amd64_generic.tar.gz
3) push back acpi=on to your 17.04 system to get all core and threads from your 
Ryzen
sudo gedit /etc/default/grub  
Change line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=on"
sudo update-grub
4) reboot and you should have all cores and threads on 17.04 new install

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

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

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

[Manoj Iyer]

Patches are in linux-next:

5d3a0880787b scsi: aacraid: Remove __GFP_DMA for raw srb memory
96a580fcd745 scsi: aacraid: Fix DMAR issues with iommu=pt
7ad76ab57203 scsi: aacraid: Added 32 and 64 queue depth for arc natives
db62b8248626 scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks
be70a99e5386 scsi: aacraid: Remove reset support from check_health
30ad417155a8 scsi: aacraid: Change wait time for fib completion
dce4bd517aa2 scsi: aacraid: Log count info of scsi cmds before reset
b791530208ae scsi: aacraid: Print ctrl status before eh reset
52fa7b51eedd scsi: aacraid: Using single reset mask for IOP reset
f2ff3fdf82bc scsi: aacraid: Rework IOP reset
dec430cefee5 scsi: aacraid: Add periodic checks to see IOP reset status
92ea09df1c11 scsi: aacraid: Rework SOFT reset code
8022c90ec2b9 scsi: aacraid: Rework aac_src_restart
b5a7478a18eb scsi: aacraid: Use correct function to get ctrl health
69c727ba1840 scsi: aacraid: Make sure ioctl returns on controller reset
9c35add987b2 scsi: aacraid: Enable ctrl reset for both hba and arc
2d5504c53a18 scsi: aacraid: Add reset debugging statements
5d9cb9c96198 scsi: aacraid: Remove reference to Series-9
0e98ceae7bfe scsi: aacraid: Update driver version to 50834

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

Title:
  AACRAID for power9 platform

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

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1690174] Re: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

[Marcelo Cerri]

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

** No longer affects: linux-azure (Ubuntu Yakkety)

** No longer affects: linux-azure (Ubuntu Zesty)

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

Title:
  [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

Status in linux package in Ubuntu:
  Triaged
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Azure hosts are not supporting non-TCP port numbers in vRSS hashing for
  now. For example, UDP packet loss rate will be high if port numbers are
  also included in vRSS hash.

  So, we created this patch to use only IP numbers for hashing in non-TCP
  traffic.

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=f72860afa2e32cdc674cbdd7f354f8fb62e908a6

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Stephen Hamer]

Hi,

Running 64-bit Ubuntu 16.04 on a new quietpc "sentinel" fanless pc with
a 256GB Samsung PM961 Polaris NVMe M.2 SSD.

Came back to my set-up this lunchtime and found that the screen had
frozen - first ever crash in 7 years of using ubuntu!

Did Ctrl+Alt+F4 to get to a terminal and got this message:

EXT4-fs error (dev nvme0n1p4:ext4_find_entry:1461:inode #1460718: com
(agetty): reading directory block lblock 0

Is it the same issue?

Solution 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/1678184

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1688114] Re: arm64/ACPI support for SBSA watchdog

[dann frazier]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  arm64/ACPI support for SBSA watchdog

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  On arm64/ACPI-based servers, such as the QDT2400 and HiSilicon D05, there is 
a watchdog feature based on the architected timer that is not usable in Ubuntu. 
This prevents these systems from using this facility to automatically recover 
from a hard lockup.

  [Test Case]
  sudo modprobe sbsa-gwdt
  ls -l /dev/watchdog*

  [Regression Risk]
  The changes required are to the ARM architected timer driver and some new 
code to parse the configuration data from the ACPI GTDT table. These changes 
only apply to ARM-specific code, so the risk is limited to those platforms.

  This has been tested on the QDT2400 and HiSilicon D05, and regression
  tested on an non-ACPI (devicetree) HP m400 and Cavium ThunderX
  systems.

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

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

Re: [Kernel-packages] [Bug 1668031] Re: Network adapter keeps on hanging up

[Gerardus]

Hey Kai-Heng,

Sorry for the late reply - we moved house and it was chaotic. Still is
:)

To try to answer your question: I've got Zesty installed, and the issue is
still happening. I need to sudo service network-manager restart every so
often to get the data flowing.

Be sure to let me know if there's anything else I can help you with!

Many regards

On 14 March 2017 at 05:27, Kai-Heng Feng 
wrote:

> Gerardus,
>
> Can you make a Zesty LiveUSB and test if this issue happens?
>
> I just grabbed a Killer 1535 and seems like the issue does not happen on
> Zesty.
>
> I'd like to make sure this issue is solved in 4.10, so I can bisect and
> backport needed patch.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1668031
>
> Title:
>   Network adapter keeps on hanging up
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Every hour or so, I'm unable to access the internet through this
>   laptop. dmesg usually reports errors related to the network adapter,
>   but not always. Disconnecting from the current Wifi network and
>   connecting to another, usually works. Immediately connecting to the
>   original network after that does not cause the problem to reoccur. At
>   least, not for another hour or so.
>
>   I'm not sure how to better describe this bug.
>
>   The network also provides a nfs drive that is mounted on the laptop,
>   if that is significant.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-39-generic 4.8.0-39.42
>   ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
>   Uname: Linux 4.8.0-39-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ruud   2810 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Feb 26 02:13:55 2017
>   HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b
>   InstallationDate: Installed on 2016-11-08 (109 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   MachineType: Dell Inc. XPS 13 9360
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.8.0-39-generic N/A
>linux-backports-modules-4.8.0-39-generic  N/A
>linux-firmware1.162
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/18/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.3.2
>   dmi.board.name: 0T3FTF
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:
> pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: XPS 13 9360
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1668031/+subscriptions
>

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

Title:
  Network adapter keeps on hanging up

Status in linux package in Ubuntu:
  Expired

Bug description:
  Every hour or so, I'm unable to access the internet through this
  laptop. dmesg usually reports errors related to the network adapter,
  but not always. Disconnecting from the current Wifi network and
  connecting to another, usually works. Immediately connecting to the
  original network after that does not cause the problem to reoccur. At
  least, not for another hour or so.

  I'm not sure how to better describe this bug.

  The network also provides a nfs drive that is mounted on the laptop,
  if that is significant.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-39-generic 4.8.0-39.42
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruud   2810 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 26 02:13:55 2017
  HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b
  InstallationDate: Installed on 2016-11-08 (109 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware   

[Kernel-packages] [Bug 1690984] Re: Wifi drops out RTL8821AE

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].

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

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/


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

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

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

Title:
  Wifi drops out RTL8821AE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Have tried downloading and compiling driver, have tried
  /etc/modprobe.d/rtl8821ae.conf with combinations of options rtl8821ae
  fwlps swlps being Y, N, 1, and 0. None of the combinations works.

  WiFi comes up, lasts a few seconds - maybe up to a few minutes, then
  disconnects.

  Restarting the network manager service usually restores the connection
  for a few minutes, sometimes a reboot is required.

  Running a VPN over the wireless adapter causes the dropout to occur
  quicker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1758 F pulseaudio
   /dev/snd/controlC1:  steve  1758 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 16 11:51:44 2017
  HibernationDevice: RESUME=UUID=395e6c11-8c59-45e8-85eb-2917c9588d7b
  InstallationDate: Installed on 2017-01-09 (126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. P552LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic 
root=UUID=bedc4f01-09c8-407a-b5b9-5b2da87846f7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P552LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P552LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP552LA.204:bd08/11/2015:svnASUSTeKCOMPUTERINC.:pnP552LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP552LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: P552LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1691292] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Freezing of Ubuntu (Zesty) Software Center while installing Kdenlive
  video program.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pegasus1862 F pulseaudio
   /dev/snd/pcmC0D0p:   pegasus1862 F...m pulseaudio
   /dev/snd/controlC0:  pegasus1862 F pulseaudio
  Date: Wed May 17 00:39:35 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=cc97699a-036f-4fea-85ba-00701fc557ff
  InstallationDate: Installed on 2017-04-15 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   enp6s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=74bcd564-f87b-4694-bd6d-9f6945e03528 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1502:bd03/02/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1691292] [NEW] package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Gerald Schedl]

Public bug reported:

Freezing of Ubuntu (Zesty) Software Center while installing Kdenlive
video program.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pegasus1862 F pulseaudio
 /dev/snd/pcmC0D0p:   pegasus1862 F...m pulseaudio
 /dev/snd/controlC0:  pegasus1862 F pulseaudio
Date: Wed May 17 00:39:35 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=cc97699a-036f-4fea-85ba-00701fc557ff
InstallationDate: Installed on 2017-04-15 (31 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 enp6s0no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=74bcd564-f87b-4694-bd6d-9f6945e03528 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1502
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1502:bd03/02/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Freezing of Ubuntu (Zesty) Software Center while installing Kdenlive
  video program.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pegasus1862 F pulseaudio
   /dev/snd/pcmC0D0p:   pegasus1862 F...m pulseaudio
   /dev/snd/controlC0:  pegasus1862 F pulseaudio
  Date: Wed May 17 00:39:35 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=cc97699a-036f-4fea-85ba-00701fc557ff
  InstallationDate: Installed on 2017-04-15 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   enp6s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=74bcd564-f87b-4694-bd6d-9f6945e03528 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1687718] Re: linux: 3.13.0-119.166 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

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

  backports: 1687719
  derivatives:
  -- swm properties --
  boot-testing-requested: 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/1687718/+subscriptions

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

[Kernel-packages] [Bug 1687718] Re: linux: 3.13.0-119.166 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-119.166

---
linux (3.13.0-119.166) trusty; urgency=low

  * linux: 3.13.0-119.166 -proposed tracker (LP: #1687718)

  * CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation
(LP: #1687107)
- rose: limit sk_filter trim to payload
- tcp: take care of truncations done by sk_filter()

linux (3.13.0-118.165) trusty; urgency=low

  * linux: 3.13.0-118.165 -proposed tracker (LP: #1686154)

  * linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
handle_invept() (LP: #1678676)
- SAUCE: KVM has a flaw in INVEPT emulation that could crash the host

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

 -- Thadeu Lima de Souza Cascardo   Tue, 02 May
2017 15:14:50 -0300

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

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

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

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

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

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

  backports: 1687719
  derivatives:
  -- swm properties --
  boot-testing-requested: 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/1687718/+subscriptions

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

[Kernel-packages] [Bug 1687107] Re: CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-119.166

---
linux (3.13.0-119.166) trusty; urgency=low

  * linux: 3.13.0-119.166 -proposed tracker (LP: #1687718)

  * CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation
(LP: #1687107)
- rose: limit sk_filter trim to payload
- tcp: take care of truncations done by sk_filter()

linux (3.13.0-118.165) trusty; urgency=low

  * linux: 3.13.0-118.165 -proposed tracker (LP: #1686154)

  * linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
handle_invept() (LP: #1678676)
- SAUCE: KVM has a flaw in INVEPT emulation that could crash the host

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

 -- Thadeu Lima de Souza Cascardo   Tue, 02 May
2017 15:14:50 -0300

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

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

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

Title:
  CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  From CVE description:
  https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-8645.html

  "The TCP stack in the Linux kernel before 4.8.10 mishandles skb truncation,
  which allows local users to cause a denial of service (system crash) via a
  crafted application that makes sendto system calls, related to
  net/ipv4/tcp_ipv4.c and net/ipv6/tcp_ipv6.c."

  [Test Case]
  See references in the CVE page.

  [Regression Potential]
  This modifies the code that handles all tcp packets, so it could cause 
problems with network traffic, although unlikely since it's been applied 
upstream and to various stable kernels (but not the 3.13.y stable branch).

  [Other Info]
  The patch appears to have been pulled into xenial through the 4.4.y stable 
tree, but it doesn't appear that the patch will be applied to the 3.13.y stable 
tree, so this bug is track manually adding the patch.

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

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

[Kernel-packages] [Bug 1686154] Re: linux: 3.13.0-118.165 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux - 3.13.0-119.166

---
linux (3.13.0-119.166) trusty; urgency=low

  * linux: 3.13.0-119.166 -proposed tracker (LP: #1687718)

  * CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation
(LP: #1687107)
- rose: limit sk_filter trim to payload
- tcp: take care of truncations done by sk_filter()

linux (3.13.0-118.165) trusty; urgency=low

  * linux: 3.13.0-118.165 -proposed tracker (LP: #1686154)

  * linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
handle_invept() (LP: #1678676)
- SAUCE: KVM has a flaw in INVEPT emulation that could crash the host

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

 -- Thadeu Lima de Souza Cascardo   Tue, 02 May
2017 15:14:50 -0300

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

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

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

Title:
  linux: 3.13.0-118.165 -proposed tracker

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

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

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

  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1685892] Re: CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec

[Launchpad Bug Tracker]

This bug was fixed in the package linux-hwe - 4.8.0-52.55~16.04.1

---
linux-hwe (4.8.0-52.55~16.04.1) xenial; urgency=low

  * linux-hwe: 4.8.0-52.55~16.04.1 -proposed tracker (LP: #1686978)

  * linux: 4.8.0-52.55 -proposed tracker (LP: #1686976)

  * CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec (LP: #1685892)
- macsec: avoid heap overflow in skb_to_sgvec
- macsec: dynamically allocate space for sglist

  * net/ipv4: original ingress device index set as the loopback interface.
(LP: #1683982)
- net: fix incorrect original ingress device index in PKTINFO

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * Potential memory corruption with capi adapters (LP: #1681469)
- powerpc/mm: Add missing global TLB invalidate if cxl is active

  * [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and
image (LP: #1650058)
- net/mlx4_en: Fix bad WQE issue
- net/mlx4_core: Fix racy CQ (Completion Queue) free
- net/mlx4_core: Fix when to save some qp context flags for dynamic VST to 
VGT
  transitions
- net/mlx4_core: Avoid command timeouts during VF driver device shutdown

 -- Stefan Bader   Fri, 28 Apr 2017 12:17:12
+0200

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

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

Title:
  CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Invalid

Bug description:
  Please apply
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=4d6fa57b4dab0d77f4d8e9d9c73d1e63f6fe8fee

  (See also http://www.openwall.com/lists/oss-security/2017/04/24/4 )

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

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

[Kernel-packages] [Bug 1685892] Re: CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec

[Launchpad Bug Tracker]

This bug was fixed in the package linux-hwe - 4.8.0-52.55~16.04.1

---
linux-hwe (4.8.0-52.55~16.04.1) xenial; urgency=low

  * linux-hwe: 4.8.0-52.55~16.04.1 -proposed tracker (LP: #1686978)

  * linux: 4.8.0-52.55 -proposed tracker (LP: #1686976)

  * CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec (LP: #1685892)
- macsec: avoid heap overflow in skb_to_sgvec
- macsec: dynamically allocate space for sglist

  * net/ipv4: original ingress device index set as the loopback interface.
(LP: #1683982)
- net: fix incorrect original ingress device index in PKTINFO

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * Potential memory corruption with capi adapters (LP: #1681469)
- powerpc/mm: Add missing global TLB invalidate if cxl is active

  * [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and
image (LP: #1650058)
- net/mlx4_en: Fix bad WQE issue
- net/mlx4_core: Fix racy CQ (Completion Queue) free
- net/mlx4_core: Fix when to save some qp context flags for dynamic VST to 
VGT
  transitions
- net/mlx4_core: Avoid command timeouts during VF driver device shutdown

 -- Stefan Bader   Fri, 28 Apr 2017 12:17:12
+0200

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

Title:
  CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Invalid

Bug description:
  Please apply
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=4d6fa57b4dab0d77f4d8e9d9c73d1e63f6fe8fee

  (See also http://www.openwall.com/lists/oss-security/2017/04/24/4 )

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

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

[Kernel-packages] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-119.166

---
linux (3.13.0-119.166) trusty; urgency=low

  * linux: 3.13.0-119.166 -proposed tracker (LP: #1687718)

  * CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation
(LP: #1687107)
- rose: limit sk_filter trim to payload
- tcp: take care of truncations done by sk_filter()

linux (3.13.0-118.165) trusty; urgency=low

  * linux: 3.13.0-118.165 -proposed tracker (LP: #1686154)

  * linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
handle_invept() (LP: #1678676)
- SAUCE: KVM has a flaw in INVEPT emulation that could crash the host

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

 -- Thadeu Lima de Souza Cascardo   Tue, 02 May
2017 15:14:50 -0300

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

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

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

Title:
  Please backport fix to reference leak in cgroup blkio throttle

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

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

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

[Kernel-packages] [Bug 1686414] Re: linux: 4.10.0-21.23 -proposed tracker

[Brad Figg]

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

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

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

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

  backports: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: 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/1686414/+subscriptions

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

[Kernel-packages] [Bug 1678676] Re: linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in handle_invept()

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-119.166

---
linux (3.13.0-119.166) trusty; urgency=low

  * linux: 3.13.0-119.166 -proposed tracker (LP: #1687718)

  * CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation
(LP: #1687107)
- rose: limit sk_filter trim to payload
- tcp: take care of truncations done by sk_filter()

linux (3.13.0-118.165) trusty; urgency=low

  * linux: 3.13.0-118.165 -proposed tracker (LP: #1686154)

  * linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
handle_invept() (LP: #1678676)
- SAUCE: KVM has a flaw in INVEPT emulation that could crash the host

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

 -- Thadeu Lima de Souza Cascardo   Tue, 02 May
2017 15:14:50 -0300

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

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

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

Title:
  linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
  handle_invept()

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  KVM in linux 3.11 - 3.14 (including ubuntu 14.04 linux <= 3.13.0-113.160) has 
a
  flaw in INVEPT emulation that could crash the host.

  [ 1046.384746] BUG: unable to handle kernel NULL pointer dereference at 
0070
  [ 1046.387386] IP: [] handle_invept+0x123/0x170 [kvm_intel]
  [ 1046.389577] PGD 0 
  [ 1046.390273] Oops:  [#1] SMP 

  (tested with Ubuntu 14.04 linux-image-3.13.0-113-generic)

  The host KVM touches NULL pointer (vmx->nested.current_vmcs12) when a
  (crafted or buggy) guest issues a single-context INVEPT instruction
  *without* VMPTRLD like this:

kvm_cpu_vmxon(phys_addr);
ept_sync_context(0);

  (requires nested EPT; full linux kernel module code attached)

  This code is introduced in upstream commit 
bfd0a56b90005f8c8a004baf407ad90045c2b11e
  (nEPT: Nested INVEPT) and removed in 4b855078601fc422dbac3059f2215e776f49780f
  (KVM: nVMX: Don't advertise single context invalidation for invept).
  Therefore there should be two ways to fix this.

  a. pullup bfd0a56b90005f (and 45e11817d5703e)
  b. check current_vmcs12 before accessing for minimal fix:

  diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
  index d9e567f..d785e9c 100644
  --- a/arch/x86/kvm/vmx.c
  +++ b/arch/x86/kvm/vmx.c
  @@ -6391,6 +6391,8 @@ static int handle_invept(struct kvm_vcpu *vcpu)
   
switch (type) {
case VMX_EPT_EXTENT_CONTEXT:
  + if (to_vmx(vcpu)->nested.current_vmptr == -1ull)
  + break;
if ((operand.eptp & eptp_mask) !=
(nested_ept_get_cr3(vcpu) & eptp_mask))
break;

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

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

[Kernel-packages] [Bug 1678676] Re: linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in handle_invept()

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-119.166

---
linux (3.13.0-119.166) trusty; urgency=low

  * linux: 3.13.0-119.166 -proposed tracker (LP: #1687718)

  * CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation
(LP: #1687107)
- rose: limit sk_filter trim to payload
- tcp: take care of truncations done by sk_filter()

linux (3.13.0-118.165) trusty; urgency=low

  * linux: 3.13.0-118.165 -proposed tracker (LP: #1686154)

  * linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
handle_invept() (LP: #1678676)
- SAUCE: KVM has a flaw in INVEPT emulation that could crash the host

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

 -- Thadeu Lima de Souza Cascardo   Tue, 02 May
2017 15:14:50 -0300

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

Title:
  linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
  handle_invept()

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  KVM in linux 3.11 - 3.14 (including ubuntu 14.04 linux <= 3.13.0-113.160) has 
a
  flaw in INVEPT emulation that could crash the host.

  [ 1046.384746] BUG: unable to handle kernel NULL pointer dereference at 
0070
  [ 1046.387386] IP: [] handle_invept+0x123/0x170 [kvm_intel]
  [ 1046.389577] PGD 0 
  [ 1046.390273] Oops:  [#1] SMP 

  (tested with Ubuntu 14.04 linux-image-3.13.0-113-generic)

  The host KVM touches NULL pointer (vmx->nested.current_vmcs12) when a
  (crafted or buggy) guest issues a single-context INVEPT instruction
  *without* VMPTRLD like this:

kvm_cpu_vmxon(phys_addr);
ept_sync_context(0);

  (requires nested EPT; full linux kernel module code attached)

  This code is introduced in upstream commit 
bfd0a56b90005f8c8a004baf407ad90045c2b11e
  (nEPT: Nested INVEPT) and removed in 4b855078601fc422dbac3059f2215e776f49780f
  (KVM: nVMX: Don't advertise single context invalidation for invept).
  Therefore there should be two ways to fix this.

  a. pullup bfd0a56b90005f (and 45e11817d5703e)
  b. check current_vmcs12 before accessing for minimal fix:

  diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
  index d9e567f..d785e9c 100644
  --- a/arch/x86/kvm/vmx.c
  +++ b/arch/x86/kvm/vmx.c
  @@ -6391,6 +6391,8 @@ static int handle_invept(struct kvm_vcpu *vcpu)
   
switch (type) {
case VMX_EPT_EXTENT_CONTEXT:
  + if (to_vmx(vcpu)->nested.current_vmptr == -1ull)
  + break;
if ((operand.eptp & eptp_mask) !=
(nested_ept_get_cr3(vcpu) & eptp_mask))
break;

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

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

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

[bugproxy]

--- Comment From vipar...@in.ibm.com 2017-05-16 07:07 EDT---
Commit c950fd6f20 ("pstore: Split pstore fragile flags") is
available in kernel 4.9 and above, while commit
041939c1ec ("pstore: Fix flags to enable dumps on powerpc")
would get into 4.12, so need to be pulled into kernel version 4.9 and
above.

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

Title:
  PowerPC: Pstore dump for powerpc is broken

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1691045/+subscriptions

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

[Kernel-packages] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

[Kleber Sacilotto de Souza]

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

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

Title:
  linux-aws: 4.4.0-1017.26 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1686645
  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/1686651/+subscriptions

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

[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail

[Richard Laager]

I suspect that wouldn't work, for one reason or another. The upstream
one has more features, probably.

I'd rather just keep this Debian-specific. The initramfs script is
likely to have distro specific code. I don't see the idea of one unified
script working out well.

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

Title:
  ZFS initramfs mounts dataset explicitly set not to be mounted, causing
  boot process to fail

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs
  zfs script might overrule canmount and mountpoint options for a
  dataset, causing other mount operations and with them the boot process
  to fail.

  Experienced this with Ubuntu Zesty. Xenial seems to ship with a
  different zfs script for the initrd.

  Work around when it happens: unmount the dataset that should not be
  mounted, and exit the initramfs rescue prompt to resume booting.

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

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

[Kernel-packages] [Bug 1686645] Re: linux: 4.4.0-78.99 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1686645/+subscriptions

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

[Kernel-packages] [Bug 1681862] Re: Xenial update to v4.4.60 stable release

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1682140] Re: Xenial update to v4.4.61 stable release

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1683728] Re: Xenial update to v4.4.62 stable release

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1682215] Re: [Hyper-V] mkfs regression in kernel 4.4+

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1667323] Re: Backlight control does not work and there are no entries in /sys/class/backlight

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1686645] Re: linux: 4.4.0-78.99 -proposed tracker

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1672144] Re: ifup service of network device stay active after driver stop

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1659111] Re: UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1662589] Re: Touchpad not working correctly after kernel upgrade

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1682103] Re: sysfs channel reads of lps22hb pressure sensor are stale

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1591640] Re: [Feature] KBL: intel_rapl driver support

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1591640] Re: [Feature] KBL: intel_rapl driver support

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1591641] Re: [Feature] KBL: intel_powerclamp driver support

[Launchpad Bug Tracker]

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

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

  * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645)

  * Please backport fix to reference leak in cgroup blkio throttle
(LP: #1683976)
- block: fix module reference leak on put_disk() call for cgroups throttle

  * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
4.4.0-47-generic (LP: #1659111)
- block: Unhash block device inodes on gendisk destruction
- block: Use pointer to backing_dev_info from request_queue
- block: Dynamically allocate and refcount backing_dev_info
- block: Make blk_get_backing_dev_info() safe without open bdev
- block: Get rid of blk_get_backing_dev_info()
- block: Move bdev_unhash_inode() after invalidate_partition()
- block: Unhash also block device inode for the whole device
- block: Revalidate i_bdev reference in bd_aquire()
- block: Initialize bd_bdi on inode initialization
- block: Move bdi_unregister() to del_gendisk()
- block: Allow bdi re-registration
- bdi: Fix use-after-free in wb_congested_put()
- block: Make del_gendisk() safer for disks without queues
- block: Fix bdi assignment to bdev inode when racing with disk delete
- bdi: Mark congested->bdi as internal
- bdi: Make wb->bdi a proper reference
- bdi: Unify bdi->wb_list handling for root wb_writeback
- bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
- bdi: Do not wait for cgwbs release in bdi_unregister()
- bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
- block: Fix oops in locked_inode_to_wb_and_lock_list()
- kobject: Export kobject_get_unless_zero()
- block: Fix oops scsi_disk_get()

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * Xenial update to v4.4.62 stable release (LP: #1683728)
- drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3
- drm/i915: Stop using RP_DOWN_EI on Baytrail
- usb: dwc3: gadget: delay unmap of bounced requests
- mtd: bcm47xxpart: fix parsing first block after aligned TRX
- MIPS: Introduce irq_stack
- MIPS: Stack unwinding while on IRQ stack
- MIPS: Only change $28 to thread_info if coming from user mode
- MIPS: Switch to the irq_stack in interrupts
- MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK
- MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch
- crypto: caam - fix RNG deinstantiation error checking
- Linux 4.4.62

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * [Feature] KBL: intel_powerclamp driver support (LP: #1591641)
- thermal/powerclamp: remove cpu whitelist
- thermal/powerclamp: correct cpu support check
- thermal/powerclamp: add back module device table

  * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103)
- iio: st_pressure: initialize lps22hb bootime

  * Backlight control does not work and there are no entries in
/sys/class/backlight (LP: #1667323)
- Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"

  * [Feature] KBL: intel_rapl driver support (LP: #1591640)
- powercap/intel_rapl: Add support for Kabylake

  * Xenial update to v4.4.61 stable release (LP: #1682140)
- drm/vmwgfx: Type-check lookups of fence objects
- drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()
- drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()
- drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces
- drm/vmwgfx: Remove getparam error message
- drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()
- sysfs: be careful of error returns from ops->show()
- staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
- arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm
- arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region
- iio: bmg160: reset chip when probing
- Reset TreeId to zero on SMB2 TREE_CONNECT
- ptrace: fix PTRACE_LISTEN race corrupting task->state
- ring-buffer: Fix return value check in test_ringbuffer()
- metag/usercopy: Drop unused macros
- metag/usercopy: Fix alignment error checking
- metag/usercopy: Add early abort to copy_to_user
- metag/usercopy: Zero rest of buffer from copy_from_user
- metag/usercopy: Set flags before ADDZ
- metag/usercopy: Fix src fixup in from user rapf loops
- metag/usercopy: Add missing fixups
- powerpc/mm: Add missing global TLB invalidate if cxl is active
- powerpc: Don't try to fix up misaligned load-with-reservation instructions
- nios2: reserve boot memory for device tree
- s390/decompressor: fix initrd corruption caused by bss 

[Kernel-packages] [Bug 1659111] backported patches, mentioning conflicts

[bugproxy]

--- Comment on attachment From thiag...@br.ibm.com 2017-04-06 14:11 
EDT---


I'm not sure I understood the question. All of the patches are backports.
These are the files that had conflicts:

block/blk-cgroup.c
block/blk-core.c
block/blk-settings.c
block/blk-sysfs.c
block/blk-wbt.c
block/compat_ioctl.c
block/ioctl.c
drivers/block/aoe/aoeblk.c
drivers/block/drbd/drbd_nl.c
drivers/md/dm.c
drivers/md/md.c
fs/block_dev.c
fs/btrfs/volumes.c
include/linux/backing-dev-defs.h
include/linux/blkdev.h

I'm also attaching a new mbox file with exactly the same patches, with
the only difference being that the description of each patch mentions
which files had conflicts when cherry-picking.

** Attachment added: "backported patches, mentioning conflicts"
   
https://bugs.launchpad.net/bugs/1659111/+attachment/4877433/+files/block-races-backports-conflicts.mbox

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

Title:
  UbuntuKVM guest crashed while running I/O stress test with Ubuntu
  kernel  4.4.0-47-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Attn. Canonical: For your awareness only at this time.

  == Comment: #0 - LEKSHMI C. PILLAI  - 2016-11-22 03:49:38 ==

  Machine INFO

  KVM HOST: luckyv1

  Guest :lucky05

  lucky05 crashed while running the I/O stress test for SAN disks.

  Installed lucky05 and enabled the xmon on that.After that started the
  RAW disk test on around 50 disks.After 6-7 hours after running,Now
  machine dropped into xmon.

  Logs:
  [25023.224182] Unable to handle kernel paging request for data at address 
0x
  [25023.224257] Faulting instruction address: 0xc0324c60
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620]
  pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c032831c: writeback_sb_inodes+0x30c/0x590
  sp: c000fffc38a0
 msr: 80019033
 dar: 0
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4
  3:mon> f
  3:mon> th
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 
  3:mon> sh
  [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651220]  (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992)
  [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 
(4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [27384.651501] rcu_sched kthread starved for 40596 jiffies! g2849830 c2849829 
f0x2 s3 ->state=0x0
  [27384.651747] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651905]  (detected by 4, t=590354 jiffies, g=2849830, c=2849829, 
q=1285)
  [27384.652012] All QSes seen, last rcu_sched kthread activity 590352 
(4301738470-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [27384.652191] rcu_sched kthread starved for 590352 jiffies! g2849830 
c2849829 f0x2 s3 ->state=0x0
  [27384.730645] Unable to handle kernel paging request for data at address 
0xffd8
  [27384.730781] Faulting instruction address: 0xc00e7258
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3000]
  pc: c00e7258: kthread_data+0x28/0x40
  lr: c00de940: wq_worker_sleeping+0x30/0x110
  sp: c000fffc3280
 msr: 80019033
 dar: ffd8
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help

  == Comment: #1 - LEKSHMI C. PILLAI - 2016-11-22 04:05:41 ==
  3:mon> th
  [c000fffc32b0] c00de940