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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new interface 
driver rtl8xxxu
  Feb 21 07:17:03 orin dbus[1112]: [system] Activating via systemd: service 

[Kernel-packages] [Bug 1666421] [NEW] kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[camikusch]

Public bug reported:

booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

booting the PC without the stick attached works fine, but as soon as it
is attached (see syslog) mouse, keyboard and the desktop itself are dead
(checked by opening terminal and "watch date" - freezes, with desktop
still visible).

problem is resolved by booting former kernel 4.4.0-59-generic.

syslog upon attaching stick ---
Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB device 
number 2 using xhci_hcd
Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 00e04c01
Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: unset
Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - end_freq 
@ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 2472000 
KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 2482000 
KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 2494000 
KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 525 
KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 533 
KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 573 
KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 5835000 
KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new interface 
driver rtl8xxxu
Feb 21 07:17:03 orin dbus[1112]: [system] Activating via systemd: service 
name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Feb 21 07:17:03 orin kernel: [  190.652729] rtl8192cu 8-2:1.0 wlx14cc20104398: 
renamed from wlan0
Feb 21 07:17:03 orin systemd[1]: Starting WPA supplicant...
Feb 21 07:17:03 orin systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7963] rfkill1: 
found WiFi radio killswitch (at 
/sys/devices/pci:00/:00:10.1/usb8/8-2/8-2:1.0/ieee80211/phy0/rfkill1) 
(driver 

[Kernel-packages] [Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Chris Valean]

Can we get Vivid out of the list please?
I see that it is now EOL.

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
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:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+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 1666401] 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 1666401

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

Title:
  Export symbol "dev_pm_qos_update_user_latency_tolerance"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  To enable NVME APST (autonomous power state transitions) to conserve
  NVME power consumption, this commit is required:

  commit 034e7906211c18c230ef4da43a1c44796dd5b95e
  Author: Andrew Lutomirski 
  Date:   Tue Nov 29 17:11:52 2016 -0800

  PM / QoS: Export dev_pm_qos_update_user_latency_tolerance

  nvme wants a module parameter that overrides the default latency
  tolerance.  This makes it easy for nvme to reflect that default in
  sysfs.

  Signed-off-by: Andy Lutomirski 
  Signed-off-by: Rafael J. Wysocki 

  It can be cleanly picked into Xenail and Yakkety kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666401/+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 1666413] 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 1666413

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

Title:
  linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing the linux-generic-hwe-16.04 package pulls in linux-generic-
  hwe-16.04-edge, thus the system has linux-image-4.8.0-34-generic and
  linux-image-4.8.0-36-generic installed. The system then boots to
  4.8.0-36.

  Installing linux-generic-hwe-16.04 shouldn't pull in linux-generic-
  hwe-16.04-edge and only one kernel should be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666413/+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 1666413] [NEW] linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge

[Lee Trager]

Public bug reported:

Installing the linux-generic-hwe-16.04 package pulls in linux-generic-
hwe-16.04-edge, thus the system has linux-image-4.8.0-34-generic and
linux-image-4.8.0-36-generic installed. The system then boots to
4.8.0-36.

Installing linux-generic-hwe-16.04 shouldn't pull in linux-generic-
hwe-16.04-edge and only one kernel should be installed.

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

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

Title:
  linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing the linux-generic-hwe-16.04 package pulls in linux-generic-
  hwe-16.04-edge, thus the system has linux-image-4.8.0-34-generic and
  linux-image-4.8.0-36-generic installed. The system then boots to
  4.8.0-36.

  Installing linux-generic-hwe-16.04 shouldn't pull in linux-generic-
  hwe-16.04-edge and only one kernel should be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666413/+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 1628889] Re: [17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu distribution

[Frank Heimes]

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

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

Title:
  [17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu
  distribution

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  For each kernel a message catalogue is available for s390x.
  For better servicablity, customers asking for having this kernel messages as 
part of the distribution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1628889/+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 1666401] [NEW] Export symbol "dev_pm_qos_update_user_latency_tolerance"

[Kai-Heng Feng]

Public bug reported:

To enable NVME APST (autonomous power state transitions) to conserve
NVME power consumption, this commit is required:

commit 034e7906211c18c230ef4da43a1c44796dd5b95e
Author: Andrew Lutomirski 
Date:   Tue Nov 29 17:11:52 2016 -0800

PM / QoS: Export dev_pm_qos_update_user_latency_tolerance

nvme wants a module parameter that overrides the default latency
tolerance.  This makes it easy for nvme to reflect that default in
sysfs.

Signed-off-by: Andy Lutomirski 
Signed-off-by: Rafael J. Wysocki 

It can be cleanly picked into Xenail and Yakkety kernel.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Kai-Heng Feng (kaihengfeng)
 Status: New


** Tags: originate-from-1659177 somerville

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Export symbol "dev_pm_qos_update_user_latency_tolerance"

Status in linux package in Ubuntu:
  New

Bug description:
  To enable NVME APST (autonomous power state transitions) to conserve
  NVME power consumption, this commit is required:

  commit 034e7906211c18c230ef4da43a1c44796dd5b95e
  Author: Andrew Lutomirski 
  Date:   Tue Nov 29 17:11:52 2016 -0800

  PM / QoS: Export dev_pm_qos_update_user_latency_tolerance

  nvme wants a module parameter that overrides the default latency
  tolerance.  This makes it easy for nvme to reflect that default in
  sysfs.

  Signed-off-by: Andy Lutomirski 
  Signed-off-by: Rafael J. Wysocki 

  It can be cleanly picked into Xenail and Yakkety kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666401/+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 1666365] Re: Desktop Effects were Restarting due to graphcal reset in Kubuntu 16:04

[Murali krishnan]

Changed in linux (Ubuntu):
status: New → Confirmed

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

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

Title:
  Desktop Effects were Restarting due to graphcal reset in Kubuntu 16:04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Desktop effects got hung intermittently while browsing videos in
  browser. This is happening after Kernel Update, tried reinstalling
  xserver-xorg-video-intel package as per
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575301 but it did
  not help either, I am using Kubuntu 16.04

  dmesg output:

   1420.773494] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], 
reason: Ring hung, action: reset
  [ 1420.773496] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [ 1420.773497] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [ 1420.773497] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [ 1420.773498] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [ 1420.773499] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [ 1420.775585] drm/i915: Resetting chip after gpu hang
  [ 1522.762995] [drm] stuck on render ring
  [ 1522.764133] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], 
reason: Ring hung, action: reset
  [ 1522.764305] [ cut here ]
  [ 1522.764366] WARNING: CPU: 1 PID: 3092 at 
/build/linux-W6HB68/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  [ 1522.764369] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
  [ 1522.764371] Modules linked in:
  [ 1522.764374]  ipt_MASQUERADE nf_nat_masquerade_ipv4 
vmw_vsock_vmci_transport vsock vmw_vmci iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs eeepc_wmi 
asus_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_hda_core snd_hwdep snd_pcm media snd_seq_midi 
snd_seq_midi_event snd_rawmidi kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_seq snd_seq_device snd_timer input_leds snd cryptd 
serio_raw soundcore shpchp tpm_infineon mei_me mei mac_hid 8250_fintek lpc_ich 
binfmt_misc
  [ 1522.764437]  nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev 
lp parport autofs4 hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper ahci 
libahci r8169 mii syscopyarea sysfillrect sysimgblt fb_sys_fops drm video fjes 
wmi
  [ 1522.764468] CPU: 1 PID: 3092 Comm: kworker/1:1 Not tainted 
4.4.0-62-generic #83-Ubuntu
  [ 1522.764471] Hardware name: ASUS All Series/H81M-CS, BIOS 0401 03/09/2015
  [ 1522.764515] Workqueue: events intel_mmio_flip_work_func [i915]
  [ 1522.764518]  0286 8e417408 880119f67d20 
813f7c63
  [ 1522.764523]  880119f67d68 c0203ab8 880119f67d58 
810812d2
  [ 1522.764528]  880048c039c0 88011fb165c0 88011fb1af00 
0040
  [ 1522.764532] Call Trace:
  [ 1522.764540]  [] dump_stack+0x63/0x90
  [ 1522.764547]  [] warn_slowpath_common+0x82/0xc0
  [ 1522.764551]  [] warn_slowpath_fmt+0x5c/0x80
  [ 1522.764558]  [] ? __switch_to+0x437/0x5c0
  [ 1522.764597]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
  [ 1522.764603]  [] process_one_work+0x165/0x480
  [ 1522.764608]  [] worker_thread+0x4b/0x4c0
  [ 1522.764613]  [] ? process_one_work+0x480/0x480
  [ 1522.764617]  [] ? process_one_work+0x480/0x480
  [ 1522.764621]  [] kthread+0xd8/0xf0
  [ 1522.764625]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 1522.764632]  [] ret_from_fork+0x3f/0x70
  [ 1522.764636]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 1522.764640] ---[ end trace b709120738fd081c ]---
  [ 1522.766309] drm/i915: Resetting chip after gpu hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666365/+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 1651005] Re: Unidentified Trackpad Synaptics

[Launchpad Bug Tracker]

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

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

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

Title:
  Unidentified Trackpad Synaptics

Status in linux package in Ubuntu:
  Expired

Bug description:
  I recently purchased a Sager NP8152-S / Clevo 650RP6 on which I am dual 
booting.
  See http://www.clevo.com/clevo_prodetail.asp?id=958=en

  The trackpad is not detected. xinput does not display a trackpad
  device nor is the device listed in cat /proc/bus/input/devices which
  is uploaded as a file entitled devices.

  The trackpad device is a Synaptics SMBus TouchPad.

  Please let me know if I incorrectly reported this bug as it is my
  first for Ubuntu. I followed the instructions listed on
  https://wiki.ubuntu.com/DebuggingTouchpadDetection in the section
  called "In case your Touchpad doesn't work at all (No response from
  the Touchpad)".

  Thank you!

  


  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.8.0.30.39
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cmuell89   2587 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec 18 17:52:04 2016
  HibernationDevice: RESUME=UUID=a7e110fa-7d4d-4b96-8681-fb7acbb406a9
  InstallationDate: Installed on 2016-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc.
   Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=49d81fc1-d0a2-493f-9a49-c2a533f8d0a6 ro quiet splash i8042.nomux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08LS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08LS2:bd11/11/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651005/+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 1666214] Re: linux: 4.10.0-9.11 -proposed tracker

[Tim Gardner]

** Tags added: block-proposed

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

Title:
  linux: 4.10.0-9.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
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.10.0-9.11 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1666214/+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 1666365] 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 1666365

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

Title:
  Desktop Effects were Restarting due to graphcal reset in Kubuntu 16:04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Desktop effects got hung intermittently while browsing videos in
  browser. This is happening after Kernel Update, tried reinstalling
  xserver-xorg-video-intel package as per
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575301 but it did
  not help either, I am using Kubuntu 16.04

  dmesg output:

   1420.773494] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], 
reason: Ring hung, action: reset
  [ 1420.773496] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [ 1420.773497] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [ 1420.773497] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [ 1420.773498] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [ 1420.773499] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [ 1420.775585] drm/i915: Resetting chip after gpu hang
  [ 1522.762995] [drm] stuck on render ring
  [ 1522.764133] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], 
reason: Ring hung, action: reset
  [ 1522.764305] [ cut here ]
  [ 1522.764366] WARNING: CPU: 1 PID: 3092 at 
/build/linux-W6HB68/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  [ 1522.764369] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
  [ 1522.764371] Modules linked in:
  [ 1522.764374]  ipt_MASQUERADE nf_nat_masquerade_ipv4 
vmw_vsock_vmci_transport vsock vmw_vmci iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs eeepc_wmi 
asus_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_hda_core snd_hwdep snd_pcm media snd_seq_midi 
snd_seq_midi_event snd_rawmidi kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_seq snd_seq_device snd_timer input_leds snd cryptd 
serio_raw soundcore shpchp tpm_infineon mei_me mei mac_hid 8250_fintek lpc_ich 
binfmt_misc
  [ 1522.764437]  nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev 
lp parport autofs4 hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper ahci 
libahci r8169 mii syscopyarea sysfillrect sysimgblt fb_sys_fops drm video fjes 
wmi
  [ 1522.764468] CPU: 1 PID: 3092 Comm: kworker/1:1 Not tainted 
4.4.0-62-generic #83-Ubuntu
  [ 1522.764471] Hardware name: ASUS All Series/H81M-CS, BIOS 0401 03/09/2015
  [ 1522.764515] Workqueue: events intel_mmio_flip_work_func [i915]
  [ 1522.764518]  0286 8e417408 880119f67d20 
813f7c63
  [ 1522.764523]  880119f67d68 c0203ab8 880119f67d58 
