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

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

Title:
  Auto Shutdown of system while web-browsing in tabs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Laptop shutdowns while web browsing in 6 or 7 sites at a time.

  Gateway NE56R laptop is in power-save mode.

  Instead of allowing shutdowns it should notify to close down some tabs
  or process if it cannot handle many process or heat (ie. when it
  exceeds allowed limits).

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

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

[Kernel-packages] [Bug 1488395] Re: backport of driver for I2C on Sunrisepoint PCH

[Jesse Sung]

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  backport of driver for I2C on Sunrisepoint PCH

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Released

Bug description:
  Some newly released laptops talk to touchpad via I2C to provide
  advanced functions. The new Intel Skylake uses Sunrisepoint PCH, thus
  the I2C on it needs to to enabled in order to support these touchpads.

  Intel is still working on the driver. There are six versions so far:
  v1: https://lkml.org/lkml/2015/3/31/255
  v2: https://lkml.org/lkml/2015/5/25/298
  v3: https://lkml.org/lkml/2015/6/1/429
  v4: https://lkml.org/lkml/2015/6/15/160
  v5: https://lkml.org/lkml/2015/7/6/317
  v6: https://lkml.org/lkml/2015/7/27/599

  The driver supports SPI, UART, and I2C on the Sunrisepoint PCH, but
  we'll only focus on the I2C part.

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

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

[Kernel-packages] [Bug 1649057] [NEW] Auto Shutdown of system while web-browsing in tabs

[Oppili]

Public bug reported:

Ubuntu Laptop shutdowns while web browsing in 6 or 7 sites at a time.

Gateway NE56R laptop is in power-save mode.

Instead of allowing shutdowns it should notify to close down some tabs
or process if it cannot handle many process or heat (ie. when it exceeds
allowed limits).

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


** Tags: auto random shutdown 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/1649057

Title:
  Auto Shutdown of system while web-browsing in tabs

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu Laptop shutdowns while web browsing in 6 or 7 sites at a time.

  Gateway NE56R laptop is in power-save mode.

  Instead of allowing shutdowns it should notify to close down some tabs
  or process if it cannot handle many process or heat (ie. when it
  exceeds allowed limits).

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

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

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

Title:
  "Power off" required for resume from hybrid-sleep on AC power

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Due to issues with "waking from suspend", I have modified a few entries in 
/etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 
'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 
'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my 
laptop lid while it is plugged it and when I return to it later, it does not 
resume on lifting the lid. The disk spins up and the fan runs as if the laptop 
was resuming but I am unable to do anything other than hold the power button 
down until it shuts down - much as I had to when I was having problems with 
suspend. When I hit the power button again and select the entry for Ubuntu in 
grub, the laptop boots to the login screen normally. When I log in, everything 
is just as it was when I originally closed the laptop's lid - basically 
"resuming" the way I had hoped. I do not believe that this is the intended 
behavior as I have had my computer resume from hybrid-sleep without powering it 
off in 16
 .04 and in 16.10 (I have not, that I know of, experienced this problem while 
on battery power). In case it is relevant, the current values of 'Suspend when 
inactive for' and 'When the lid closes' in Settings > Power are "Don't suspend" 
(for battery and plugged in) and "Suspend" (for battery and plugged in), 
respectively.
  I will attach the output from 'cat /proc/version_signature' and 'lspci -vnvn' 
but I would like to add that 'sudo lspci -vnvn' sent 'pcilib: sysfs_read_vpd: 
read failed: Input/output error' to stderr, which was not redirected to the log 
file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steven 4004 F pulseaudio
   /dev/snd/controlC0:  steven 4004 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 10 22:06:19 2016
  HibernationDevice: RESUME=UUID=891e7a47-9f8c-4fc9-9fe3-fe5c88ef2147
  InstallationDate: Installed on 2016-11-23 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20347
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=b40d7383-45c3-4885-a1df-0e534eb44fef ro quiet splash 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 99CN21WW(V1.04)
  dmi.board.asset.tag: Std
  dmi.board.name: Lenovo Y40-70
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr99CN21WW(V1.04):bd03/24/2014:svnLENOVO:pn20347:pvrLenovoY40-70:rvnLENOVO:rnLenovoY40-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY40-70:
  dmi.product.name: 20347
  dmi.product.version: Lenovo Y40-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1649048] [NEW] "Power off" required for resume from hybrid-sleep on AC power

[Steven Ward]

Public bug reported:

Due to issues with "waking from suspend", I have modified a few entries in 
/etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 
'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 
'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my 
laptop lid while it is plugged it and when I return to it later, it does not 
resume on lifting the lid. The disk spins up and the fan runs as if the laptop 
was resuming but I am unable to do anything other than hold the power button 
down until it shuts down - much as I had to when I was having problems with 
suspend. When I hit the power button again and select the entry for Ubuntu in 
grub, the laptop boots to the login screen normally. When I log in, everything 
is just as it was when I originally closed the laptop's lid - basically 
"resuming" the way I had hoped. I do not believe that this is the intended 
behavior as I have had my computer resume from hybrid-sleep without powering it 
off in 16.0
 4 and in 16.10 (I have not, that I know of, experienced this problem while on 
battery power). In case it is relevant, the current values of 'Suspend when 
inactive for' and 'When the lid closes' in Settings > Power are "Don't suspend" 
(for battery and plugged in) and "Suspend" (for battery and plugged in), 
respectively.
I will attach the output from 'cat /proc/version_signature' and 'lspci -vnvn' 
but I would like to add that 'sudo lspci -vnvn' sent 'pcilib: sysfs_read_vpd: 
read failed: Input/output error' to stderr, which was not redirected to the log 
file.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-30-generic 4.8.0-30.32
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  steven 4004 F pulseaudio
 /dev/snd/controlC0:  steven 4004 F pulseaudio