810812d2
  [ 1522.764528]  880048c039c0 88011fb165c0 88011fb1af00 
0040
  [ 1522.764532] Call Trace:
  [ 1522.764540]  [] dump_stack+0x63/0x90
  [ 1522.764547]  [] warn_slowpath_common+0x82/0xc0
  [ 1522.764551]  [] warn_slowpath_fmt+0x5c/0x80
  [ 1522.764558]  [] ? __switch_to+0x437/0x5c0
  [ 1522.764597]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
  [ 1522.764603]  [] process_one_work+0x165/0x480
  [ 1522.764608]  [] worker_thread+0x4b/0x4c0
  [ 1522.764613]  [] ? process_one_work+0x480/0x480
  [ 1522.764617]  [] ? process_one_work+0x480/0x480
  [ 1522.764621]  [] kthread+0xd8/0xf0
  [ 1522.764625]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 1522.764632]  [] ret_from_fork+0x3f/0x70
  [ 1522.764636]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 1522.764640] ---[ end trace b709120738fd081c ]---
  [ 1522.766309] drm/i915: Resetting chip after gpu hang

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

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

[Kernel-packages] [Bug 1593293] Re: brd module compiled as built-in

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  brd module compiled as built-in

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

Bug description:
  Block RAM disk module (brd, CONFIG_BLK_DEV_RAM) compiled as 'y', that
  means it is 'built-in' and can not be unloaded or loaded with
  different parameters. This render module completely useless because
  user can not anymore change it size.

  Please change it back to 'm' (module) to allow users use this module.

  Affected kernels (so far): Xenial, Yakkety (4.4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593293/+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 1626740] Re: i915 module requests unreleased GUC firmware files

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  i915 module requests unreleased GUC firmware files

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

Bug description:
  This causes the following warnings when generating the initrd:

  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-14-generic 4.8.0-14.15
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2032 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2032 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 22 18:02:29 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (424 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-14-generic N/A
   linux-backports-modules-4.8.0-14-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS 

[Kernel-packages] [Bug 1651248] Re: Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs caused KVM host hung and all KVM guests down.

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV
  VFs caused KVM host hung and all KVM guests down.

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

Bug description:
  Hello Canonical.

  This appears to be related to LP1636330

  There are additional patches we would like picked up once they
  accepted upstream:

  http://www.spinics.net/lists/kvm/msg141747.html

  [PATCH 1/5] KVM: PPC: XICS cleanup: remove XICS_RM_REJECT
  [PATCH 2/5] KVM: PPC: XICS: correct the real mode ICP rejecting counter
  [PATCH 3/5] KVM: PPC: XICS: Fix potential resend twice issue
  [PATCH 4/5] KVM: PPC: XICS: Implement ICS P/Q states
  [PATCH 5/5] KVM: PPC: XICS: Don't lock twice when doing check resend

  
  Bug history context:

  == Comment: #1 - Application Cdeadmin  - 2016-10-17 11:05:07 ==
   State: Open by: nguyenp on 17 October 2016 09:54:13 

  Ubuntu16.10-KVM host:
  =
  tul612p01.aus.stglabs.ibm.com

  Problem Description:
  ===
  I set up a big configure with multiple guests running SRIOV on tul612fp1 
system. For VFs, I created 64 of them on Ubuntu16.10-KVM host (32 VFs per 
port). I have 6 guests total (mix of ubuntu16.10 and ubuntu16.04.01 guests). I 
assigned 4 VFs for each guest.

  I kicked off network tests on VFs on all guests late Friday night. The test 
ran good on Friday night then it all failed on sometime on Saturday night. 
Right now, all guests are currently are down. Another bad part is that the 
Ubuntu-KVM host is currently hung. So the whole system is very much down. I 
could not get to neither the KVM host nor any guest.
   
  I have talked to my team leads, Siraj I. and Brian C. about the problem this 
morning. They want me to open the defect so that I/O developer to looking into 
the SRIOV problem on Ubuntu16.10-KVM again.

  == Comment: #11 - Paul Nguyen - 2016-10-18 17:55:40 ==
  Worked with Carol earlier today on the SRIOV configuration on this tul612 
system.  Thanks for your help, Carol !

  I just want to document the differences of this configuration .vs. previous 
run configuration. So that we can keep track of what we have tried.
   

  Here are the differences:

  1) In this configuration, 

[Kernel-packages] [Bug 1661300] Re: linux: 4.10.0-6.8 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  linux: 4.10.0-6.8 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
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:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.10.0-6.8 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:Thursday, 02. February 2017 17:47 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/1661300/+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 1657539] Re: [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

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

Bug description:
  Linux-next testing with upstream identified a regression with mkfs
  operations based on an uptream patch accepted into Linus's tree.
  Please consider this commit that corrects the regression:

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539/+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 1660842] Re: apparmor not checking error if security_pin_fs() fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor not checking error if security_pin_fs() fails

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

Bug description:
  The error condition of security_pin_fs() was not being checked which
  will result can result in an oops or use after free, due to the fs pin
  count not being incremented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660842/+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 1628889] Re: [17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu distribution

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  [17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu
  distribution

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  For each kernel a message catalogue is available for s390x.
  For better servicablity, customers asking for having this kernel messages as 
part of the distribution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1628889/+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 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

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 

[Kernel-packages] [Bug 1660832] Re: unix domain socket cross permission check failing with nested namespaces

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

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

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660832/+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 1660836] Re: apparmor auditing denied access of special apparmor .null fi\ le

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor  auditing denied access of special apparmor .null fi\ le

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

Bug description:
  When an fd is disallowed from being inherited during exec, instead of 
  
  closed it is duped to a special apparmor/.null file. This prevents the
  
  fd from being reused by another file in case the application expects  
  
  the original file on a give fd (eg stdin/stdout etc). This results in 
  
  a denial message like 
  
  [32375.561535] audit: type=1400 audit(1478825963.441:358): apparmor="DENIED" 
op\
  eration="file_inherit" namespace="root//lxd-t_" 
profile="/sbin/dhc\
  lient" name="/dev/pts/1" pid=16795 comm="dhclient" requested_mask="wr" 
denied_m\
  ask="wr" fsuid=165536 ouid=165536 
  

  
  Further access to the fd is resultin in the rather useless denial message 
  
  of
  
  [32375.566820] audit: type=1400 audit(1478825963.445:359): apparmor="DENIED" 
op\
  eration="file_perm" namespace="root//lxd-t_" 
profile="/sbin/dhclie\
  nt" name="/apparmor/.null" pid=16795 comm="dhclient" requested_mask="w" 
denied_\
  mask="w" fsuid=165536 ouid=0  
  

  
  since we have the original denial, the noisy and useless .null based  
  
  denials can be skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660836/+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 1660840] Re: apparmor oops in bind_mnt when dev_path lookup fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor oops in bind_mnt when dev_path lookup fails

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

Bug description:
  Bind mounts can oops when devname lookup fails because the devname is 
  
  unintialized and used in auditing the denial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840/+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 1638996] Re: apparmor's raw_data file in securityfs is sometimes truncated

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor's raw_data file in securityfs is sometimes truncated

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  It looks like sometimes apparmor's securityfs output is sometimes
  truncated,

  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al
  total 0
  drwxr-xr-x  3 root root 0 Nov  3 16:45 .
  drwxr-xr-x 13 root root 0 Nov  3 16:44 ..
  -r--r--r--  1 root root 0 Nov  3 16:45 attach
  -r--r--r--  1 root root 0 Nov  3 16:45 mode
  -r--r--r--  1 root root 0 Nov  3 16:45 name
  drwxr-xr-x  3 root root 0 Nov  3 16:45 profiles
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_abi
  -r--r--r--  1 root root 46234 Nov  3 16:45 raw_data
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_hash
  -r--r--r--  1 root root 0 Nov  3 16:45 sha1
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 cat raw_data > /tmp/out
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al /tmp/out 
  -rw-r--r-- 1 root root 4009 Nov  3 16:55 /tmp/out

  and

  2016-11-03 10:58:01 tych0 jjohansen: hi, http://paste.ubuntu.com/23421551/
  2016-11-03 10:58:18 tych0 it looks like fstat is lying to me about the size 
of the policy
  2016-11-03 10:59:20 @jjohansen  tych0: hrmm interesting, can you zip up the 
/tmp/out file so I can see it looks like a complete policy file?
  2016-11-03 11:00:03 @jjohansen  something is definitely not right there. hrmmm
  2016-11-03 11:00:26 @jjohansen  the size is set by the input buffer size
  2016-11-03 11:00:28 tych0 jjohansen: http://files.tycho.ws/tmp/out
  2016-11-03 11:00:36 tych0 yeah, i assume
  2016-11-03 11:01:15 @jjohansen  my guess is something is messing up in the 
seq_file walk of the policy
  2016-11-03 11:02:38 @jjohansen  tych0: yep the file is truncated, can you 
open a bug and I will start looking for it
  2016-11-03 11:03:14 tych0 jjohansen: sure, just on linux?
  2016-11-03 11:03:35 @jjohansen  tych0: yeah for now, just linux
  2016-11-03 11:03:43 @jjohansen  we can add others if needed later
  2016-11-03 11:03:44 tych0 jjohansen: FWIW, somehow it seems racy, becasue 
sometimes it works and sometimes it doesn't

To manage notifications about 

[Kernel-packages] [Bug 1660634] Re: Enable CONFIG_NET_DROP_MONITOR=m in Ubuntu Kernel

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  Enable CONFIG_NET_DROP_MONITOR=m in Ubuntu Kernel

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

Bug description:
  CONFIG_NET_DROP_MONITOR=m is needed for the dropwatch software.

  At the moment dropwatch is packaged only for Fedora:
  https://fedorahosted.org/dropwatch/

  The kernel compiled with CONFIG_NET_DROP_MONITOR=n makes not possible
  to use this software.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660634/+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 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
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:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+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 1660834] Re: apparmor label leak when new label is unused

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor label leak when new label is unused

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

Bug description:
  When a new label is created, it is created with a proxy in a circular 
  
  ref count that is broken by replacement. However if the label is not  
  
  used it will never be replaced and the circular ref count will never  
  
  be broken resulting in a leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660834/+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 1663687] Re: [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)

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

Bug description:
  Patchset:

  1/6 Enable tracking of queue depth.

  2/6 Remove the artificially imposed restriction on max segment size.

  3/6 Enable multi-q support. We will allocate the outgoing channel using
  the following policy:

  1. We will make every effort to pick a channel that is in the
 same NUMA node that is initiating the I/O
  2. The mapping between the guest CPU and the outgoing channel
 is persistent.

  4/6 Properly set SRB flags when hosting device supports tagged queuing.
  This patch improves the performance on Fiber Channel disks.

  5/6 When sense message is present on error, we should pass along to the upper
  layer to decide how to deal with the error.
  This patch fixes connectivity issues with Fiber Channel devices.

  6/6 On I/O errors, the Windows driver doesn't set data_transfer_length
  on error conditions other than SRB_STATUS_DATA_OVERRUN.
  In these cases we need to set data_transfer_length to 0,
  indicating there is no data transferred. On SRB_STATUS_DATA_OVERRUN,
  data_transfer_length is set by the Windows driver to the actual data 
transferred.

  The new feature (multi-q) in this patchset require boot line
  parameters to enable so they are safe to integrate.

  K. Y. Srinivasan (3):
storvsc: Enable tracking of queue depth
storvsc: Remove the restriction on max segment size
storvsc: Enable multi-queue support

  Long Li (3):
storvsc: use tagged SRB requests if supported by the device
storvsc: properly handle SRB_ERROR when sense message is present
storvsc: properly set residual data length on errors

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=40630f462824ee24bc00d692865c86c3828094e0

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

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

[Kernel-packages] [Bug 1660849] Re: apparmor refcount leak of profile namespace when removing profiles

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor refcount leak of profile namespace when removing profiles

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

Bug description:
  When doing profile removal, the parent ns of the profiles is taken,
  but the reference isn't being put, resulting in the ns never being
  freed even after it is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660849/+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 1662201] Re: linux: 4.10.0-7.9 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  linux: 4.10.0-7.9 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
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:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.10.0-7.9 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:Uploaded
  kernel-phase-changed:Tuesday, 07. February 2017 23:25 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1662201/+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 1660833] Re: apparmor reference count bug in label_merge_insert()

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor reference count bug in label_merge_insert()

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

Bug description:
  @new does not have a reference taken locally and should not have its  
  
  reference put locally either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660833/+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 1661887] Re: AMDGPU support for CIK parts in kernel config?

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  AMDGPU support for CIK parts in kernel config?

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

Bug description:
  Hi, I am "nauticalnexus", I'd like to ask for AMDGPU support for
  CIK(Sea Islands, 390, 290, 290x, 390x, etc) cards in the standard and
  lowlatency linux kernel. There is no reason for it to be disabled.
  I've been using it for a long time on various different distributions
  and kernels and I've had no issues with it. I'd love to see it in the
  Ubuntu Linux kernel :) Thanks!

  P.S: I was told to create a bug report for this, I originally asked
  this as a question.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661887/+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 1660846] Re: apparmor leaking securityfs pin count

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor leaking securityfs pin count

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

Bug description:
  apparmor is leaking pinfs refcoutn when inode setup fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660846/+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 1660845] Re: apparmor reference count leak when securityfs_setup_d_inode\ () fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  apparmor reference count leak when securityfs_setup_d_inode\ () fails

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

Bug description:
  apparmor is leaking the parent ns ref count, by directly returning the
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660845/+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 1664217] Re: linux: 4.10.0-8.10 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

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

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

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

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.10.0-8.10 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1664217/+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 1666365] [NEW] Desktop Effects were Restarting due to graphcal reset in Kubuntu 16:04

[Murali krishnan]

Public bug reported:

Desktop effects got hung intermittently while browsing videos in
browser. This is happening after Kernel Update, tried reinstalling
xserver-xorg-video-intel package as per
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575301 but it did
not help either, I am using Kubuntu 16.04

dmesg output:

 1420.773494] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], reason: 
Ring hung, action: reset
[ 1420.773496] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[ 1420.773497] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[ 1420.773497] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[ 1420.773498] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[ 1420.773499] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1420.775585] drm/i915: Resetting chip after gpu hang
[ 1522.762995] [drm] stuck on render ring
[ 1522.764133] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], 
reason: Ring hung, action: reset
[ 1522.764305] [ cut here ]
[ 1522.764366] WARNING: CPU: 1 PID: 3092 at 
/build/linux-W6HB68/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
[ 1522.764369] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
[ 1522.764371] Modules linked in:
[ 1522.764374]  ipt_MASQUERADE nf_nat_masquerade_ipv4 vmw_vsock_vmci_transport 
vsock vmw_vmci iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack 
br_netfilter bridge stp llc aufs eeepc_wmi asus_wmi sparse_keymap 
snd_hda_codec_realtek snd_hda_codec_generic uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev 
snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_hda_core snd_hwdep snd_pcm media snd_seq_midi snd_seq_midi_event 
snd_rawmidi kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq snd_seq_device snd_timer input_leds snd cryptd serio_raw soundcore 
shpchp tpm_infineon mei_me mei mac_hid 8250_fintek lpc_ich binfmt_misc
[ 1522.764437]  nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp 
parport autofs4 hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper ahci 
libahci r8169 mii syscopyarea sysfillrect sysimgblt fb_sys_fops drm video fjes 
wmi
[ 1522.764468] CPU: 1 PID: 3092 Comm: kworker/1:1 Not tainted 4.4.0-62-generic 
#83-Ubuntu
[ 1522.764471] Hardware name: ASUS All Series/H81M-CS, BIOS 0401 03/09/2015
[ 1522.764515] Workqueue: events intel_mmio_flip_work_func [i915]
[ 1522.764518]  0286 8e417408 880119f67d20 
813f7c63
[ 1522.764523]  880119f67d68 c0203ab8 880119f67d58 
810812d2
[ 1522.764528]  880048c039c0 88011fb165c0 88011fb1af00 
0040
[ 1522.764532] Call Trace:
[ 1522.764540]  [] dump_stack+0x63/0x90
[ 1522.764547]  [] warn_slowpath_common+0x82/0xc0
[ 1522.764551]  [] warn_slowpath_fmt+0x5c/0x80
[ 1522.764558]  [] ? __switch_to+0x437/0x5c0
[ 1522.764597]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
[ 1522.764603]  [] process_one_work+0x165/0x480
[ 1522.764608]  [] worker_thread+0x4b/0x4c0
[ 1522.764613]  [] ? process_one_work+0x480/0x480
[ 1522.764617]  [] ? process_one_work+0x480/0x480
[ 1522.764621]  [] kthread+0xd8/0xf0
[ 1522.764625]  [] ? kthread_create_on_node+0x1e0/0x1e0
[ 1522.764632]  [] ret_from_fork+0x3f/0x70
[ 1522.764636]  [] ? kthread_create_on_node+0x1e0/0x1e0
[ 1522.764640] ---[ end trace b709120738fd081c ]---
[ 1522.766309] drm/i915: Resetting chip after gpu hang

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

Title:
  Desktop Effects were Restarting due to graphcal reset in Kubuntu 16:04

Status in linux package in Ubuntu:
  New

Bug description:
  Desktop effects got hung intermittently while browsing videos in
  browser. This is happening after Kernel Update, tried reinstalling
  xserver-xorg-video-intel package as per
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575301 but it did
  not help either, I am using Kubuntu 16.04

  dmesg output:

   1420.773494] [drm] GPU HANG: ecode 7:0:0x85dc, in kwin_x11 [2055], 
reason: Ring hung, action: reset
  [ 1420.773496] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [ 1420.773497] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [ 1420.773497] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [ 1420.773498] [drm] The gpu crash 

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[Keith]

I did have bootchart installed.  So I removed and purged it and went as
far as moving the hidden .bootchart directory to the trash (couldn't
delete it) and then restarting the computer.  So far this seems to have
resolved the problem for me.  I'm no longer seeing the slow but steady
increase in memory usage.  So my thanks to Jacek Kończewski for his
comment above (#47).

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+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 1520988] Re: Copy of large files from USB3 card reader fails mid-way

[Christopher M. Penalver]

Kevin Brubeck Unhammer, on the hardware you originally reported with
(Lenovo A740), to keep this relevant to upstream, one would want to
periodically check for, and test the latest mainline kernel (now 4.10)
as it is released.

Could you please advise?

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

Title:
  Copy of large files from USB3 card reader fails mid-way

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've got a "Lexar Professional Workflow XR1" CF card reader that
  supports USB3, and has worked fine for regular JPG/CR2 images (sizes
  up to about 20 MB), but when I tried some videos (which were 170MB and
  up), the copy would fail around midway with "Error Splicing File:
  Input/Output Error" from Thunar, and dmesg showed messages like:

  [  +9,232995] usb 2-3: Disable of device-initiated U1 failed.
  [  +5,006028] usb 2-3: Disable of device-initiated U2 failed.
  [  +0,168540] usb 2-3: reset SuperSpeed USB device number 10 using xhci_hcd
  [  +1,126795] sd 12:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  +0,11] sd 12:0:0:0: [sdb] Sense Key : Unit Attention [current] 
  [  +0,07] sd 12:0:0:0: [sdb] Add. Sense: Not ready to ready change, 
medium may have changed
  [  +0,06] sd 12:0:0:0: [sdb] CDB: Read(10) 28 00 00 67 53 ce 00 00 02 00
  [  +0,05] blk_update_request: I/O error, dev sdb, sector 6771662
  [  +0,08] Buffer I/O error on dev sdb1, logical block 3385704, async page 
read
  [ +10,494574] usb 2-3: Disable of device-initiated U1 failed.
  [  +5,006046] usb 2-3: Disable of device-initiated U2 failed.
  [  +0,168624] usb 2-3: reset SuperSpeed USB device number 10 using xhci_hcd
  [  +1,126823] sd 12:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  +0,09] sd 12:0:0:0: [sdb] Sense Key : Unit Attention [current] 
  [  +0,05] sd 12:0:0:0: [sdb] Add. Sense: Not ready to ready change, 
medium may have changed
  [  +0,05] sd 12:0:0:0: [sdb] CDB: Read(10) 28 00 00 68 53 76 00 00 02 00
  [  +0,03] blk_update_request: I/O error, dev sdb, sector 6837110
  [  +0,07] Buffer I/O error on dev sdb1, logical block 3418428, async page 
read

  I tried a fsck.vfat, but that didn't help. Ejecting and unmounting, I
  was able to copy one file, but not the rest (tried a couple times,
  just got the same errors).

  This computer only has USB3 ports. So I tried another computer
  (running Xubuntu 14.04) that had a non-USB3-port, and there the copy
  worked just fine.

  
  On connecting, dmesg says:

  [nov.29 20:56] usb 2-3: new SuperSpeed USB device number 12 using xhci_hcd
  [  +0,018698] usb 2-3: New USB device found, idVendor=05dc, idProduct=ba02
  [  +0,08] usb 2-3: New USB device strings: Mfr=3, Product=4, 
SerialNumber=5
  [  +0,05] usb 2-3: Product: WorkflowCFR1
  [  +0,03] usb 2-3: Manufacturer: Lexar
  [  +0,04] usb 2-3: SerialNumber: 5018
  [  +0,002362] usb-storage 2-3:1.0: USB Mass Storage device detected
  [  +0,000135] scsi host14: usb-storage 2-3:1.0
  [  +1,000955] scsi 14:0:0:0: Direct-Access LexarWorkflowCFR1 0822 
PQ: 0 ANSI: 6
  [  +0,000297] sd 14:0:0:0: Attached scsi generic sg1 type 0
  [  +1,104094] sd 14:0:0:0: [sdb] 62537328 512-byte logical blocks: (32.0 
GB/29.8 GiB)
  [  +0,000598] sd 14:0:0:0: [sdb] Write Protect is off
  [  +0,09] sd 14:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [  +0,000646] sd 14:0:0:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
  [  +0,004239]  sdb: sdb1
  [  +0,001969] sd 14:0:0:0: [sdb] Attached SCSI removable disk

  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
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kiwibird   1912 F pulseaudio
   /dev/snd/controlC1:  kiwibird   1912 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Nov 29 20:52:51 2015
  HibernationDevice: RESUME=UUID=dc4226ca-3ebe-4611-95ac-c1a0ccbb7d7a
  InstallationDate: Installed on 2015-06-04 (178 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: LENOVO F0AM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=91533e8a-b5ca-4447-8c4a-b5bb2d095238 ro noprompt persistent
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-24 (35 days ago)
  dmi.bios.date: 09/30/2014
  

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

[Christopher M. Penalver]

Tormod Volden, to track your hardware, it will help immensely if you filed a 
new report with Ubuntu, using the default repository kernel (not 
mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

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

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

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

  

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

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

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

[Kernel-packages] [Bug 1643341] Re: Unexpected shutdown

[Christopher M. Penalver]

Sam_, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643341/comments/21
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  Unexpected shutdown

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This happens twice in between a short time, 2-5 minutes, after the computer 
was turned on and Ubuntu desktop has started.
  It never happens a third time.
  From Ubuntu desktop, the cooler starts to run, a shutdown dialog with four 
options appears and computer turns off.
  I turn it on again and watch the same procedure happen again.
  I turn it on the third time, all is fine.

  4.4.0-47.68
  ACPI: Thermal Zone [TZ0] (11 C)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68 and 4.4.0-49.70
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zootie 1897 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov 20 17:19:01 2016
  HibernationDevice: RESUME=UUID=6a848b08-24f4-499b-8281-8ba10097226d
  InstallationDate: Installed on 2016-11-02 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160823)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 5986:055c Acer, Inc
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=31f6cc2f-d9df-473c-be2d-fd1abf719500 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RB
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/16/2015:svnNotebook:pnW65_W67RB:pvrNotApplicable:rvnNotebook:rnW65_W67RB:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65_W67RB
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643341/+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 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

[Christopher M. Penalver]

Dea1993, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532746/comments/63
regarding this being fixed with a BIOS update. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Tags removed: latest-bios-f.13
** Tags added: bios-outdated-f.41

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

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

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  WORKAROUND: Use kernel parameter:
  i8042.dumbkbd

  the only way to solve momentarily the problem, is pressing for some
  seconds the only SHIFT key, after that, the problems disappears
  indefinitely, or until the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  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 

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Christopher M. Penalver]

htrex, so your problem may be tracked, it will help immensely if you filed a 
new report with Ubuntu, using the default repository kernel (not 
mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

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

Bug description:
  Continued in Bug #1622322.

  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 892544] Re: Unity slow after resume from suspend

[Christopher M. Penalver]

Samir M (samir-menon-cs), it will help immensely if you filed a new report with 
Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) 
via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

Title:
  Unity slow after resume from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  After resuming from suspend unity feels like it is very slow.

  How to play:

  Go to Unity Dash, show all applications, move icons up and down with
  the scroll bar, suspend and resume, perform the same operation and
  notice that is very slow.

  This already happens with the (cd or usb) of installation.

  This bug only happens with free radeon driver with driver fglrx does
  not happen.

  This only happens in unity, this does not happen in either Gnome Shell
  or Unity 2D.

  I do not know if it's a bug in Unity or compiz, but "unity --reset"
  solves the problem until the next suspend / resume.

  I do not know if this bug may be related to #782810 or #803943, but I
  did not notice any increase in CPU consumption.

  This bug occurs on a clean install of 11.10 [64 bits]   with a ATI
  Radeon 5770 graphics card,  Asus P6T Deluxe V2 Motherboard, Micro
  Intel Core™ i7-950 y SSD OCZ Vertex2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/892544/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