CurrentDesktop: Unity
Date: Sat Dec 10 22:06:19 2016
HibernationDevice: RESUME=UUID=891e7a47-9f8c-4fc9-9fe3-fe5c88ef2147
InstallationDate: Installed on 2016-11-23 (17 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 20347
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=b40d7383-45c3-4885-a1df-0e534eb44fef ro quiet splash 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: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 99CN21WW(V1.04)
dmi.board.asset.tag: Std
dmi.board.name: Lenovo Y40-70
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: Std
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Y40-70
dmi.modalias: 
dmi:bvnLENOVO:bvr99CN21WW(V1.04):bd03/24/2014:svnLENOVO:pn20347:pvrLenovoY40-70:rvnLENOVO:rnLenovoY40-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY40-70:
dmi.product.name: 20347
dmi.product.version: Lenovo Y40-70
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug yakkety

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

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

Title:
  "Power off" required for resume from hybrid-sleep on AC power

Status in linux package in Ubuntu:
  New

Bug description:
  Due to issues with "waking from suspend", I have modified a few entries in 
/etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 
'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 
'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my 
laptop lid while it is plugged it and when I return to it later, it does not 
resume on lifting the lid. The disk spins up and the fan runs as if the laptop 
was resuming but I am unable to do anything other than hold the power button 
down until it shuts down - much as I had to when I was having problems with 
suspend. When I hit the power button again and select the entry for Ubuntu in 
grub, the laptop boots to the login screen normally. When I log in, everything 
is just as it was when I originally closed the laptop's lid - basically 
"resuming" the way I had hoped. I do not believe that this is the intended 
behavior as I have had my computer resume from hybrid-sleep without powering it 
off in 16
 .04 and in 16.10 (I have not, that I know of, experienced this problem while 
on battery power). In case it is relevant, the current values of 'Suspend when 
inactive for' and 'When the lid 

[Kernel-packages] [Bug 1632237] Re: I have no expertise on progamming please

[Launchpad Bug Tracker]

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

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

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

Title:
  I have no expertise on progamming please

Status in bcmwl package in Ubuntu:
  Expired

Bug description:
  Installation of upgrades failed

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

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

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

[冯宇]

Same issue here, bluetooth mouse often hans.

journalctl --unit=bluetooth
-- Logs begin at 日 2016-12-11 10:01:22 CST, end at 日 2016-12-11 11:32:43 CST. --
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Bluetooth daemon 5.37
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Starting SDP server
12月 11 10:01:25 fengyu-laptop systemd[1]: Starting Bluetooth service...
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Bluetooth management interface 
1.10 initialized
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Failed to obtain handles for 
"Service Changed" characteristic
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to 
register service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Error adding Link Loss service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to 
register service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to 
register service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to 
register service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Current Time Service could not 
be registered
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: gatt-time-server: Input/output 
error (5)
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to 
register service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to 
register service
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Sap driver initialization 
failed.
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: sap-server: Operation not 
permitted (1)
12月 11 10:01:25 fengyu-laptop systemd[1]: Started Bluetooth service.
12月 11 10:01:27 fengyu-laptop bluetoothd[2142]: Endpoint registered: 
sender=:1.29 path=/MediaEndpoint/A2DPSource
12月 11 10:01:27 fengyu-laptop bluetoothd[2142]: Endpoint registered: 
sender=:1.29 path=/MediaEndpoint/A2DPSink
12月 11 10:07:31 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x000c for device C5:5B:CD:DB:C5:D1
12月 11 10:07:31 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x0017 for device C5:5B:CD:DB:C5:D1
12月 11 10:07:31 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x001b for device C5:5B:CD:DB:C5:D1
12月 11 11:16:20 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x000c for device C5:5B:CD:DB:C5:D1
12月 11 11:16:20 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x0017 for device C5:5B:CD:DB:C5:D1
12月 11 11:16:20 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x001b for device C5:5B:CD:DB:C5:D1
12月 11 11:18:09 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x000c for device C5:5B:CD:DB:C5:D1
12月 11 11:18:09 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x0017 for device C5:5B:CD:DB:C5:D1
12月 11 11:18:09 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x001b for device C5:5B:CD:DB:C5:D1
12月 11 11:26:21 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x000c for device C5:5B:CD:DB:C5:D1
12月 11 11:26:21 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x0017 for device C5:5B:CD:DB:C5:D1
12月 11 11:26:21 fengyu-laptop bluetoothd[2142]: Unable to register GATT service 
with handle 0x001b for device C5:5B:CD:DB:C5:D1
12月 11 11:29:41 fengyu-laptop systemd[1]: Stopping Bluetooth service...
12月 11 11:29:41 fengyu-laptop bluetoothd[2142]: Terminating
12月 11 11:29:46 fengyu-laptop bluetoothd[2142]: Endpoint unregistered: 
sender=:1.29 path=/MediaEndpoint/A2DPSource
12月 11 11:29:46 fengyu-laptop bluetoothd[2142]: Endpoint unregistered: 
sender=:1.29 path=/MediaEndpoint/A2DPSink
12月 11 11:29:46 fengyu-laptop systemd[1]: Stopped Bluetooth service.
12月 11 11:29:46 fengyu-laptop systemd[1]: Starting Bluetooth service...
12月 11 11:29:46 fengyu-laptop systemd[1]: Started Bluetooth service.
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Bluetooth daemon 5.37
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Starting SDP server
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Bluetooth management interface 
1.10 initialized
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Failed to obtain handles for 
"Service Changed" characteristic
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to 
register service
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Error adding Link Loss service
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to 
register service
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to 
register service
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to 
register service
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Current Time Service could not 
be registered
12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: gatt-time-server: Input/output 
error (5)
12月 11 11:29:46 fengyu-laptop 

[Kernel-packages] [Bug 1490212] Re: "Modaliases" field missing from debian control file

[Mathew Hodson]

** No longer affects: software-properties (Ubuntu)

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

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  Expired

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+subscriptions

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

[Kernel-packages] [Bug 1491070] Re: On removal the package should warn a reboot is needed

[Mathew Hodson]

** Changed in: bcmwl (Ubuntu)
   Importance: Undecided => Low

** Changed in: bcmwl (Ubuntu Trusty)
   Importance: Undecided => Low

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

Title:
  On removal the package should warn a reboot is needed

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  When the bcmwl-kernel-source package is removed it should communicate
  that a reboot is needed. This will be picked up by software-
  properties-gtk and be communicated to the user.  Attached is a patch.

  This will help with this bug
  https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212

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

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

[Kernel-packages] [Bug 1490713] Re: The Debian control file's "modaliases" is too generic

[Mathew Hodson]

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

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

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

Title:
  The Debian control file's "modaliases" is too generic

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  Software-properties-gtk offers wl as the driver for all Broadcom wifi
  cards, regardless of whether they are supported or not.  This is due
  to the modaliases field used by the bcmwl-kernel-source package.

  Although in reality I know very little about such things, I'll attach
  a proposed debian/bcmwl-kernel-source.modaliases file based on the
  info here:
  http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt

  Users are going through needless painful procedures to get the correct
  working driver.

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

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

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1649039/+attachment/4790165/+files/UdevDb.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790166/+files/WifiSyslog.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790156/+files/CurrentDmesg.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790160/+files/ProcCpuinfo.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1649039/+attachment/4790158/+files/Lspci.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790161/+files/ProcEnviron.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1649039/+attachment/4790159/+files/Lsusb.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790164/+files/PulseList.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing 

[Kernel-packages] [Bug 1649039] CRDA.txt

[Nazar Mokrynskyi]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1649039/+attachment/4790155/+files/CRDA.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/1649039

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

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

[Nazar Mokrynskyi]

apport information

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

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790163/+files/ProcModules.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing 

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

[Nazar Mokrynskyi]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790162/+files/ProcInterrupts.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 

[Kernel-packages] [Bug 1649039] Re: USB 3.1 controller does weird magic: appears after Windows 10, disappears otherwise

[Nazar Mokrynskyi]

apport information

** Tags added: apport-collected zesty

** Description changed:

  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.
  
  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).
  
  But magically situation changes when involve Windows 10 to the party. I
  boot into Windows PE based on Windows 10 and it happily see flash drive
  and my Nexus 6P connected to both ports.
  
  After this without unplugging mentioned devices I reboot into Ubuntu and
  "magic" - both flash drive and Nexus 6P work fine through these 2 USB
  Type-C ports. Even though it works in Ubuntu, BIOS still doesn't see
  anything.
  
  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd
  
  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as I
  unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:
  
  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  
  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