[Christopher M. Penalver]

Niklas Sombert, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/comments/20
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
   iwlwifi: Microcode SW error detected. Restarting 0x200

Status in linux package in Ubuntu:
  Invalid

Bug description:
  My wifi won't work after I wake my laptop up from standby.

  This problem looks quite the same as #1099487 or #944271.

  But I experienced this bug on Xenial with 4.4.0-22-generic (amd64).

  A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve
  the problem. (A reboot does.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niklas 2175 F pulseaudio
   /dev/snd/controlC0:  niklas 2175 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 08:23:06 2016
  InstallationDate: Installed on 2015-12-11 (174 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  MachineType: LENOVO 20E8S00600
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ 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: 02/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JHET20WW (1.00 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20E8S00600
  dmi.product.version: ThinkPad 11e
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1651981] Re: shaking screen

[Christopher M. Penalver]

** Tags added: cherry-pick

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

Title:
  shaking screen

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After login into Ubuntu the screen starts to shake permanently.
  The login screen is still fine, problem start after log in.
  The problem is caused by last kernel update: running Ubuntu with the older 
kernel 4.8.0-30-generic fixes the issue.

  Upstream patch submission:
  https://lists.freedesktop.org/archives/dri-devel/2016-December/128331.html

  WORKAROUND: Revert:
  # first bad commit: [9cc4fd5b9fbb0d74e77c81521da1e2fe712f6787] 
drm/radeon/si_dpm: workaround for SI kickers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   7797 F pulseaudio
   /dev/snd/controlC1:  afiergol   7797 F pulseaudio
   /dev/snd/seq:timidity   6155 F timidity
  Date: Thu Dec 22 10:02:30 2016
  HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831
  InstallationDate: Installed on 2015-04-02 (629 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (66 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651981/+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 1643165] Re: Wifi drops out regularly after upgrade to 16.04

[Christopher M. Penalver]

** Description changed:

  Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll
  drop out for 20s every few minutes then come back. network manager still
  thinks that it is connected, but websites will fail to load/time out.
  Reconnecting to the AP (by clicking on it in network-manager) seems to
  re-establish the connection.  I typically sit 6ft from the access point
  so the signal is strong and much stronger than any nearby APs.
+ 
+ WORKAROUND: Disable 40MHz bands on my router.
  
  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  shaun  2212 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  shaun  2212 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 19 10:39:23 2016
  HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
  InstallationDate: Installed on 2012-09-26 (1515 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7
  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
+  linux-restricted-modules-4.4.0-45-generic N/A
+  linux-backports-modules-4.4.0-45-generic  N/A
+  linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago)
  dmi.bios.date: 07/12/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P03AAC
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 900X3C/900X3D/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

Title:
  Wifi drops out regularly after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll
  drop out for 20s every few minutes then come back. network manager
  still thinks that it is connected, but websites will fail to load/time
  out. Reconnecting to the AP (by clicking on it in network-manager)
  seems to re-establish the connection.  I typically sit 6ft from the
  access point so the signal is strong and much stronger than any nearby
  APs.

  WORKAROUND: Disable 40MHz bands on my router.

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaun  2212 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 19 10:39:23 2016
  HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
  InstallationDate: Installed on 2012-09-26 (1515 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago)
  dmi.bios.date: 07/12/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P03AAC
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 

[Kernel-packages] [Bug 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install

[Christopher M. Penalver]

Andrew F in Australia, could you please advise which version of the
kernel you tested specifically?

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

Title:
  [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Gigabyte P57 laptop

  Fresh install, 10 days old, updated yesterday so software/kernel
  should be current.

  Some function keys work.
  Function plus F1 puts the machine to sleep
  Function plus F7, F8, F9 control the volume

  However,
  Pressing Function plus F2 does not turn off wireless
  Pressing Function plus F3,F4 do not change brightness
  Function plus F5 does not change output to LCD or Monitor
  Pressing Function plus F6 does not toggle touchpad (a separate bug in this 
machine, but the Elantech touchpad is recognised at the moment.)
  Function plus F10 does not turn the display off
  Function plus F11 does not turn off bluetooth
  Function plus F12 does not disable the camera

  Please let me know if you need any further troubleshooting

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horace 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 26 07:44:13 2016
  HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
  InstallationDate: Installed on 2016-11-13 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE P57
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB0B
  dmi.board.asset.tag: Default string
  dmi.board.name: P57
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: P57
  dmi.product.version: Default string
  dmi.sys.vendor: GIGABYTE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+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 1590985] Re: Wifi non-functional after suspend (Intel 6205)

[Tormod Volden]

Other possible workarounds to try out:
https://bugzilla.redhat.com/show_bug.cgi?id=737424
https://ubuntuforums.org/showthread.php?t=2004690=4

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

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

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

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

  

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

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

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

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

[Tormod Volden]

Seeing the same as OP with "Intel Corporation Centrino Advanced-N 6235
(rev 24)" on 16.04.2 with 4.8.0-34-generic.

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

** Bug watch added: Red Hat Bugzilla #737424
   https://bugzilla.redhat.com/show_bug.cgi?id=737424

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

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

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

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

  

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

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

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

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

[Christopher M. Penalver]

noob saibot, it will help immensely if you filed a new report with Ubuntu, 
using the default repository kernel (not mainline/upstream/3rd party) via a 
terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

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

Title:
  iwlwifi queue stuck, Microcode SW error detected,  "ieee80211 phy0:
  Hardware restart was requested

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64
  (4.4.0-34.53), i've not used this notebook to much lately), my wifi
  connection is unstable, often hangs and therefore spread a lot of bad
  karma to all networking applications. My log shows entries of the
  following pattern

  Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi :02:00.0: Queue 2 
stuck for 1 ms.
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi :02:00.0: Current 
SW read_ptr 86 write_ptr 124
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: : 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00  
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi :02:00.0: FH 
TRBs(0) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi :02:00.0: FH 
TRBs(1) = 0x80102065
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi :02:00.0: FH 
TRBs(2) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi :02:00.0: FH 
TRBs(3) = 0x8031
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi :02:00.0: FH 
TRBs(4) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi :02:00.0: FH 
TRBs(5) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi :02:00.0: FH 
TRBs(6) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi :02:00.0: FH 
TRBs(7) = 0x00709052
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi :02:00.0: Q 0 is 
active and mapped to fifo 3 ra_tid 0x [2,2]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi :02:00.0: Q 1 is 
active and mapped to fifo 2 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi :02:00.0: Q 2 is 
active and mapped to fifo 1 ra_tid 0x [86,124]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi :02:00.0: Q 3 is 
active and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi :02:00.0: Q 4 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi :02:00.0: Q 5 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi :02:00.0: Q 6 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi :02:00.0: Q 7 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi :02:00.0: Q 8 is 
active and mapped to fifo 3 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi :02:00.0: Q 9 is 
active and mapped to fifo 7 ra_tid 0x [83,83]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi :02:00.0: Q 10 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519726] iwlwifi :02:00.0: Q 11 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519776] iwlwifi :02:00.0: Q 12 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519826] iwlwifi :02:00.0: Q 13 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519876] iwlwifi :02:00.0: Q 14 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519925] iwlwifi :02:00.0: Q 15 is 
active and mapped to fifo 5 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519975] iwlwifi :02:00.0: Q 16 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520025] iwlwifi :02:00.0: Q 17 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520075] iwlwifi :02:00.0: Q 18 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520125] iwlwifi :02:00.0: Q 19 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520175] iwlwifi :02:00.0: Q 20 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520225] iwlwifi :02:00.0: Q 21 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 

[Kernel-packages] [Bug 1641432] Re: Logout after supend

[Christopher M. Penalver]

besto, to clarify, did you test the kernel requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641432/comments/3
or did you test a kernel while booted into a newer version of Ubuntu?

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

Title:
  Logout after supend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  well, since ubuntu 16.04 I have the following bug:
  When I close the lid and the ubuntu on Lenovo Thinkpad T410 goes to suspend, 
it sometimes (not always) hangs on wake up. In dmesg I gett differeing error 
messages:

  [ 5115.965586] [drm] stuck on render ring
  [ 5115.972313] [drm] GPU HANG: ecode 5:0:0x87f6fff8, in Xorg [1318], reason: 
Ring hung, action: reset
  [ 5115.972317] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [ 5115.972318] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [ 5115.972319] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [ 5115.972320] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [ 5115.972322] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [ 5115.975614] drm/i915: Resetting chip after gpu hang

  and today:
  [94130.207146] [drm] stuck on render ring
  [94130.212672] [drm] GPU HANG: ecode 5:0:0xb5cafffb, in compiz [12158], 
reason: Ring hung, action: reset
  [94130.215083] drm/i915: Resetting chip after gpu hang
  [94136.170991] [drm] stuck on render ring
  [94136.176190] [drm] GPU HANG: ecode 5:0:0xb5cafffb, in compiz [12158], 
reason: Ring hung, action: reset
  [94136.176339] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [94136.180454] drm/i915: Resetting chip after gpu hang

  Well,this is not freedesktop.org, however, maybe someone could help.
  It is a bit annoying, since there is the potential to lose data, when
  all programs close.

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  uname -a
  Linux bs 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  Anybody knows something?

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bs25246 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Nov 13 17:54:05 2016
  HibernationDevice: RESUME=UUID=5a21ddc4-aea5-46c7-98c7-d019e396a35e
  InstallationDate: Installed on 2015-02-02 (650 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 003: ID 05c6:9204 Qualcomm, Inc. 
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 2537UEZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=UUID=2f39ed28-4b66-43a9-83ee-eb33d12ea876 ro quiet splash 
"acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (95 days ago)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2537UEZ
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537UEZ:pvrThinkPadT410:rvnLENOVO:rn2537UEZ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2537UEZ
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641432/+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 1653361] Re: [Asus E502SA] Suspend/resume triggers random hang

[Christopher M. Penalver]

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

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

Title:
  [Asus E502SA] Suspend/resume triggers random hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Resuming from suspend hangs the computer. This doesn't happen with
  Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jamse  1839 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 31 18:01:35 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d46d5e40-bd0f-41a5-87bb-f4f470f7b4d6
  InstallationDate: Installed on 2016-12-14 (17 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd
   Bus 001 Device 006: ID 13d3:3423 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E502SA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=17457b58-fc63-470b-a916-2eedb0dbd58e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E502SA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E502SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE502SA.300:bd07/20/2016:svnASUSTeKCOMPUTERINC.:pnE502SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE502SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E502SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653361/+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 1624917] Re: external usb-3 disk crashes when writing.

[Tormod Volden]

Possible UAS module bug, see
https://bbs.archlinux.org/viewtopic.php?pid=1455956#p1455956

Blacklisting UAS for the given device is probably a workaround.

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

Title:
  external usb-3 disk crashes when writing.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using two Intenso Memory Box 2TB on a NUC NUC5PPYH USB-3 Port.

  Executing a "dd if=/dev/sda1 of=/dev/null" seems to work fine but if i
  am writing on one of them, the drives hang and the disk is unusable.

  The dmesg shows as follows:

  [ 3542.821686] sd 2:0:0:0: [sda] tag#25 uas_eh_abort_handler 0 uas-tag 26 
inflight: CMD OUT
  [ 3542.821720] sd 2:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 2c 57 94 00 00 
04 00 00
  [ 3542.930180] sd 2:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 25 
inflight: CMD OUT
  [ 3542.930198] sd 2:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 2c 57 90 00 00 
04 00 00
  [ 3543.042188] sd 2:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 
inflight: CMD OUT
  [ 3543.042223] sd 2:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 2c 57 8c 00 00 04 
00 00
  [ 3543.154371] sd 2:0:0:0: [sda] tag#23 uas_eh_abort_handler 0 uas-tag 24 
inflight: CMD OUT
  [ 3543.154405] sd 2:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 2c 57 88 00 00 
04 00 00
  [ 3543.266394] sd 2:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 23 
inflight: CMD OUT
  [ 3543.266428] sd 2:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 2c 57 84 00 00 
04 00 00
  [ 3543.378226] sd 2:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 22 
inflight: CMD OUT
  [ 3543.378260] sd 2:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 2c 57 80 00 00 
04 00 00
  [ 3543.490188] sd 2:0:0:0: [sda] tag#14 uas_eh_abort_handler 0 uas-tag 15 
inflight: CMD OUT
  [ 3543.490223] sd 2:0:0:0: [sda] tag#14 CDB: Write(10) 2a 00 2c 57 7c 00 00 
04 00 00
  [ 3543.602187] sd 2:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 14 
inflight: CMD OUT
  [ 3543.602204] sd 2:0:0:0: [sda] tag#13 CDB: Write(10) 2a 00 2c 57 78 00 00 
04 00 00
  [ 3543.714315] sd 2:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 13 
inflight: CMD OUT
  [ 3543.714347] sd 2:0:0:0: [sda] tag#12 CDB: Write(10) 2a 00 2c 57 74 00 00 
04 00 00
  [ 3543.826343] sd 2:0:0:0: [sda] tag#11 uas_eh_abort_handler 0 uas-tag 12 
inflight: CMD OUT
  [ 3543.826378] sd 2:0:0:0: [sda] tag#11 CDB: Write(10) 2a 00 2c 57 70 00 00 
04 00 00
  [ 3543.938161] sd 2:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 11 
inflight: CMD OUT
  [ 3543.938192] sd 2:0:0:0: [sda] tag#10 CDB: Write(10) 2a 00 2c 57 6c 00 00 
04 00 00
  [ 3544.050187] sd 2:0:0:0: [sda] tag#9 uas_eh_abort_handler 0 uas-tag 10 
inflight: CMD OUT
  [ 3544.050223] sd 2:0:0:0: [sda] tag#9 CDB: Write(10) 2a 00 2c 57 68 00 00 04 
00 00
  [ 3544.162183] sd 2:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 9 
inflight: CMD OUT
  [ 3544.162218] sd 2:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 2c 57 64 00 00 04 
00 00
  [ 3544.274400] sd 2:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 8 
inflight: CMD OUT
  [ 3544.274436] sd 2:0:0:0: [sda] tag#7 CDB: Write(10) 2a 00 2c 57 60 00 00 04 
00 00
  [ 3544.386313] sd 2:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 7 
inflight: CMD OUT
  [ 3544.386347] sd 2:0:0:0: [sda] tag#6 CDB: Write(10) 2a 00 2c 57 5c 00 00 04 
00 00
  [ 3544.498194] sd 2:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 6 
inflight: CMD OUT
  [ 3544.498229] sd 2:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 2c 57 58 00 00 04 
00 00
  [ 3544.610187] sd 2:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 21 
inflight: CMD OUT
  [ 3544.610222] sd 2:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 2c 57 54 00 00 
04 00 00
  [ 3544.722188] sd 2:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 20 
inflight: CMD OUT
  [ 3544.72] sd 2:0:0:0: [sda] tag#20 CDB: Write(10) 2a 00 2c 57 50 00 00 
04 00 00
  [ 3544.834379] sd 2:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 17 
inflight: CMD OUT
  [ 3544.834408] sd 2:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 2c 57 4c 00 00 
04 00 00
  [ 3544.946262] sd 2:0:0:0: [sda] tag#18 uas_eh_abort_handler 0 uas-tag 19 
inflight: CMD OUT
  [ 3544.946298] sd 2:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 2c 57 48 00 00 
04 00 00
  [ 3545.058196] sd 2:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 18 
inflight: CMD OUT
  [ 3545.058230] sd 2:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 2c 57 24 00 00 
04 00 00
  [ 3545.170185] sd 2:0:0:0: [sda] tag#15 uas_eh_abort_handler 0 uas-tag 16 
inflight: CMD OUT
  [ 3545.170219] sd 2:0:0:0: [sda] tag#15 CDB: Write(10) 2a 00 2c 57 20 00 00 
04 00 00
  [ 3545.282185] sd 2:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 
inflight: CMD OUT
  [ 3545.282220] sd 2:0:0:0: [sda] tag#4 CDB: Write(10) 2a 00 2c 57 1c 00 00 04 
00 00
  [ 3545.394402] sd 2:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 
inflight: CMD OUT
  [ 3545.394437] sd 2:0:0:0: 

[Kernel-packages] [Bug 1628061] Re: iwl4965 crashes randomly

[Christopher M. Penalver]

Michael Kiermaier, the way to make the issue go away permanent is to
determine why disabling power management is necessary in the first
place.

Hence, to keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 4.10) as it is
released.

Could you please advise?

** Description changed:

  On my Lenovo X61s, WLAN randomly stops working, typically after a few hours 
of running time. I don't know any remedy but to reboot.
  This behavior started maybe 2 or 3 months ago. My maching is usually kept up 
to date, so the problem might be caused by some kernel update at that time.
  
  The relevant part in dmesg (attached) starts with
  [ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out 
after 500ms.
  [ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110
  [ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.424162] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 0
  [ 5813.924092] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.924107] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 5
  [ 5814.052099] iwl4965 :03:00.0: Queue 4 stuck for 2500 ms.
  [ 5814.052124] iwl4965 :03:00.0: On demand firmware reload
  [ 5814.424142] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.424168] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 6
  [ 5814.424421] iwl4965 :03:00.0: Master Disable Timed Out, 100 usec
  [ 5814.424468] ieee80211 phy0: Hardware restart was requested
  [ 5814.448160] iwl4965 :03:00.0: idx 0 not used in uCode key table.
  [ 5814.948182] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.948201] wls3: failed to remove key (0, **:**:**:**:**:**) from 
hardware (-110)
  [ 5818.964158] iwl4965 :03:00.0: START_ALIVE timeout after 4000ms.
  
+ WORKAROUND: Turn off WiFi power management:
+ sudo iw dev X set power_save off
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  mki2093 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  mki2093 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Sep 27 13:29:36 2016
  HibernationDevice: RESUME=/dev/mapper/vgubuntu-swap
  InstallationDate: Installed on 2016-06-05 (113 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: LENOVO 76693JG
  PccardctlIdent:
-  Socket 0:
-no product info available
+  Socket 0:
+    no product info available
  PccardctlStatus:
-  Socket 0:
-no card
+  Socket 0:
+    no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/vgubuntu-system ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-38-generic N/A
-  linux-backports-modules-4.4.0-38-generic  N/A
-  linux-firmware1.157.3
+  linux-restricted-modules-4.4.0-38-generic N/A
+  linux-backports-modules-4.4.0-38-generic  N/A
+  linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC2WW (2.22 )
  dmi.board.name: 76693JG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn76693JG:pvrThinkPadX61s:rvnLENOVO:rn76693JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 76693JG
  dmi.product.version: ThinkPad X61s
  dmi.sys.vendor: LENOVO

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

Title:
  iwl4965 crashes randomly

Status in linux package in Ubuntu:
  Expired

Bug description:
  On my Lenovo X61s, WLAN randomly stops working, typically after a few hours 
of running time. I don't know any remedy but to reboot.
  This behavior started maybe 2 or 3 months ago. My maching is usually kept up 
to date, so the problem might be caused by some kernel update at that time.

  The relevant part in dmesg (attached) starts with
  [ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out 
after 500ms.
  [ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110
  [ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.424162] wls3: HW problem - can not stop rx 

[Kernel-packages] [Bug 1666214] Re: linux: 4.10.0-9.11 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.10.0-9.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-phase-changed:Monday, 20. February 2017 23:31 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.10.0-9.11 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: Uploaded
- kernel-phase-changed:Monday, 20. February 2017 23:31 UTC
- kernel-phase:Uploaded

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

Title:
  linux: 4.10.0-9.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
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.10.0-9.11 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1666214/+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 1643719] Re: ACPI AE_NOT_FOUND errors aggressively being spawned, filling up log files.

[Christopher M. Penalver]

aaronfranke, to advise, this isn't Fix Committed as defined in:
https://wiki.ubuntu.com/Bugs/Status

Despite this, have you personally tested the patch on your hardware?

If not, one may follow
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
to test it.

Once the patch has been tested, please advise to the results and mark
this Status Confirmed.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1643719

Title:
  ACPI AE_NOT_FOUND errors aggressively being spawned, filling up log
  files.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  OS: Xubuntu 16.04.1 LTS - Ubuntu 4.4.0-47.68-generic 4.4.24

  Motherboard: ASRock Z170M Pro4S

  GPU: Asus Nvidia GTX 770 with 367.57 drivers

  Storage: Corsair 256 GB SSD, Toshiba 3 TB HDD, Hitachi 2 TB HDD

  
  Here's a small sample of the errors: http://pastebin.com/b2Jv8z37

  While these errors definitely have a purpose, these error messages are
  created far too quickly, and this causes severe problems on my system
  at least, the logs become bloated with these messages, completely
  filling my root partition, preventing me from using my system.  I
  believe that anyone else who is able to trigger these messages at such
  a high rate will have the same problem.

  Based on the amount of messages and the time given for each, it
  appears that this error message appears approximately 1000 times per
  second (on my system), creating 3000 lines per second or ~40 bytes
  per second (on my system). This fills up about 1.4 GB per hour (on my
  system) which fills up my root partition in less than a day. Once my
  root partition is filled, my system becomes unusable.

  My preferred solution to this issue is to limit the rate at which
  these messages appear. A limit of one error message per second seems
  like a good idea.

  Also, I tried reporting this to the Linux kernel devs, I'm not exactly sure 
if either of these places is the right place but hopefully somebody will be 
able to fix this issue. Here is the link to the other bug report 
https://bugzilla.kernel.org/show_bug.cgi?id=188331
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   aaronfranke   2674 F...m pulseaudio
   /dev/snd/controlC0:  aaronfranke   2674 F pulseaudio
   /dev/snd/controlC2:  aaronfranke   2674 F pulseaudio
   /dev/snd/controlC1:  aaronfranke   2674 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1fcb1225-87da-4148-9227-bedf5fe47d08
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04b4:1007 Cypress Semiconductor Corp. 
   Bus 001 Device 003: ID 045e:076c Microsoft Corp. Comfort Mouse 4500
   Bus 001 Device 002: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=b5b971ee-cfa4-435f-9699-2543a4f50bd3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Z170M Pro4S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd08/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1624339] Re: Elantech v4 trackpad no longer working after resuming for hibernate

[Christopher M. Penalver]

Jean-Yves Avenard, to advise, if a bug is marked Expired, it's not considered 
closed as per:
https://wiki.ubuntu.com/Bugs/Status

Despite this, could you please test the latest mainline kernel (4.10)
and advise to the results?

If reproducible, the next step is to gather hibernate debug logs.

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

Title:
  Elantech v4 trackpad no longer working after resuming for hibernate

Status in linux package in Ubuntu:
  Expired

Bug description:
  This is a Gigabyte AERO 14 laptop (http://www.gigabyte.com.au/products
  /product-page.aspx?pid=5902#kf)

  When laptop goes into hibernate mode, the trackpad will no longer work. 
Rebooting will not make the trackpad work again.
  The only work around I've found so far is to reboot into windows and then 
reboot into ubuntu.

  It is similar to bug 1490130; however here it's with hibernating and can't be 
recovered with rebooting (additionally, the kernel patch provided there doesn't 
work)
  Suspend works just fine.

  *** before hibernate

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

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

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

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

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

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

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

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name="ETPS/2 Elantech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse1 event8
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  I: Bus=0003 Vendor=1044 Product=7a06 Version=0110
  N: Name="E-Signal Keyboard"
  P: Phys=usb-:00:14.0-5/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1044:7A06.0002/input/input10
  U: Uniq=
  H: Handlers=sysrq kbd leds event9
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=1044 Product=7a06 Version=0110
  N: Name="E-Signal Keyboard"
  P: Phys=usb-:00:14.0-5/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.1/0003:1044:7A06.0003/input/input11
  U: Uniq=
  H: Handlers=kbd mouse2 event10 js0
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 48317aff32d bf56 1f0001 130f938b17c000 
677bfad9415fed 9ed6804400 1002
  B: REL=1c0
  B: ABS=10003
  B: MSC=10

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

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event12
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
  U: Uniq=
  H: Handlers=event13
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=

[Kernel-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[Czikus]

Same problem with Ubuntu 16.04 and Jaybird X3. The workaround in a2dp.py
works, but it's an annoying problem. I tried bluez 5.43, and the problem
still exists. Are there any ideas on how to  fix this problem
permanently?

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1665783] Re: Include Broadcom GPL modules in Xenial Kernel

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-February/082635.html

** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
Milestone: ubuntu-16.04.2 => None

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
   Status: New

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

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

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

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

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

Title:
  Include Broadcom GPL modules in Xenial Kernel

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

Bug description:
  Please include the OpenNSL GPL modules with the Kernel.
  These modules are located at https://github.com/Broadcom-Switch/OpenNSL.
  The latest SDK version is 6.5.6. 
  We would like to have the kernel modules included with the LTS Xenial kernel 
so that we can provide these modules to network vendors so that they don't have 
to compile them and taint our working kernel. 
  We would want to manage these modules so that we can perform updates and 
security fixes to the kernel and even use kernel-livepatch with these devices. 
  Currently, Network vendors compile and build these against older kernel's and 
then they cannot be patched or updated leaving network devices vulnerable to 
security threats that normally would be patched by our systems. By having us 
manage these modules, we can maintain security and compatibility with the 
kernel and the network vendors can use our native kernel with their software.

  The three modules that get built are linux-kernel-bde.ko, linux-user-
  bde,ko and linux-bcm-knet.ko.

  If you have any other questions, please don't hesitate to contact me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665783/+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 1665783] [NEW] Include Broadcom GPL modules in Xenial Kernel

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Please include the OpenNSL GPL modules with the Kernel.
These modules are located at https://github.com/Broadcom-Switch/OpenNSL.
The latest SDK version is 6.5.6. 
We would like to have the kernel modules included with the LTS Xenial kernel so 
that we can provide these modules to network vendors so that they don't have to 
compile them and taint our working kernel. 
We would want to manage these modules so that we can perform updates and 
security fixes to the kernel and even use kernel-livepatch with these devices. 
Currently, Network vendors compile and build these against older kernel's and 
then they cannot be patched or updated leaving network devices vulnerable to 
security threats that normally would be patched by our systems. By having us 
manage these modules, we can maintain security and compatibility with the 
kernel and the network vendors can use our native kernel with their software.

The three modules that get built are linux-kernel-bde.ko, linux-user-
bde,ko and linux-bcm-knet.ko.

If you have any other questions, please don't hesitate to contact me.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: New


** Tags: kernel-bug
-- 
Include Broadcom GPL modules in Xenial Kernel
https://bugs.launchpad.net/bugs/1665783
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1585741] Re: [ubuntu 16.10] Enable OPTPROBES for powerpc

[Tim Gardner]

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

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

Title:
  [ubuntu 16.10] Enable OPTPROBES for powerpc

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This is a feature request for Ubuntu 16.10:

  Optimized kprobes support for powerpc :
  This feauture aims to enhance the performance of kprobes. Currently, whenever 
a probe is placed in the kernel using the kprobes infrastructure, it places a 
trap instruction at that place. This feature will replace the trap with a 
branch thereby reducing the probe overhead drastically.

  Patches to enable this are being sent :
  https://lkml.org/lkml/2016/5/17/513

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585741/+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 1666214] Re: linux: 4.10.0-9.11 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Description changed:

  This bug is for tracking the 4.10.0-9.11 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:Monday, 20. February 2017 13:30 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-phase-changed:Monday, 20. February 2017 22:01 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.10.0-9.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Packaging