+  /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
+ CurrentDesktop: Custom
+ DistroRelease: Ubuntu 17.04
+ EcryptfsInUse: Yes
+ IwConfig: Error: [Errno 2] Немає такого файла або каталогу
+ MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
+ ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
+ RelatedPackageVersions:
+  linux-restricted-modules-4.9.0-10-lowlatency N/A
+  linux-backports-modules-4.9.0-10-lowlatency  N/A
+  linux-firmware   1.162
+ RfKill: Error: [Errno 2] Немає такого файла або каталогу
+ Tags:  zesty
+ Uname: Linux 4.9.0-10-lowlatency x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 11/07/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F20b
+ dmi.board.asset.tag: Default string
+ dmi.board.name: Z170X-UD5 TH-CF
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.name: Z170X-UD5 TH
+ dmi.product.version: Default string
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1649039/+attachment/4790154/+files/AlsaInfo.txt

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  

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

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8

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

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

[Kernel-packages] [Bug 1649039] [NEW] USB 3.1 controller does weird magic: appears after Windows 10, disappears otherwise

[Nazar Mokrynskyi]

Public bug reported:

I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
3.1/Thunderbolt 3) ports, BIOS version F20b.

Both ports are "sleeping" on cold start - I can't boot from USB device
plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
of December 11 doesn't see anything (no messages in dmesg).

But magically situation changes when involve Windows 10 to the party. I
boot into Windows PE based on Windows 10 and it happily see flash drive
and my Nexus 6P connected to both ports.

After this without unplugging mentioned devices I reboot into Ubuntu and
"magic" - both flash drive and Nexus 6P work fine through these 2 USB
Type-C ports. Even though it works in Ubuntu, BIOS still doesn't see
anything.

nazar-pc  ~  lspci -d ::0c03 -k   

 
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

But things are even more interesting: when I unplug either Nexus 6P or
flash drive and then plug back - they still work fine! But as soon as I
unplug both of them - Ubuntu doesn't see anything and doesn't post
anything into dmesg until I boot into Windows 10 again. Interestingly,
USB 3.1 controller disappears:

nazar-pc  ~  lspci -d ::0c03 -k   

 
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

nazar-pc  ~   cat /proc/version_signature 

 
Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8

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


** Tags: 3.1 type-c usb

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  

[Kernel-packages] [Bug 1647036] Re: Client does not ACK auth/assoc responses from Cisco AP3800

[Launchpad Bug Tracker]

This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-0ubuntu1

---
bcmwl (6.30.223.271+bdcom-0ubuntu1) zesty; urgency=medium

  * debian/dkms.conf.in
- Drop obsolete patches.
  * New upstream release:
- Client does not ACK auth/assoc responses from Cisco AP3800 (LP: #1647036).

 -- Alberto Milone   Tue, 06 Dec 2016
16:29:07 +0100

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

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

Title:
  Client does not ACK auth/assoc responses from Cisco AP3800

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

Bug description:
  This client does not ACK Assoc Responses from a Cisco 3800.  Traces
  attached.

  - Model:Dell XPS13 9343
  - OS Version:Ubuntu 14.04.5 LTS
  - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248
  - SSID:user.wifi (WPA2/dot1x )
  - MAC address:c4:8e:8f:f5:4a:7f
  -Cisco AP : 3800 (wave 2)

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

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

[Kernel-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!

[aljosa]

Lenovo Y700-17ISK notebook (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia 
GTX960M 4GB)
BIOS CDCN53WW 09/19/2016
Ubuntu 16.04.1
Kernel 4.8.14

[3.591312] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (5986:0672)
[3.594145] uvcvideo 1-6:1.0: Entity type for entity Realtek Extended Controls 
Unit was not initialized!
[3.594147] uvcvideo 1-6:1.0: Entity type for entity Extension 4 was not 
initialized!
[3.594148] uvcvideo 1-6:1.0: Entity type for entity Processing 2 was not 
initialized!
[3.594149] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not 
initialized!
[3.594214] input: Lenovo EasyCamera as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input11

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

Title:
  uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not
  initialized!

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

Bug description:
  [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
  [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was 
not initialized!
  [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!

  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 17:20:51 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 CO., LTD.

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[Mons ter Wade]

BQ Aquaris E5
Volkswagen Phaeton 2011 (VW Navigation System RNS810)
OTA14

Finally IT WORKS! But from the beginning:

After the OTA 14 Update I tried again to connect to my in car bluetooth
system and make calls. Connecting (still) worked. Next I tried to make a
call and again no sound from the speakers. After random changes on both
ends (phone and in car system, of course with no systematic tracking), I
tried again to call somebody and now speakers/mic worked perfectly. I
left my car, entered again, phone reconnected and now again no sound!?!
Wtf? But I was hooked, if it worked one time, it has to be possible to
make it work again ...

It took me some time to track down the necessary conditions for a stable
and working bluetooth connection:

1. In the phones bluetooth settings the auto connect button for the
connection to the in car bluetooth system has to be disabled. If this is
not disabled, the car and the phone try to establish the connection at
the same time and things get messed up, up to the point where both
systems eventually freeze.

2. The car system can only establish the bluetooth connection, if the
screen of the phone is unlocked.

That's all. If you pay attention to these 2 points, really everything
works perfectly (for Volkswagen systems)! Even streaming media via
bluetooth works!

I'm really excited, thank you very much for your work! I use my phone
for business and desperately needed a working hands free system in my
car. Unlocking my screen after entering the car is no big deal to me.
Switching back to android is now definitely off the table. Thank you
again and keep up the great work! I really love the usability and GUI of
my ubuntu phone!

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

[Kernel-packages] [Bug 1543788] Re: Fails to resume from suspend

[Abderrahman Jouhari]

Thank You Christopher and sorry i just noticed your reply. I upgraded
the kernel to 4.6.2-040602-generic and my Nvidia card Geforce GT 740M
drivers to 375.20 version and that seems to have fixed the issue for me
now.

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

Title:
  Fails to resume from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Resuming from suspend used to work previously in 16.04.

  On resume I see a blank screen and nothing seems to respond. I've
  tried Ctrl+Alt+F1 and then Ctrl+Alt+Delete. Also tried the power
  button. No response.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shahar 2292 F pulseaudio
   /dev/snd/controlC0:  shahar 2292 F pulseaudio
   /dev/snd/controlC2:  shahar 2292 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Feb  9 22:51:40 2016
  HibernationDevice: RESUME=UUID=f2bd5594-8447-422c-a345-492ede4de1d9
  InstallationDate: Installed on 2010-10-12 (1946 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X10SRA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic root=/dev/mapper/root 
ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2015-11-13 (88 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd11/27/2014:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1647075] Re: Unable to enter password to decrypt filesystem on boot after upgrading kernel to 4.4.0-51

[Chris Schadl]

Tried it with mainline kernel 4.4.37-040437, looks like it's fixed
there.

** Tags added: kernel-fixed-upstream

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => 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/1647075

Title:
  Unable to enter password to decrypt filesystem on boot after upgrading
  kernel to 4.4.0-51

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

Bug description:
  Disk is encrypted using full disk encryption.  I could enter my
  password to decrypt the disk when booting in 4.4.0-47, but after
  upgrading to 4.4.0-51, I'm prompted for the password, but I can't type
  anything.

  I think the last time this happened there was some change with the USB
  HID modules or something (I'm using a USB keyboard).  Has there been
  any changes to the USB modules or configuration between kernel
  4.4.0-47 and 4.4.0-51?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  2447 F pulseaudio
   /dev/snd/controlC1:  chris  2447 F pulseaudio
   /dev/snd/controlC0:  chris  2447 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec  3 11:39:50 2016
  HibernationDevice: RESUME=UUID=8a9bf6f5-bb32-459a-8f5b-fc7f95451c26
  InstallationDate: Installed on 2014-07-04 (883 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet nosplash
  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:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH P67
  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.:bvr2001:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHP67: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/1647075/+subscriptions

-- 
Mailing list: https://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 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam

[Clint Byrum]

Excerpts from Joseph Salisbury's message of 2016-12-06 16:36:24 UTC:
> Can you also give the latest DRM nightly kernel a test?  It is available from:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2016-12-06/
> 

I'm installing it now. The crash is less frequent with 4.9 (have gone
2 hours now without it), so it may take me a few days to confirm it
doesn't happen anymore.

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

Title:
  I am getting frequent DRM hangs while playing Cities: Skylines from
  Steam

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

Bug description:
  It happens during normal gameplay. Have tried reducing settings. Seems
  like a legitimate driver bug. The program crashes, but X does not.

  [16868.151225] [drm] stuck on render ring
  [16868.155458] [drm] GPU HANG: ecode 8:0:0x84dffefc, in Cities.x64 [21076], 
reason: Ring hung, action: reset
  [16868.155472] [ cut here ]
  [16868.155503] WARNING: CPU: 1 PID: 13959 at 
/build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  [16868.155505] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
  [16868.155506] Modules linked in:
  [16868.155508]  tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio 
usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 
xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm 
aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common 
intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm 
snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi
  [16868.155545]  input_leds cdc_acm btusb usbnet serio_raw media btrtl 
snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi snd_hda_codec btintel 
memstick snd_hda_core cfg80211 bluetooth snd_hwdep snd_seq_midi 
snd_seq_midi_event intel_pch_thermal nvram snd_rawmidi lpc_ich snd_pcm mei_me 
mei shpchp snd_seq snd_seq_device snd_timer snd soundcore kvm_intel mac_hid kvm 
irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher 
af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt rtsx_pci fb_sys_fops ahci psmouse ptp drm libahci pps_core wmi fjes 
video
  [16868.155589] CPU: 1 PID: 13959 Comm: kworker/1:0 Tainted: GW  OE   
4.4.0-51-generic #72-Ubuntu
  [16868.155591] Hardware name: LENOVO 20CLS5N900/20CLS5N900, BIOS N10ET36W 
(1.15 ) 06/19/2015
  [16868.155617] Workqueue: events intel_mmio_flip_work_func [i915]
  [16868.155619]  0286 dd043c13 880382bbbd20 
813f5fc3
  [16868.155622]  880382bbbd68 c03a7ab8 880382bbbd58 
810812b2
  [16868.155624]  8802970af040 88042dc56500 88042dc5ae00 
0040
  [16868.155626] Call Trace:
  [16868.155632]  [] dump_stack+0x63/0x90
  [16868.155637]  [] warn_slowpath_common+0x82/0xc0
  [16868.155639]  [] warn_slowpath_fmt+0x5c/0x80
  [16868.155643]  [] ? __switch_to+0x437/0x5c0
  [16868.155667]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
  [16868.155672]  [] process_one_work+0x165/0x480
  [16868.155674]  [] worker_thread+0x4b/0x4c0
  [16868.155677]  [] ? process_one_work+0x480/0x480
  [16868.155679]  [] kthread+0xd8/0xf0
  [16868.155681]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [16868.155685]  [] ret_from_fork+0x3f/0x70
  [16868.155687]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [16868.155689] ---[ end trace 1339c06922e659f4 ]---
  [16868.157772] drm/i915: Resetting chip after gpu hang
  [16874.163802] [drm] stuck on render ring
  [16874.168161] [drm] GPU HANG: ecode 8:0:0x86dd, in Cities.x64 [21076], 
reason: Ring hung, action: reset
  [16874.168182] [ cut here ]
  [16874.168215] WARNING: CPU: 1 PID: 13959 at 
/build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  [16874.168216] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
  [16874.168217] Modules linked in:
  [16874.168221]  tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio 
usbhid hid snd_usbmidi_lib usb_serial_simple usbserial 

[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[jagdtigger]

Who knows, the detachable tablet thingy i have has another issue beside
this, it has a micros SD slot but for some reason kubuntu wont read any
card i put in it. Just throws out some error in dmesg. I submitted a bug
report but that was a month ago(plus it was sitting on the forums for a
very long time until i had enough and submitted the bug report) and
there is still no solution for it :/ ...

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Kernel-packages] [Bug 1648526] Re: Intel 8265 Bluetooth ([8087:0A2B]) fails to init properly on wakeup from hibernation

[Leonard Lausen]

I have confirmed that the issue is also present in a self-compiled
upstream version of v4.9-rc8 and reported it at
http://www.spinics.net/lists/linux-bluetooth/msg69063.html

** Tags added: kernel-bug-reported-upstream

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

Title:
  Intel 8265 Bluetooth ([8087:0A2B]) fails to init properly on wakeup
  from hibernation

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am experiencing issues with hibernation on a xiaomi mibook air with
  the Intel 8265 Bluetooth chip ([8087:0A2B]). When waking up from
  hibernation, the chip fails to properly initialize (?).

  More specifically, when trying to hibernate a second time the notebook will 
fail to enter hibernation mode due to:
  "Freezing of tasks failed after 20.00r seconds (1 tasks refusing to freeze, 
wq_busy=0)"
  where the task failing to freeze is hciconfig.

  This seems to be due to a kernel bug initializing the bluetooth device
  on wakeup from hibernation. The kernel message reads "kernel:
  Bluetooth: hci0: Setting Intel event mask failed (-16)".

  I have attached
  1) /proc/version_signature
  2) sudo lspci -vnvn
  3) journalctrl

  I can confirm that the issue with hibernation is resolved by blacklisting the 
bluetooth chip in 
  /etc/udev/rules.d/81-bluetooth-hci.rules

  I have tried the most recent mainline kernel from the ubuntu kernel
  ppa and can confirm that the problem also occurs there
  (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8/).

  
  Please let me know if I can provide any other information to help fixing this 
bug.

  I am running Maui Linux, which is basically Ubuntu 16.04 but includes more 
up-to-date KDE packages.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leonard1336 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Maui 2.1
  InstallationDate: Installed on 2016-12-02 (5 days ago)
  InstallationMedia: Maui - Release amd64 (20160811)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b5a3 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Timi TM1613
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic 
root=/dev/mapper/lvm-btrfs ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/lvm-swap vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-25-generic N/A
   linux-backports-modules-4.8.0-25-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial xenial
  Uname: Linux 4.8.0-25-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 08/11/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: A05
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TM1613
  dmi.board.vendor: Timi
  dmi.board.version: A05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrA05:bd08/11/2016:svnTimi:pnTM1613:pvrA05:rvnTimi:rnTM1613:rvrA05:cvnTimi:ct10:cvrA05:
  dmi.product.name: TM1613
  dmi.product.version: A05
  dmi.sys.vendor: Timi

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

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

[Kernel-packages] [Bug 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Chris Valean]

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[Vincas Dargis]

With OTA-14 I can now pair with Parrot CK3100 again, but there is still
no sound (crossed note symbol).

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

[Kernel-packages] [Bug 1608526] Re: Asus N551JM screen brightness keys fn+F5/F6 don't work unless using kernel parameter acpi_osi=

[Vincas Dargis]

I have bumped bug report on linux-acpi list [1], but still with no
reply.

With 4.9 rc8 buttons still does not work.

[1] https://marc.info/?l=linux-acpi=147550958501931=2

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

Title:
  Asus N551JM screen brightness keys fn+F5/F6 don't work unless using
  kernel parameter acpi_osi=

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Keyboard combination fn+F5/F6 keys doesn't decrease/increase the
  screen brightness.

  WORKAROUND: Add kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincas 4675 F pulseaudio
   /dev/snd/controlC0:  vincas 4675 F pulseaudio
  Date: Mon Aug  1 16:20:41 2016
  HibernationDevice: RESUME=UUID=8c5322e6-f871-4abf-b1e0-61b84f0aa4b4
  InstallationDate: Installed on 2015-06-25 (402 days ago)
  InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  ProcEnviron:
   LANGUAGE=
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=e2407f5a-3411-4b70-a245-7c128267680f ro quiet splash acpi_osi= 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (1 days ago)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  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/1608526/+subscriptions

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

[Kernel-packages] [Bug 1646150] Re: linux: 4.4.0-52.73 -proposed tracker

[Luis Henriques]

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

** This bug is no longer a duplicate of bug 1648579
   linux: 4.4.0-56.77 -proposed tracker
** This bug has been marked a duplicate of bug 1648867
   linux: 4.4.0-57.78 -proposed tracker

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

Title:
  linux: 4.4.0-52.73 -proposed tracker

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

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

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

  -- swm properties --
  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-sru-workflow/+bug/1646150/+subscriptions

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

[Kernel-packages] [Bug 1648017] Re: linux: 4.4.0-54.75 -proposed tracker

[Luis Henriques]

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

** This bug is no longer a duplicate of bug 1648579
   linux: 4.4.0-56.77 -proposed tracker
** This bug has been marked a duplicate of bug 1648867
   linux: 4.4.0-57.78 -proposed tracker

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-54.75 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-sru-workflow/+bug/1648017/+subscriptions

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

[Kernel-packages] [Bug 1648503] Re: linux: 4.4.0-55.76 -proposed tracker

[Luis Henriques]

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

** This bug is no longer a duplicate of bug 1648579
   linux: 4.4.0-56.77 -proposed tracker
** This bug has been marked a duplicate of bug 1648867
   linux: 4.4.0-57.78 -proposed tracker

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

Title:
  linux: 4.4.0-55.76 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-55.76 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-stable-phase:Packaging
  kernel-stable-phase-changed:Thursday, 08. December 2016 14:51 UTC

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

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

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

[Kernel-packages] [Bug 1648495] Re: linux: 4.4.0-55.76 -proposed tracker

[Luis Henriques]

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

** This bug is no longer a duplicate of bug 1648579
   linux: 4.4.0-56.77 -proposed tracker
** This bug has been marked a duplicate of bug 1648867
   linux: 4.4.0-57.78 -proposed tracker

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

Title:
  linux: 4.4.0-55.76 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-55.76 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-stable-phase:Packaging
  kernel-stable-phase-changed:Thursday, 08. December 2016 14:34 UTC

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

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

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

[Kernel-packages] [Bug 1648579] Re: linux: 4.4.0-56.77 -proposed tracker

[Luis Henriques]

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

** This bug has been marked a duplicate of bug 1648867
   linux: 4.4.0-57.78 -proposed tracker

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

Title:
  linux: 4.4.0-56.77 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-56.77 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-sru-workflow/+bug/1648579/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-10_10-11-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-10_09-46-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/onza__4.4.0-57.78__2016-12-10_09-22-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

[Kernel-packages] [Bug 1648867] modoc (ppc64el) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/modoc__4.4.0-57.78__2016-12-10_09-07-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/onza__4.4.0-57.78__2016-12-10_08-58-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

[Kernel-packages] [Bug 1648867] s2lp6g001 (s390x.zKVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-53.74-generic/s2lp6g001__4.4.0-53.74__2016-12-10_08-36-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

[Kernel-packages] [Bug 1648867] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-53.74-generic/s2lp3__4.4.0-53.74__2016-12-10_08-36-00/results-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

[Kernel-packages] [Bug 1648867] Re: linux: 4.4.0-57.78 -proposed tracker

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-53.74-generic/kernel01__4.4.0-53.74__2016-12-10_08-36-00/results-index.html

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

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

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

** Description changed:

  This bug is for tracking the 4.4.0-57.78 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-stable-phase:Uploaded
+ kernel-stable-phase-changed:Saturday, 10. December 2016 08:34 UTC

** Description changed:

  This bug is for tracking the 4.4.0-57.78 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-stable-phase:Uploaded
- kernel-stable-phase-changed:Saturday, 10. December 2016 08:34 UTC

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  libcpupower.so is not installed from linux-tools (saucy)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

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

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

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

[Dmitry Shachnev]

Added a patch against lp:~ubuntu-kernel/ubuntu/+source/linux/+git/zesty
that adds a libcpupower-dev package, compatible with what Debian has.

Dear kernel team, please review it.

** Patch added: 
"0001-UBUNTU-Add-a-new-libcpupower-dev-package-for-compati.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+attachment/4789839/+files/0001-UBUNTU-Add-a-new-libcpupower-dev-package-for-compati.patch

** Changed in: linux (Ubuntu)
 Assignee: Kamal Mostafa (kamalmostafa) => Ubuntu Kernel Team 
(ubuntu-kernel-team)

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

Title:
  libcpupower.so is not installed from linux-tools (saucy)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

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

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

[Kernel-packages] [Bug 1648867] Re: linux: 4.4.0-57.78 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-57.78 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-sru-workflow/+bug/1648867/+subscriptions

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