- kernel-phase-changed:Monday, 20. February 2017 22:01 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.10.0-9.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
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.10.0-9.11 upload package. This bug will
  contain status and testing results related to that upload.

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1666214/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Mike Williams]

I'm pretty sure this bug was introduced in 4.4.0-58, even though I
reported it against 4.4.0-59. Still, +1 for a raising a separate bug
against 4.8.

Thanks to Cascardo for fixing this one.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/ubuntu/+source/linux/+bug/1655842/+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 1666324] [NEW] Xenial update to v4.4.50 stable release

[Tim Gardner]

Public bug reported:

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.4.50 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.4.50 stable release shall be
applied:

can: Fix kernel panic at security_sock_rcv_skb
ipv6: fix ip6_tnl_parse_tlv_enc_lim()
ipv6: pointer math error in ip6_tnl_parse_tlv_enc_lim()
tcp: fix 0 divide in __tcp_select_window()
net: use a work queue to defer net_disable_timestamp() work
ipv4: keep skb->dst around in presence of IP options
netlabel: out of bound access in cipso_v4_validate()
ip6_gre: fix ip6gre_err() invalid reads
ipv6: tcp: add a missing tcp_v6_restore_cb()
tcp: avoid infinite loop in tcp_splice_read()
tun: read vnet_hdr_sz once
macvtap: read vnet_hdr_size once
mlx4: Invoke softirqs after napi_reschedule
sctp: avoid BUG_ON on sctp_wait_for_sndbuf
sit: fix a double free on error path
net: introduce device min_header_len
packet: round up linear to header len
ping: fix a null pointer dereference
l2tp: do not use udp_ioctl()
Linux 4.4.50

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Description changed:

+ SRU Justification
  
- 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.4.50 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- 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.4.50 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.4.50 stable release shall be
+ applied:
  
-The following patches from the v4.4.50 stable release shall be
- applied:
+ can: Fix kernel panic at security_sock_rcv_skb
+ ipv6: fix ip6_tnl_parse_tlv_enc_lim()
+ ipv6: pointer math error in ip6_tnl_parse_tlv_enc_lim()
+ tcp: fix 0 divide in __tcp_select_window()
+ net: use a work queue to defer net_disable_timestamp() work
+ ipv4: keep skb->dst around in presence of IP options
+ netlabel: out of bound access in cipso_v4_validate()
+ ip6_gre: fix ip6gre_err() invalid reads
+ ipv6: tcp: add a missing tcp_v6_restore_cb()
+ tcp: avoid infinite loop in tcp_splice_read()
+ tun: read vnet_hdr_sz once
+ macvtap: read vnet_hdr_size once
+ mlx4: Invoke softirqs after napi_reschedule
+ sctp: avoid BUG_ON on sctp_wait_for_sndbuf
+ sit: fix a double free on error path
+ net: introduce device min_header_len
+ packet: round up linear to header len
+ ping: fix a null pointer dereference
+ l2tp: do not use udp_ioctl()
+ Linux 4.4.50

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

Title:
  Xenial update to v4.4.50 stable release

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

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.4.50 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.4.50 stable release shall be
  applied:

  can: Fix kernel panic at security_sock_rcv_skb
  ipv6: fix 

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

Title:
  Windows become unclickable (transparent for mouse clicks) after resume
  from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Windows become unclickable (transparent for mouse clicks) after resume from 
the sleep mode. Both system and JVM windows can't capture mouse clicks 
including clicks on the title bar after resuming from the sleep mode. Unity 
panel works fine, new applications can be started and they do not have this 
issue, i.e. new windows are fully functional.
  This bug appears seldom and is hardly reproducible (like #1651520).

  This bug is a minor security vulnerability because clicking on the
  foreground non-clickable window, a user performs actual click on the
  background window (or desktop shortcuts) and anything can be
  initiated/started that the user has right, but was not intended to do.

  
  Notes:
  This bug might relate to
  #1651520 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520) 
except in 4.4.0-62, except 1) the windows' content now is not damaged and 
visually indistinguishable from the fully functional windows and 2) windows in 
#1651520 had destroyed content, but were clickable.
  Neither this bug nor #1651520 appear in the 4.9.3 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lav3136 F pulseaudio
   /dev/snd/controlC0:  lav3136 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 20 21:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-25 (849 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20A8S28400
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-09-11 (162 days ago)
  dmi.bios.date: 06/06/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET39WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S28400
  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:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A8S28400
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666316/+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 1664217] Re: linux: 4.10.0-8.10 -proposed tracker

[Tim Gardner]

** Tags removed: block-proposed

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

Title:
  linux: 4.10.0-8.10 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.10.0-8.10 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1664217/+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 1666214] Re: linux: 4.10.0-9.11 -proposed tracker

[Tim Gardner]

** Tags removed: block-proposed

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

Title:
  linux: 4.10.0-9.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
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.10.0-9.11 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:Monday, 20. February 2017 13:30 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/1666214/+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 1666070] Re: booting problem 16.10

[Schoeters Jason]

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/linux/+question/467658

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

Title:
  booting problem 16.10

Status in linux package in Ubuntu:
  Invalid

Bug description:
  About 90% or more of the times I boot ubuntu 16.10, I encounter a bug or 
error or freeze.
  These errors range from "setting intel event mask failed (-16)" to "end 
kernel panic - not syncing: attempted to kill init".

  I recently installed ubuntu and all I want is it to work, I don't care
  if I need to reinstall some other ubuntu version and delete this one
  with all I already installed on it, as long as it FUNCTIONS.

  So please if anyone knows any ubuntu version that is sure to be bug-
  free, please share. Or if anyone is sure to be able to help me get rid
  of the bugs on this ubuntu version, please do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: 
boot/vmlinuz-4.8.0-22-generic]
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  schoeters   2154 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 19 22:49:02 2017
  InstallationDate: Installed on 2017-02-10 (9 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:57f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=44ed2b47-d533-4807-831d-0018866b74a5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UAK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UAK.303:bd10/03/2016:svnASUSTeKCOMPUTERINC.:pnUX360UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.name: UX360UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666070/+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 1666316] Re: Windows become unclickable (transparent for mouse clicks) after resume from sleep

[Artem V L]

This bug appeared for months on different (previous) kernels, just I
have reported it for the first time.

** Information type changed from Private Security to Public Security

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

Title:
  Windows become unclickable (transparent for mouse clicks) after resume
  from sleep

Status in linux package in Ubuntu:
  New

Bug description:
  Windows become unclickable (transparent for mouse clicks) after resume from 
the sleep mode. Both system and JVM windows can't capture mouse clicks 
including clicks on the title bar after resuming from the sleep mode. Unity 
panel works fine, new applications can be started and they do not have this 
issue, i.e. new windows are fully functional.
  This bug appears seldom and is hardly reproducible (like #1651520).

  This bug is a minor security vulnerability because clicking on the
  foreground non-clickable window, a user performs actual click on the
  background window (or desktop shortcuts) and anything can be
  initiated/started that the user has right, but was not intended to do.

  
  Notes:
  This bug might relate to
  #1651520 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520) 
except in 4.4.0-62, except 1) the windows' content now is not damaged and 
visually indistinguishable from the fully functional windows and 2) windows in 
#1651520 had destroyed content, but were clickable.
  Neither this bug nor #1651520 appear in the 4.9.3 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lav3136 F pulseaudio
   /dev/snd/controlC0:  lav3136 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 20 21:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-25 (849 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20A8S28400
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-09-11 (162 days ago)
  dmi.bios.date: 06/06/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET39WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S28400
  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:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A8S28400
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666316/+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 1256822] Re: Misspelling in description of linux-goldfish-tools-3.4.0-4

[Pascal De Vuyst]

** Tags removed: needs-ddtp-pot-update

** Tags added: xenial yakkety zesty

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

Title:
  Misspelling in description of linux-goldfish-tools-3.4.0-4

Status in Package Descriptions for Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-goldfish package in Ubuntu:
  Fix Released

Bug description:
  Package: linux-goldfish-tools-3.4.0-4
  Version: 3.4.0-4.27

  The long package description contains a small typo:
  You probabally want to install linux-tools-3.4.0-4-.
  Should be:
  You probably want to install linux-tools-3.4.0-4-.

  The same misspelling can be found in 2 strings:
  
https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-universe/fr/80685/+translate
  
https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-universe/fr/80983/+translate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ddtp-ubuntu/+bug/1256822/+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 1666290] 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/1666290

Title:
  package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to
  install/upgrade:
  »/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko
  .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Automated bug report. No further information from my side

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-38-generic 4.8.0-38.41
  ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17
  Uname: Linux 4.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   linux-image-extra-4.8.0-38-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  roman  5925 F pulseaudio
   /dev/snd/controlC2:  roman  5925 F pulseaudio
   /dev/snd/controlC1:  roman  5925 F pulseaudio
   /dev/snd/controlC0:  roman  5925 F pulseaudio
  Date: Mon Feb 20 18:53:22 2017
  DpkgTerminalLog:
   Vorbereitung zum Entpacken von 
.../linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb ...
   Entpacken von linux-image-extra-4.8.0-38-generic (4.8.0-38.41) ...
   dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb
 (--unpack):

»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
  ErrorMessage: 
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
  HibernationDevice: RESUME=UUID=65743a1a-1279-417e-ab26-cd17b1baa629
  InstallationDate: Installed on 2017-01-29 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-38-generic 
root=UUID=3d889fca-fb58-4d48-bfb6-61c9d6408e49 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to 
install/upgrade: 
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666290/+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 1666290] [NEW] package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to install/upgrade: »/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new«

[Roman]

Public bug reported:

Automated bug report. No further information from my side

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-extra-4.8.0-38-generic 4.8.0-38.41
ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17
Uname: Linux 4.8.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering:
 linux-image-extra-4.8.0-38-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  roman  5925 F pulseaudio
 /dev/snd/controlC2:  roman  5925 F pulseaudio
 /dev/snd/controlC1:  roman  5925 F pulseaudio
 /dev/snd/controlC0:  roman  5925 F pulseaudio
Date: Mon Feb 20 18:53:22 2017
DpkgTerminalLog:
 Vorbereitung zum Entpacken von 
.../linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb ...
 Entpacken von linux-image-extra-4.8.0-38-generic (4.8.0-38.41) ...
 dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb
 (--unpack):
  
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
ErrorMessage: 
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
HibernationDevice: RESUME=UUID=65743a1a-1279-417e-ab26-cd17b1baa629
InstallationDate: Installed on 2017-01-29 (21 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-38-generic 
root=UUID=3d889fca-fb58-4d48-bfb6-61c9d6408e49 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to 
install/upgrade: 
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package yakkety

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

Title:
  package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to
  install/upgrade:
  »/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko
  .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig

Status in linux package in Ubuntu:
  New

Bug description:
  Automated bug report. No further information from my side

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-38-generic 4.8.0-38.41
  ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17
  Uname: Linux 4.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   linux-image-extra-4.8.0-38-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  roman  5925 F pulseaudio
   /dev/snd/controlC2:  roman  5925 F pulseaudio
   /dev/snd/controlC1:  roman  5925 F pulseaudio
   /dev/snd/controlC0:  roman  5925 F pulseaudio
  Date: Mon Feb 20 18:53:22 2017
  DpkgTerminalLog:
   Vorbereitung zum Entpacken von 
.../linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb ...
   Entpacken von linux-image-extra-4.8.0-38-generic (4.8.0-38.41) ...
   dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb
 (--unpack):

»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht 

[Kernel-packages] [Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Iain Buclaw]

Attaching current slabtop

---
# cat /proc/meminfo 
MemTotal:   32856000 kB
MemFree:  381632 kB
MemAvailable:   30990804 kB
Buffers:28709688 kB
Cached:   221664 kB
SwapCached:  184 kB
Active: 24854232 kB
Inactive:5393552 kB
Active(anon): 783780 kB
Inactive(anon):   538772 kB
Active(file):   24070452 kB
Inactive(file):  4854780 kB
Unevictable:  32 kB
Mlocked:  32 kB
SwapTotal:  33553332 kB
SwapFree:   33552460 kB
Dirty:  2472 kB
Writeback: 0 kB
AnonPages:   1316236 kB
Mapped:42768 kB
Shmem:  6164 kB
Slab:2120976 kB
SReclaimable:2086268 kB
SUnreclaim:34708 kB
KernelStack:4480 kB
PageTables: 9944 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:49981332 kB
Committed_AS:1326540 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   0 kB
VmallocChunk:  0 kB
HardwareCorrupted: 0 kB
AnonHugePages:868352 kB
CmaTotal:  0 kB
CmaFree:   0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
DirectMap4k:  188008 kB
DirectMap2M:33275904 kB


** Attachment added: "slabtop.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822862/+files/slabtop.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/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  

[Kernel-packages] [Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Iain Buclaw]

SLAB is still dropping.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+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 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Iain Buclaw]

I think this is currently in the middle of happening right now on one of
the servers running 4.4.0-63.

SReclaimable is down from 15GB to 5GB, and Buffers is has been slowly
rising over the last hour from 12GB to approaching 25GB.

---
# cat /proc/meminfo 
MemTotal:   32856000 kB
MemFree: 1331808 kB
MemAvailable:   30994136 kB
Buffers:24951992 kB
Cached:   388368 kB
SwapCached:  188 kB
Active: 22271936 kB
Inactive:4383080 kB
Active(anon): 786576 kB
Inactive(anon):   534244 kB
Active(file):   21485360 kB
Inactive(file):  3848836 kB
Unevictable:  32 kB
Mlocked:  32 kB
SwapTotal:  33553332 kB
SwapFree:   33552460 kB
Dirty:  2048 kB
Writeback: 0 kB
AnonPages:   1314500 kB
Mapped:42820 kB
Shmem:  6164 kB
Slab:4765816 kB
SReclaimable:4730460 kB
SUnreclaim:35356 kB
KernelStack:4512 kB
PageTables:10164 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:49981332 kB
Committed_AS:1352800 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   0 kB
VmallocChunk:  0 kB
HardwareCorrupted: 0 kB
AnonHugePages:856064 kB
CmaTotal:  0 kB
CmaFree:   0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
DirectMap4k:  188008 kB
DirectMap2M:33275904 kB
---

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  

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

[Mike Rushton]

@paelzer the machine was sent out for repair/replacement. We expect it
to return later this week. I will test the package from the above PPA as
soon as it is back.

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

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

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

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

  kvm_init_vcpu failed: Invalid argument

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

  
  The full output from the test is as follows:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to 

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

Title:
  Screen flickering

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 12 11:29:15 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C600JAGE
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600JAGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600JAGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sun Feb 12 11:28:27 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663989/+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 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx

[K1773R]

Now wait 1 year till they MAYBE will fix it...

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

Title:
  Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with
  identifier from /mnt/disk/by-id/

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  zfs-dkms 0.6.5.6-0ubuntu15

  I cant mount/install my zpool. so i tried reinstalling zfslinux-utils,
  which gives me three error messages like this: "zfs-mount.service is a
  disabled" or a static unit, not starting it."...

  If something doesn't work I try googling error messages. most answers
  not totally like my problem but related to dkms, so I tried loading
  zfs-dkms and reinstalling zfslinux-utils.

  I created the zpool with id from /mnt/disk/by-id/ - which is zfs good-
  practice. This may be causing problems with the mount. I dont know...

  Cheers.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
  Uname: Linux 4.4.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-58-generic
  Date: Sat Jan  7 15:58:15 2017
  DuplicateSignature: 
dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12:
 error: too few arguments to function ‘posix_acl_valid’
  InstallationDate: Installed on 2016-12-26 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225)
  PackageVersion: 0.6.5.6-0ubuntu15
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1654708/+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 1663989] Re: Screen flickering

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  Screen flickering

Status in linux package in Ubuntu:
  New

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 12 11:29:15 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C600JAGE
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600JAGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600JAGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sun Feb 12 11:28:27 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663989/+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 1663989] Re: Screen flickering

[Dave Long]

Confirmed that the bug is fixed in the 4.10 kernel series.

Further confirmed that this is down to the i915.enable_psr parameter:

Linux 4.8 with no command line => flickering (enable_psr defaults to on)
Linux 4.8 with i915.enable_psr=0 => no flickering
Linux 4.10 with no command line => no flickering (enable_psr defaults to off)
Linux 4.10 with i915.enable_psr=1 => flickering


** Package changed: nvidia-graphics-drivers (Ubuntu) => linux (Ubuntu)

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

Title:
  Screen flickering

Status in linux package in Ubuntu:
  New

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 12 11:29:15 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C600JAGE
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600JAGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600JAGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sun Feb 12 11:28:27 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1

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

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

Re: [Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[warren]

Does Bug 1572801 have anything to do with the Upstart to systemd
transition?


On 02/17/2017 03:37 AM, nevergone wrote:
> Somebody?
>

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+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 1663989] [NEW] Screen flickering

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
flickering irregularly. It only happens with kernel 4.8.x. No flickering
problems when manually switching back to kernel versions 4.4.x at boot.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Feb 12 11:29:15 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
   Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:07dc Intel Corp. 
 Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20C600JAGE
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET98WW (2.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C600JAGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C600JAGE
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sun Feb 12 11:28:27 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1

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


** Tags: amd64 apport-bug compiz-0.9 kernel-da-key kernel-fixed-upstream ubuntu 
yakkety
-- 
Screen flickering
https://bugs.launchpad.net/bugs/1663989
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1666257] Re: Cannot find wireless networks in xenial

[musanage]

Could not find a right source package. Chose the closest one 'wireless-
crda'. Please assign it to the right component.

** Package changed: ubuntu => wireless-crda (Ubuntu)

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

Title:
  Cannot find wireless networks in xenial

Status in wireless-crda package in Ubuntu:
  New

Bug description:
  I have Ubuntu Xenial(16.4.0.2) installed and unable to find wireless
  networks to connect to. Wireless switch is on and wireless networking
  is enabled and the device is in a up state

  wlp2s0Link encap:Ethernet  HWaddr 94:53:30:4d:84:27
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  More information on my setup:

  $ lspci -nn | grep 0280
  02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]

  $ lsusb
  Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 003: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
  Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 002: ID 0bda:b006 Realtek Semiconductor Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
  1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  
   $ dmesg | grep -e wlan -e b43
  [   15.006188] rtl8723be :02:00.0 wlp2s0: renamed from wlan0

  $ sudo modprobe b43
  $
  This is a dual boot system and when I boot with Windows 10, I am able to find 
wireless networks and connect successfully with the same hardware.

  Tried workaround mentioned in How do I get a Realtek RTL8723BE
  wireless card to work? but did not help.

  Ubuntu is able to find wireless connection at home without any
  problem. When I go to a library, that's when Ubuntu fails to pick up
  any wireless network.

  Rebooted Ubuntu and captured syslog messages when I was in a library. Syslog 
messages available at 
  http://pastebin.com/W4BuC74W

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-crda/+bug/1666257/+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 1666257] [NEW] Cannot find wireless networks in xenial

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have Ubuntu Xenial(16.4.0.2) installed and unable to find wireless
networks to connect to. Wireless switch is on and wireless networking is
enabled and the device is in a up state

wlp2s0Link encap:Ethernet  HWaddr 94:53:30:4d:84:27
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
More information on my setup:

$ lspci -nn | grep 0280
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]

$ lsusb
Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:b006 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no


 $ dmesg | grep -e wlan -e b43
[   15.006188] rtl8723be :02:00.0 wlp2s0: renamed from wlan0

$ sudo modprobe b43
$
This is a dual boot system and when I boot with Windows 10, I am able to find 
wireless networks and connect successfully with the same hardware.

Tried workaround mentioned in How do I get a Realtek RTL8723BE wireless
card to work? but did not help.

Ubuntu is able to find wireless connection at home without any problem.
When I go to a library, that's when Ubuntu fails to pick up any wireless
network.

Rebooted Ubuntu and captured syslog messages when I was in a library. Syslog 
messages available at 
http://pastebin.com/W4BuC74W

** Affects: wireless-crda (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
Cannot find wireless networks in xenial
https://bugs.launchpad.net/bugs/1666257
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to wireless-crda in Ubuntu.

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

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

[ChristianEhrhardt]

Preliminary builds as preparation for an SRU currently building at

Xenial https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2502

My testing will start on those, but if you can please give it as much
testing as you can as well.

@leftyfb - how about your machine, is it running again to be able to
test that?

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

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

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

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

  kvm_init_vcpu failed: Invalid argument

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

  
  The full output from the test is as follows:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 

[Kernel-packages] [Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Iain Buclaw]

Attaching the call trace for 4.8.0-34, this is from Feb 19th.

** Attachment added: "linux-48034.oom.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822834/+files/linux-48034.oom.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/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+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 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Iain Buclaw]

Attaching the call trace for 4.4.0-59, this is from Jan 16th.

** Attachment added: "linux-44059.oom.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822833/+files/linux-44059.oom.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/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+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 1666262] 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 1666262

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

Title:
  Wireless does not connect after wakeup LenovoG50

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am not sure if the problem is due to the kernel update. I use Linux
  Mint 18.1 and I have Linux kernel 4.8.0-36. I noticed that after
  updating to the last kernel whenever my system wakes up from sleep, it
  cannot connect to wireless network. it does not even show the wireless
  networks available but a random network that might have been available
  in the past (as in displayed in list of available networks around, but
  never connected to). I have to reboot to get the wireless.

  I tried running "ubuntu-bug linux" command and got-
  "*** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.8.0-36-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Press any key to continue...  
  No pending crash reports. Try --help for more information."

  Also ran "cat /proc/version_signature > version.log" which did
  nothing.

  Running "sudo lspci -vnvn > lspci-vnvn.log" did not bring up any log to copy 
paste. It gave-
  " laptop@laptop-Lenovo-G50-80 ~ $ sudo sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error "

  I have been using Linux on and off for over 10 years now but am still
  not proficient enough mostly because there are so very few problems
  unlike windows where I had to learn everything from reinstalling
  drivers, Windows OS, programs, checking for malware, firewalls,
  privacy controls.. the list is almost endless.

  I am not sure if I have provided all the information needed but if any
  other information is needed, I can provide it if shown how to get it.

  
  Thanks a ton.
  Cheers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666262/+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 1666260] 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/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+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 1666262] [NEW] Wireless does not connect after wakeup LenovoG50

[Amit182]

Public bug reported:

I am not sure if the problem is due to the kernel update. I use Linux
Mint 18.1 and I have Linux kernel 4.8.0-36. I noticed that after
updating to the last kernel whenever my system wakes up from sleep, it
cannot connect to wireless network. it does not even show the wireless
networks available but a random network that might have been available
in the past (as in displayed in list of available networks around, but
never connected to). I have to reboot to get the wireless.

I tried running "ubuntu-bug linux" command and got-
"*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..

*** Problem in linux-image-4.8.0-36-generic

The problem cannot be reported:

This is not an official Linux package. Please remove any third party
package and try again.

Press any key to continue...  
No pending crash reports. Try --help for more information."

Also ran "cat /proc/version_signature > version.log" which did nothing.

Running "sudo lspci -vnvn > lspci-vnvn.log" did not bring up any log to copy 
paste. It gave-
" laptop@laptop-Lenovo-G50-80 ~ $ sudo sudo lspci -vnvn > lspci-vnvn.log
pcilib: sysfs_read_vpd: read failed: Input/output error "

I have been using Linux on and off for over 10 years now but am still
not proficient enough mostly because there are so very few problems
unlike windows where I had to learn everything from reinstalling
drivers, Windows OS, programs, checking for malware, firewalls, privacy
controls.. the list is almost endless.

I am not sure if I have provided all the information needed but if any
other information is needed, I can provide it if shown how to get it.


Thanks a ton.
Cheers.

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

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

Title:
  Wireless does not connect after wakeup LenovoG50

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am not sure if the problem is due to the kernel update. I use Linux
  Mint 18.1 and I have Linux kernel 4.8.0-36. I noticed that after
  updating to the last kernel whenever my system wakes up from sleep, it
  cannot connect to wireless network. it does not even show the wireless
  networks available but a random network that might have been available
  in the past (as in displayed in list of available networks around, but
  never connected to). I have to reboot to get the wireless.

  I tried running "ubuntu-bug linux" command and got-
  "*** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.8.0-36-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Press any key to continue...  
  No pending crash reports. Try --help for more information."

  Also ran "cat /proc/version_signature > version.log" which did
  nothing.

  Running "sudo lspci -vnvn > lspci-vnvn.log" did not bring up any log to copy 
paste. It gave-
  " laptop@laptop-Lenovo-G50-80 ~ $ sudo sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error "

  I have been using Linux on and off for over 10 years now but am still
  not proficient enough mostly because there are so very few problems
  unlike windows where I had to learn everything from reinstalling
  drivers, Windows OS, programs, checking for malware, firewalls,
  privacy controls.. the list is almost endless.

  I am not sure if I have provided all the information needed but if any
  other information is needed, I can provide it if shown how to get it.

  
  Thanks a ton.
  Cheers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666262/+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 1666260] [NEW] "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Iain Buclaw]

Public bug reported:

Same as #1655842 - Started seeing oom-killer on multiple servers
upgraded to 4.4.0-59.

Unlike #1655842, also seeing the same oom-killer on multiple servers
updated to 4.8.0-34.

First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
4.4.0-63.  I am seeing no change in the memory usage, so I can only
assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
and 4.8.0-34.  Either because #1655842 is not fixed, or it is only fixed
for certain kinds of workloads.

However, on closer inspection, there is definitely a notable difference
between 4.4.0-59 and 4.4.0-63/4.8.0-34.

The symptoms I'm seeing are:

Upgrading 4.4.0-57 -> 4.4.0-59:
- /proc/meminfo:Buffers: Up from 9GB to 15GB
- /proc/meminfo:Cached: Up from 5GB to 10GB
- /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
- /proc/meminfo:SUnreclaim: No notable change

Upgrading 4.4.0-57 -> 4.8.0-34:
- /proc/meminfo:Buffers: Up from 9GB to 14GB
- /proc/meminfo:Cached: Down from 5GB to 2GB
- /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
- /proc/meminfo:SUnreclaim: No notable change

Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
- /proc/meminfo:Buffers: No notable change
- /proc/meminfo:Cached: No notable change
- /proc/meminfo:SReclaimable: No notable change
- /proc/meminfo:SUnreclaim: No notable change

Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
not causing OOMs.

Downgrading to 4.4.0-57 also works.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-63-generic 4.4.0-63.84
ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
Uname: Linux 4.4.0-63-generic x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
Date: Mon Feb 20 16:15:56 2017
InstallationDate: Installed on 2012-06-04 (1721 days ago)
InstallationMedia:
 
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: System manufacturer System Product Name
PciMultimedia:
 
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-63-generic N/A
 linux-backports-modules-4.4.0-63-generic  N/A
 linux-firmware1.157.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
dmi.bios.date: 10/17/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug xenial

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  New

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No 

[Kernel-packages] [Bug 1665911] Re: Linux 4.8 hangs system when playing video

[Rehan Khamaruddin]

Further update: It appears that the lockup happens only when streaming
video and not when playing local files. There is a possibility that
could be network related. Definitely does not happen with the 4.4x
kernel.

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

Title:
  Linux 4.8 hangs system when playing video

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently updated to the 16.04.2 LTS release and installed the new
  HWE stack which installed kernel 4.8. Ever since, my machine
  completely freezes when playing video (eg. Youtube). I have to power
  off or hard reset using physical buttons to recover. Nothing seems to
  be written to the logs.

  Please let me know how to get additional information to help diagnose
  the issue.

  Thanks.

  Release:   Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11

  System:Host: rsk4 Kernel: 4.8.0-36-generic x86_64 (64 bit gcc: 5.4.0)
 Desktop: Unity 7.4.0 (Gtk 2.24.30) Distro: Ubuntu 16.04 xenial
  Machine:   Mobo: ASUSTeK model: M5A99FX PRO R2.0 v: Rev 1.xx
 Bios: American Megatrends v: 2501 date: 04/07/2014
  CPU:   Quad core AMD FX-8350 Eight-Core (-HT-MCP-) cache: 8192 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
32107
 clock speeds: max: 4000 MHz 1: 1400 MHz 2: 1400 MHz 3: 1400 MHz
 4: 1400 MHz 5: 1400 MHz 6: 1400 MHz 7: 1400 MHz 8: 1400 MHz
  Graphics:  Card: NVIDIA GK106 [GeForce GTX 650 Ti] bus-ID: 01:00.0
 Display Server: X.Org 1.18.4 driver: nvidia
 Resolution: 1920x1080@60.00hz, 1920x1080@59.93hz
 GLX Renderer: GeForce GTX 650 Ti/PCIe/SSE2
 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes
  Audio: Card-1 NVIDIA GK106 HDMI Audio Controller
 driver: snd_hda_intel bus-ID: 01:00.1
 Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
 driver: snd_hda_intel bus-ID: 00:14.2
 Sound: Advanced Linux Sound Architecture v: k4.8.0-36-generic
  Network:   Card-1: Intel 82541PI Gigabit Ethernet Controller
 driver: e1000 v: 7.3.21-k8-NAPI port: d000 bus-ID: 05:05.0
 IF: eth1 state: up speed: 1000 Mbps duplex: full mac: 
 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
 driver: r8169 v: 2.3LK-NAPI port: b000 bus-ID: 09:00.0
 IF: eth0 state: down mac: 
  Drives:HDD Total Size: 740.2GB (42.4% used)
 ID-1: /dev/sda model: SPCC_Solid_State size: 240.1GB temp: 30C
 ID-2: /dev/sdb model: ST500DM002 size: 500.1GB temp: 27C
  Partition: ID-1: / size: 34G used: 13G (40%) fs: ext4 dev: /dev/sda1
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 28.0C mobo: 19.4C gpu: 0.0:35C
 Fan Speeds (in rpm): cpu: 0 fan-1: 1308 fan-2: 1028 fan-3: 0
  Info:  Processes: 284 Uptime: 6 min Memory: 1564.9/32075.1MB
 Init: systemd runlevel: 5 Gcc sys: 5.4.0
 Client: Shell (bash 4.3.461) inxi: 2.2.35
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rehan  3527 F pulseaudio
   /dev/snd/controlC0:  rehan  3527 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=796bfa06-20c4-4486-b4b3-6ea3ed8e0a7b
  InstallationDate: Installed on 2012-11-12 (1558 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=6cbf5176-699e-40cd-8119-3e1802a1e70a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (167 days ago)
  UserGroups: adm cdrom dip lp lpadmin mythtv plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To 

[Kernel-packages] [Bug 1666209] Re: PPC new 4.4.0-63-powerpc63-smp kernel kills networking

[Joseph Salisbury]

Can you test the latest upstream stable kernel to see if this regression
is already fixed?  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.50/

If the bug does still exies in 4.4.50, we can perform a kernel bisect to
identify the commit that introduced the regression.

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

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

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

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

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

** Tags added: kernel-da-key performing-bisect xenial

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

Title:
  PPC new 4.4.0-63-powerpc63-smp kernel kills networking

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

Bug description:
  After upgrading to a new kernel (4.4.0-63-powerpc64-smp) completely
  lost ethernet. Looks like the kernel doesn't load a module for my
  interface (driver r8169). Rolling back to previous kernel version
  fixes networking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666209/+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 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[Danilo Inácio]

I'm also having a similar issues, I have a xps 9360 with the killer 1535
board running on ubuntu 16.10. The weird part with my case is that I'm
unable to make new requests while the existing ones keep working fine
(like a download or a hangouts/skype call, they never drop).

Example, when browsing a website, the main page load, but the images
from a CDN not. Its very similar to a DNS problem, but I tried google
and open DNS without success. Also, I tested with my other computers and
devices and they are all working fine.

Another example is with music streaming, that fails only when changing
the music file.

I already did the fix suggested by #22, and also updated my linux-
firmware to 1.163 (http://mirrors.kernel.org/ubuntu/pool/main/l/linux-
firmware/)

Anyone had similar problems?
Would ubuntu 16.04 work better to me?

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 

[Kernel-packages] [Bug 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx

[David Martinka]

I ran into this same problem today on an update.

The above fix in #6 worked for me on:

Ubuntu 16.04.2 LTS

4.4.0-62-generic

The DKMS modules now compile after editing
/usr/src/zfs-0.6.5.6/module/zfs/zpl_xattr.c

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

Title:
  Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with
  identifier from /mnt/disk/by-id/

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  zfs-dkms 0.6.5.6-0ubuntu15

  I cant mount/install my zpool. so i tried reinstalling zfslinux-utils,
  which gives me three error messages like this: "zfs-mount.service is a
  disabled" or a static unit, not starting it."...

  If something doesn't work I try googling error messages. most answers
  not totally like my problem but related to dkms, so I tried loading
  zfs-dkms and reinstalling zfslinux-utils.

  I created the zpool with id from /mnt/disk/by-id/ - which is zfs good-
  practice. This may be causing problems with the mount. I dont know...

  Cheers.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
  Uname: Linux 4.4.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-58-generic
  Date: Sat Jan  7 15:58:15 2017
  DuplicateSignature: 
dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12:
 error: too few arguments to function ‘posix_acl_valid’
  InstallationDate: Installed on 2016-12-26 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225)
  PackageVersion: 0.6.5.6-0ubuntu15
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1654708/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

Hi, Mr. Iain Buclaw.

Memory usage reports could be related to something else. This bug was
introduced at 4.4.0-59, you mention 4.4.0-58. We could certainly
investigate the issue you see, just not on this bug. Much more data is
necessary, but, please, don't attach new data to this bug. Your report
relates to a different kernel, which has a very different memory
management code. I could ask you to test 4.4.0-63, but it still is
possible that you find problems there, because they are unrelated to
this bug.

Thank you.
Cascardo.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/ubuntu/+source/linux/+bug/1655842/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Iain Buclaw]

The OOM fixes were introduced in 4.4.0-58 according to the changelog,
but sure.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/ubuntu/+source/linux/+bug/1655842/+subscriptions

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

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

[Emsi]

I can confirm that the trusty patches are preventing the filesystem
failure.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

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

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Iain Buclaw]

This is the reported /proc/meminfo Buffers usage for 4 different kernel
versions.  We got the same OOM call traces on both 4.4.0-58 and
4.8.0-34, I highly doubt that to be a coincidence.

** Attachment added: "meminfo-buffers.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4822727/+files/meminfo-buffers.png

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/ubuntu/+source/linux/+bug/1655842/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

This bug is not about memory use. It's about the Linux kernel triggering
the OOM killer when higher-order (order 2) allocations are requested and
progress cannot be made. This affected Linux 4.7 on mainline and was
fixed on Linux 4.7 stable and Linux 4.8. When some fixes were backported
to 4.4.0-59 (4.4.0-58 was not affected), this bugs was introduced to
Xenial kernels and is now fixed on 4.4.0-63. Any behavior on 4.8 kernels
must be investigated separately, because all fixes that were backported
to 4.4.0-63 are already present in 4.8.

Can you please open a new bug and attach all logs and details you can,
so we can investigate your problem and provide a fix? Please, do not use
this bug, because the fixes would be different anyway, and even thought
the symptom may look like, we consider them different bugs.

I appreciate you opening a new bug and providing this new report.

Thanks.
Cascardo.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/ubuntu/+source/linux/+bug/1655842/+subscriptions

-- 
Mailing list: