date:20170815

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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1710941

Title:
  Bluetooth stopped working after kernel update 4.4.0-91

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth connection to Bose Soundlink II have been fine for years.
  Applied a few new updates in the last day or two --- system was
  generally up to date, I don't often wait more than a week or so ---
  and now I can no longer connect.  Removed the device and re-paired
  just fine, although the speaker did not connect as it usually does
  after the pairing (i.e., it stayed in pairing mode).

  Messages in syslog:

  Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
  Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
  Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
  Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 15 20:34:34 2017
  InstallationDate: Installed on 2015-12-26 (597 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:6896 acl:46 sco:0 events:294 errors:0
TX bytes:4254 acl:32 sco:0 commands:156 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Kernel-packages] [Bug 1710941] Re: Bluetooth stopped working after kernel update 4.4.0-91

** Summary changed:

- Bluetooth stopped working after update
+ Bluetooth stopped working after kernel update 4.4.0-91

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

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

Title:
  Bluetooth stopped working after kernel update 4.4.0-91

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth connection to Bose Soundlink II have been fine for years.
  Applied a few new updates in the last day or two --- system was
  generally up to date, I don't often wait more than a week or so ---
  and now I can no longer connect.  Removed the device and re-paired
  just fine, although the speaker did not connect as it usually does
  after the pairing (i.e., it stayed in pairing mode).

  Messages in syslog:

  Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
  Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
  Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
  Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 15 20:34:34 2017
  InstallationDate: Installed on 2015-12-26 (597 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:6896 acl:46 sco:0 events:294 errors:0
TX bytes:4254 acl:32 sco:0 commands:156 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Weird. Does [1] have the touchscreen issue? 
[1] 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/linux-image-4.13.0-041300rc4-generic_4.13.0-041300rc4.201708062231_amd64.deb

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (208 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-rc5-elan0602 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1711028] Status changed to Confirmed

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

Title:
  Laptop freeze when plugged power cable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, my laptop freeze when i plugged the power cable or when i remove
  the power cable and has no function of the mouse or the keyboard. I
  have to restart system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   stefano7382 F...m pulseaudio
   /dev/snd/controlC0:  stefano7382 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug 16 06:21:21 2017
  HibernationDevice: RESUME=UUID=106e7865-d3bc-4093-950f-284f3089b24e
  InstallationDate: Installed on 2016-06-01 (440 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. N752VX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=2ff708a9-3c60-4dc1-a3d2-06dc141831c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (124 days ago)
  dmi.bios.date: 01/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N752VX.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N752VX
  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.:bvrN752VX.204:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N752VX
  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/1711028/+subscriptions

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

[Kernel-packages] [Bug 1711028] [NEW] Laptop freeze when plugged power cable

2017-08-15 Thread Stefano Novelli

Public bug reported:

Hi, my laptop freeze when i plugged the power cable or when i remove the
power cable and has no function of the mouse or the keyboard. I have to
restart system.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   stefano7382 F...m pulseaudio
 /dev/snd/controlC0:  stefano7382 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Aug 16 06:21:21 2017
HibernationDevice: RESUME=UUID=106e7865-d3bc-4093-950f-284f3089b24e
InstallationDate: Installed on 2016-06-01 (440 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. N752VX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=2ff708a9-3c60-4dc1-a3d2-06dc141831c1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-32-generic N/A
 linux-backports-modules-4.10.0-32-generic  N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-13 (124 days ago)
dmi.bios.date: 01/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N752VX.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N752VX
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.:bvrN752VX.204:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N752VX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug zesty

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

Title:
  Laptop freeze when plugged power cable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, my laptop freeze when i plugged the power cable or when i remove
  the power cable and has no function of the mouse or the keyboard. I
  have to restart system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   stefano7382 F...m pulseaudio
   /dev/snd/controlC0:  stefano7382 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug 16 06:21:21 2017
  HibernationDevice: RESUME=UUID=106e7865-d3bc-4093-950f-284f3089b24e
  InstallationDate: Installed on 2016-06-01 (440 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. N752VX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=2ff708a9-3c60-4dc1-a3d2-06dc141831c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (124 days ago)
  dmi.bios.date: 01/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N752VX.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N752VX
  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.:bvrN752VX.204:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N752VX
  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/1711028/+subscriptions

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

[Kernel-packages] [Bug 1696693] Re: Mousepad/trackpad not working

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

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

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

Title:
  Mousepad/trackpad not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  I booted my pc this morning and found that the trackpad is no longer
  responding. Moving it or clicking, there is no response.

  I did nothing special yesterday nor manually installed anything, the
  only thing that was installed was some new Ubuntu updates through the
  software updater.

  My laptop is an Asus ROG GL553VD with Ubuntu 16.04.2 LTS.

  Looking in the list of hardware to see if the trackpad is recognized,
  I found 'ITE Tech. Inc. ITE Device(8910)' which seems to be the name
  for my trackpad.

  I tried 'sudo apt-get install xserver-xorg-input-synaptics' but it
  said it was already up-to-date (version 1.8.2-1ubuntu3)

  I can't include the package name in this report as 'apt-cache policy
  pkgname' doesn't work ("N: Unable to locate package pkgname")

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun  8 11:11:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
  InstallationDate: Installed on 2017-05-28 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic.efi.signed 
root=UUID=958dbae2-1028-43ae-af29-6fa03c950ee3 ro acpi_backlight=vendor quiet 
splash acpi_osi= vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.301:bd12/30/2016:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun  8 10:44:13 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1631 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Kernel-packages] [Bug 1698348] Re: Bluetooth is not Working

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

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

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

Title:
  Bluetooth is not Working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Devices are not being searched .Ubuntu 16.04 is the version

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   prashant   1833 F...m pulseaudio
   /dev/snd/controlC1:  prashant   1833 F pulseaudio
   /dev/snd/controlC0:  prashant   1833 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 16:19:31 2017
  HibernationDevice: RESUME=UUID=0a483b1a-6963-4fde-acc5-1a072e0114c7
  InstallationDate: Installed on 2016-08-13 (306 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d0ba25a6-8a79-4837-9d88-62c640108868 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 066KRV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/20/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn066KRV:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1698299] Re: package linux-image-4.2.0-42-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

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

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  non-PAE kernel not supported

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-42-generic (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhyry  1172 F pulseaudio
  Date: Thu Jun 15 23:38:38 2017
  DpkgTerminalLog:
   Preparing to unpack .../linux-image-4.2.0-42-generic_4.2.0-42.49_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.2.0-42-generic_4.2.0-42.49_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  DuplicateSignature: package:linux-image-4.2.0-42-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=dca97c1f-7ca0-4fe7-af28-2d9535205a92
  InstallationDate: Installed on 2015-04-28 (779 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: Hewlett-Packard hp pavilion ze4900 (PR301UA#ABA)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic 
root=/dev/mapper/lubuntu--vg-root ro priority=low quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29ubuntu0.3
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.2.0-42-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to wily on 2016-02-29 (472 days ago)
  dmi.bios.date: 11/09/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.name: 3084
  dmi.board.vendor: Quanta
  dmi.board.version: 41.0B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd11/09/2004:svnHewlett-Packard:pnhppavilionze4900(PR301UA#ABA):pvrRev1:rvnQuanta:rn3084:rvr41.0B:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: hp pavilion ze4900 (PR301UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1710941] Re: Bluetooth stopped working after update

2017-08-15 Thread Doug Morse

Thanks Daniel.  Rolling back to kernel 4.4.0-87-generic #110-Ubuntu SMP
seemed to fix the problem.  Upgrading to 4.4.0-91 also seemed to cause
other problems: My system started overheating, eventually slowed to a
crawl (i.e., over a matter of minutes after each reboot slowed to the
point of being unresponsive), and I saw 4 instances (one for each core,
I presume) of kidle_interrupt, which I had never seen before.

I notice that 4.4.0-91 is no longer showing up as an update in the repos
for 16.04.

For what it's worth, I also downgraded libgd3 to version 2.1.1-4build2,
as it also upgraded around the same time as my recent kernel updates
(-87 and -89, but I don't think I ever rebooted into -89).

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

Title:
  Bluetooth stopped working after update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth connection to Bose Soundlink II have been fine for years.
  Applied a few new updates in the last day or two --- system was
  generally up to date, I don't often wait more than a week or so ---
  and now I can no longer connect.  Removed the device and re-paired
  just fine, although the speaker did not connect as it usually does
  after the pairing (i.e., it stayed in pairing mode).

  Messages in syslog:

  Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
  Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
  Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
  Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 15 20:34:34 2017
  InstallationDate: Installed on 2015-12-26 (597 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:6896 acl:46 sco:0 events:294 errors:0
TX bytes:4254 acl:32 sco:0 commands:156 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Kernel-packages] [Bug 1698454] Re: TCP/IP Throughput Limitation

2017-08-15 Thread Brandon Bates

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

** Package changed: linux (Ubuntu) => numactl (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/1698454

Title:
  TCP/IP Throughput Limitation

Status in irqbalance package in Ubuntu:
  New
Status in numactl package in Ubuntu:
  Confirmed

Bug description:
  I'm having a severe TCP receive problem with a new Ubuntu 16 server
  and an Intel 82599ES 10-Gigabit SFP+ (X520 series card) when a windows
  10 machine is used to send the data. The receive performance is 1Gb to
  2Gb steady using iperf single stream, while send is 9.42Gb.

  Here is what I have found:

  -Running 8 parallel streams in iperf gets me the full 9.42 in
  aggregate

  -Tried a few windows 10 machines with repeatable same results

  -Same results through switch or direct

  -Linux to linux no problems

  -Tested with clean installs of 16.04.02 and 4.4.0-66 kernel, latest
  the upgrade will give me, also tried 17.04 with up to
  4.10.0-20-generic same problem, tried 4.11.0-041100rc8-generic and
  problem seemed to go away for a bit but came back so I think that
  might be a red herring (see interesting note below).

  -14.04 and 15.10 with up to 4.2.8-040208-generic is 9.42/9.42 (works
  fine, couldn't get 4.3 to install on 15.10)

  -14.04 with the latest 5.0.4 ixgbe driver still works fine, does not
  seem to be a driver version issue.

  -Tried swapping out cards with another same model/chipset with same
  exact result

  -Large receive offload increases the performance from a steady 1Gb to
  a steady 2.14Gb

  -Disabling sack under got me 75% of the way back to full speed, but it
  was very unstable (didn't hold at a solid speed)

  -Using a different brand of card in this same server (but not the same
  slot) (mellanox infiniband running in ethernet mode) is 9.42/8.5
  (seems to work fine, 9.42 to 8.5 is windows machine limit I think)

  -Interesting: When swapping between intel and mellanox 10Gbe cards
  (with a reboot of the server inbetween, but not a reboot of the
  windows machine, and keeping the same IP on the server) the
  performance does not change immediately. When going from intel to
  mellanox the first test holds around 1 or 2Gbit, then after that it
  jumps up to 8.5 steady. Similarly when switching from mellanox to
  Intel the first 1 or 2 seconds of performance hits 8.x then drop in
  half or more and within 3 or 4 seconds it is back to 1Gbit and stays
  there for each subsequent iperf test.

  -Interesting: When capturing packets on wireshark on windows,
  performance comes up to 8.5! (No, ditching windows isn't an option
  here unfortunately. :) So obviously something in the way the two tcp
  stacks are interacting without a buffer inbetween when the intel
  driver is online is causing issues.

  -Port bonding makes no difference (nor should it for single stream)

  -Tried rolling the intel driver back to the 3.2.1 version that is on
  14.04 but it was too old to compile

  -I suspect this is a kernel TCP/IP implementation change somewhere
  between 4.2 and 4.4 that has caused it to not play nice with window's
  stack.  Based on the delayed performance change I'm thinking something
  is messing with flow control, the tcp congestion algorithm, or the tcp
  window. I tried turning some various tcp options off, tweaking some
  values, changing congestion algorithms, hardware flow control, and
  comparing sysctl stuff from the u14 machine to this machine to no
  avail.

  UPDATE:
  My initial conclusion on something changing in the Kernel was incorrect.  
I've since tested 17.04 all the way back to 4.2.8 and it still fails.  I've 
also tested 15.10 up to 4.3.6 and it works correctly.  So something in Ubuntu's 
implementation changed between 15.10 and 16.04 that is causing this bug.

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

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

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

https://lkml.org/lkml/2017/8/15/817

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

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1710501] Re: can't open synaptic package manager

2017-08-15 Thread Po-Hsu Lin

Hi kevinek,

I have checked in our repository, package linux-image-4.10.0-23-generic does 
not exist anymore.
(with command "apt-cache search linux-image-4.10.0-23-generic")

The latest kernel package in -release is linux-image-4.10.0-32-generic, so 
please try to remove that old package and install the new one with:
sudo apt-get remove linux-image-4.10.0-23-generic
sudo apt-get install linux-image-generic

Also, I noticed that you have -proposed enabled in your repository
setting, which is for some experimental purpose. So if you are not doing
this intentionally, I would suggest you to disable it from the "Software
& Update" tool.

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

Title:
  can't open synaptic package manager

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I try and open synaptic package man. I get this message.
  E: The package linux-image-4.10.0-23-generic needs to be reinstalled, but I 
can't find an archive for it.
  E: Internal error opening cache (1). Please report.

  Before this the software updater is showing 1 update but does not
  update it, I click on install and it says installing a few moments but
  then returns to showing one update to be done?

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

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

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

2017-08-15 Thread Miroslaw

How awkward ...
I ask you to remove the new status. Randomness.

-- 
You 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:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released

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 1710868] Re: memory-hotplug test needs to be fixed

2017-08-15 Thread Po-Hsu Lin

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  memory-hotplug test needs to be fixed

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:

  Impact: 
  The memory-hotplug test in the kernel tree 
(tools/testing/selftests/memory-hotplug/) needs to be fixed:
  1. The test will pass even the memory blocks are failed to be offlined [1].
  2. It's using a random number generator to decide if each memory block needs 
to be offlined, which is not ideal for testing as the block it tries to unplug 
might be different between two runs.
  3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. 
It's being used as the percentage to get a memory block offlined instead.

  Fix: 
  Apply the following patch from upstream can fix these issues:
  593f9278 - selftests: typo correction for memory-hotplug test
  a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test
  72441ea5 - selftests: check percentage range for memory-hotplug test
  02d8f075 - selftests: add missing test name in memory-hotplug test
  5ff0c60b - selftests: fix memory-hotplug test

  Testcase:
  Run the script directly, it will fail when all memory blocks are busy. And it 
will try to unplug memory blocks in a fixed order.

  Regression Potential:
  Negligible, it's just affecting this specific test case among those testing 
tools.

  [1] https://paste.ubuntu.com/25318445/

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

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

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

2017-08-15 Thread Miroslaw

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

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

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

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released

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 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop

I wrote a simple WMI driver for the laptop - but maybe GIGABYTE hotkey doesn't 
use WMI at all?
You probably need to ask Gigabyte to share more information.

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

Title:
  Brightness control keys not working on Gigabyte P57 laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My
  brightness control keys (fn+F3, fn+F4) are not getting detected. After
  reading about how keypresses are handled by the Linux kernel, I used
  showkey to check the scancodes of these keys. I did not get any
  output. Similarly no output from xev, evtest and acpi_listen.

  Just for your reference, other keys like volume up (fn+F9) are working 
alright.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-12-14 (65 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.8.0-040800-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1478696] Re: dell-laptop: Incorrect keyboard backlight detection

I guess this commit solves the issue:
1b1ffc57a1b2 platform/x86: dell-laptop: Fix bogus keyboard backlight sysfs 
interface

Latest mainline kernel (v4.13-rc5) has this commit. Give it a try.

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

Title:
  dell-laptop: Incorrect keyboard backlight detection

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I own Dell Inspiron M5110 (Q15R). This laptop has no keyboard backlight, but 
dell-laptop claims otherwise.
  My syslog was getting spammed with "Keyboard brightness level control not 
supported" as dell-laptop was trying to get/set backlight values.

  In dell-laptop there is kbd_led_present variable, but on my M5110 it's
  being set to true:

ret = kbd_init_info();
(...)
if (kbd_token_bits != 0 || ret == 0)
kbd_led_present = true;

  kbd_token_bits is 0, but so is ret.
  kbd_init_info method is only returning != 0 if kbd_get_info is returning != 0

  (Basing on this: 
http://linux.dell.com/cgi-bin/cgit.cgi/libsmbios.git/tree/src/bin/smbios-keyboard-ctl#n667)
  kbd_get_info method returns only cbRES1 value of following smbios call :
  cbClass 4
  cbSelect 11
  cbArg1 0x0
  And it returns 0...
  I found that any cbRES of this call is giving me nothing but zeros, as if it 
wasn't defined in my BIOS. I have it's newest version for my laptop:
  [0.00] SMBIOS 2.7 present.
  [0.00] DMI: Dell Inc. Inspiron M5110/0X7W03, BIOS A05 03/22/2012

  However, if "cbRES3, byte2  Number of keyboard light brightness
  levels" is 0 as well, that should mean backlight is not available,
  right? I'm attaching possible fix.

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

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

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

Now we can confirm that USB_QUIRK_DELAY_INIT along can workaround this
issue, I'll send a patch to  Linux 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/1678477

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1710941] Re: Bluetooth stopped working after update

You can try previous kernel versions your system had prior to the problem, 
using this technique:
  https://wiki.ubuntu.com/RecoveryMode

No need to select "recovery mode" but other older kernel versions should
still be listed for you to use.

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

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

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

Title:
  Bluetooth stopped working after update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth connection to Bose Soundlink II have been fine for years.
  Applied a few new updates in the last day or two --- system was
  generally up to date, I don't often wait more than a week or so ---
  and now I can no longer connect.  Removed the device and re-paired
  just fine, although the speaker did not connect as it usually does
  after the pairing (i.e., it stayed in pairing mode).

  Messages in syslog:

  Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
  Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
  Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
  Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 15 20:34:34 2017
  InstallationDate: Installed on 2015-12-26 (597 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:6896 acl:46 sco:0 events:294 errors:0
TX bytes:4254 acl:32 sco:0 commands:156 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Kernel-packages] [Bug 1710941] Re: Bluetooth stopped working after update

If you're using 16.04 then there have been no high-level bluetooth-
related updates at all recently:

 bluez 5.37-0ubuntu5 ... 2016-03-09
 pulseaudio 1:8.0-0ubuntu3.3 ... 2017-06-30

So if your system was working for the previous month or more then the
problem is not caused by bluez or pulseaudio at least.

You might want to assign it to "linux (Ubuntu)" in case it was caused by
a recent kernel update like:

 linux 4.4.0-91.114 ... 2017-08-07

which sounds more likely by the date.

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

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

Title:
  Bluetooth stopped working after update

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Bluetooth connection to Bose Soundlink II have been fine for years.
  Applied a few new updates in the last day or two --- system was
  generally up to date, I don't often wait more than a week or so ---
  and now I can no longer connect.  Removed the device and re-paired
  just fine, although the speaker did not connect as it usually does
  after the pairing (i.e., it stayed in pairing mode).

  Messages in syslog:

  Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
  Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
  Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
  Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 15 20:34:34 2017
  InstallationDate: Installed on 2015-12-26 (597 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:6896 acl:46 sco:0 events:294 errors:0
TX bytes:4254 acl:32 sco:0 commands:156 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1711009

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

** Tags added: artful

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

Title:
  jfs filesystem is crashy, multiple panic and I/O errors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Loading initial ramdisk ...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.11.0-13-generic (buildd@bos01-ppc64el-022) 
(gcc version 6.4.0 20170724 (Ubuntu 6.4.0-2ubuntu1) ) #19-Ubuntu SMP Thu Aug 3 
15:11:49 UTC 2017 (Ubuntu 4.11.0-13.19-generic 4.11.12)
  Detected machine type: 0101
  command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic 
root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0762
alloc_top: 3000
alloc_top_hi : 00078000
rmo_top  : 3000
ram_top  : 00078000
  instantiating rtas at 0x2fff... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0763 -> 0x076309e6
  Device tree struct  0x0764 -> 0x0765
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0200 ...
   -> smp_release_cpus()
  spinning_secondaries = 7
   <- smp_release_cpus()
  Linux ppc64le

  
  Got multiple instances of panics, on artful:

  [   11.772333] ERROR: (device dm-3): dtSearch [jfs]: stack overrun!
  [   11.772333] 
  [   11.772384] bn = 0, index = 0
  [   11.772408] bn = 4307af, index = 0
  [   11.772432] bn = 0, index = 0
  [   11.772456] bn = 4307af, index = 0
  [   11.772493] bn = 0, index = 0
  [   11.772537] bn = 4307af, index = 0
  [   11.772573] bn = 0, index = 0
  [   11.772599] bn = c0077b994800, index = 0
  /sbin/init: error while loading shared libraries: liblz4.so.1: cannot open 
shared object file: Input/output error
  [   11.772964] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   11.772964] 
  [   11.773043] CPU: 2 PID: 1 Comm: init Not tainted 4.11.0-13-generic 
#19-Ubuntu
  [   11.773102] Call Trace:
  [   11.773167] [c0077e10bc30] [c0b831bc] dump_stack+0xb0/0xf0 
(unreliable)
  [   11.773243] [c0077e10bc70] [c0b7fbc8] panic+0x144/0x318
  [   11.773311] [c0077e10bd00] [c00ea5b8] do_exit+0xc98/0xca0
  [   11.773373] [c0077e10bdd0] [c00ea690] do_group_exit+0x60/0x100
  [   11.773424] [c0077e10be10] [c00ea754] SyS_exit_group+0x24/0x30
  [   11.773470] [c0077e10be30] [c000b184] system_call+0x38/0xe0
  [   11.775434] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   11.775434] 

  And also:

  [   12.338435] Unable to handle kernel paging request for data at address 
0x
  [   12.338754] Faulting instruction address: 0xd43be02c
  [   12.338951] Oops: Kernel access of bad area, sig: 11 [#1]
  [   12.338998] SMP NR_CPUS=2048 
  [   12.338999] NUMA 
  [   12.339053] pSeries
  [   12.339166] Modules linked in: ip_tables x_tables autofs4 jfs 
dm_service_time ibmveth ibmvscsi crc32c_vpmsum scsi_dh_emc scsi_dh_rdac 
scsi_dh_alua dm_multipath
  [   12.339305] CPU: 2 PID: 2135 Comm: tty Not tainted 4.11.0-13-generic 
#19-Ubuntu
  [   12.339441] task: c5562c00 task.stack: c6f78000
  [   12.339512] NIP: d43be02c LR: d43bdfbc CTR: 
c01458f0
  [   12.339614] REGS: c6f7b4b0 TRAP: 0300   Not tainted  
(4.11.0-13-generic)
  [   12.339707] MSR: 8280b033 
  [   12.339714]   CR: 44008244  XER: 
  [   12.339822] CFAR: 3fff9aa23f14 DAR:  DSISR: 4000 
SOFTE: 1 
  [   12.339822] GPR00: d43bdfbc c6f7b730 d43d8c90 
c00778e765f8 
  [   12.339822] GPR04: d43cf770 d43d2b58 05f1 
 
  [   12.339822] GPR08:  0038102d 0012 
d43ca6e0 
  [   12.339822] GPR12: c01458f0 cfb81200  
 
  [

[Kernel-packages] [Bug 1711009] [NEW] jfs filesystem is crashy, multiple panic and I/O errors

2017-08-15 Thread Mathieu Trudel-Lapierre

Public bug reported:

Loading initial ramdisk ...
OF stdout device is: /vdevice/vty@7100
Preparing to boot Linux version 4.11.0-13-generic (buildd@bos01-ppc64el-022) 
(gcc version 6.4.0 20170724 (Ubuntu 6.4.0-2ubuntu1) ) #19-Ubuntu SMP Thu Aug 3 
15:11:49 UTC 2017 (Ubuntu 4.11.0-13.19-generic 4.11.12)
Detected machine type: 0101
command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic 
root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
memory layout at init:
  memory_limit :  (16 MB aligned)
  alloc_bottom : 0762
  alloc_top: 3000
  alloc_top_hi : 00078000
  rmo_top  : 3000
  ram_top  : 00078000
instantiating rtas at 0x2fff... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0763 -> 0x076309e6
Device tree struct  0x0764 -> 0x0765
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0200 ...
 -> smp_release_cpus()
spinning_secondaries = 7
 <- smp_release_cpus()
Linux ppc64le


Got multiple instances of panics, on artful:

[   11.772333] ERROR: (device dm-3): dtSearch [jfs]: stack overrun!
[   11.772333] 
[   11.772384] bn = 0, index = 0
[   11.772408] bn = 4307af, index = 0
[   11.772432] bn = 0, index = 0
[   11.772456] bn = 4307af, index = 0
[   11.772493] bn = 0, index = 0
[   11.772537] bn = 4307af, index = 0
[   11.772573] bn = 0, index = 0
[   11.772599] bn = c0077b994800, index = 0
/sbin/init: error while loading shared libraries: liblz4.so.1: cannot open 
shared object file: Input/output error
[   11.772964] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
[   11.772964] 
[   11.773043] CPU: 2 PID: 1 Comm: init Not tainted 4.11.0-13-generic #19-Ubuntu
[   11.773102] Call Trace:
[   11.773167] [c0077e10bc30] [c0b831bc] dump_stack+0xb0/0xf0 
(unreliable)
[   11.773243] [c0077e10bc70] [c0b7fbc8] panic+0x144/0x318
[   11.773311] [c0077e10bd00] [c00ea5b8] do_exit+0xc98/0xca0
[   11.773373] [c0077e10bdd0] [c00ea690] do_group_exit+0x60/0x100
[   11.773424] [c0077e10be10] [c00ea754] SyS_exit_group+0x24/0x30
[   11.773470] [c0077e10be30] [c000b184] system_call+0x38/0xe0
[   11.775434] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
[   11.775434] 

And also:

[   12.338435] Unable to handle kernel paging request for data at address 
0x
[   12.338754] Faulting instruction address: 0xd43be02c
[   12.338951] Oops: Kernel access of bad area, sig: 11 [#1]
[   12.338998] SMP NR_CPUS=2048 
[   12.338999] NUMA 
[   12.339053] pSeries
[   12.339166] Modules linked in: ip_tables x_tables autofs4 jfs 
dm_service_time ibmveth ibmvscsi crc32c_vpmsum scsi_dh_emc scsi_dh_rdac 
scsi_dh_alua dm_multipath
[   12.339305] CPU: 2 PID: 2135 Comm: tty Not tainted 4.11.0-13-generic 
#19-Ubuntu
[   12.339441] task: c5562c00 task.stack: c6f78000
[   12.339512] NIP: d43be02c LR: d43bdfbc CTR: c01458f0
[   12.339614] REGS: c6f7b4b0 TRAP: 0300   Not tainted  
(4.11.0-13-generic)
[   12.339707] MSR: 8280b033 
[   12.339714]   CR: 44008244  XER: 
[   12.339822] CFAR: 3fff9aa23f14 DAR:  DSISR: 4000 
SOFTE: 1 
[   12.339822] GPR00: d43bdfbc c6f7b730 d43d8c90 
c00778e765f8 
[   12.339822] GPR04: d43cf770 d43d2b58 05f1 
 
[   12.339822] GPR08:  0038102d 0012 
d43ca6e0 
[   12.339822] GPR12: c01458f0 cfb81200  
 
[   12.339822] GPR16: c0077b8c81d8 c0077b8c80c8 c00778e91200 
c0077b8c8300 
[   12.339822] GPR20: c6f7ba30 c00778e911fe c00778c38800 
c6f7b950 
[   12.339822] GPR24: 0012 0012  
d43d2b38 
[   12.339822] GPR28: 1000 f1ddf440 c0076b096480 
c00778e765b8 
[   12.340436] NIP [d43be02c] __get_metapage+0x204/0x6b0 [jfs]
[   12.340541] LR [d43bdfbc] __get_metapage+0x194/0x6b0 [jfs]
[   12.340585] Call Trace:
[   12.340608] [c6f7b730] [d43bdf78] __get_metapage+0x150/0x6b0 
[jfs] (unreliable)
[   12.340671] [c6f7b810] [d43b9210] dtSearch+0x4d8/0xa20 [jfs]
[   12.340731] [c6f7b930] [d43a3a88] jfs_lookup+0x80/0x100 [jfs]
[   12.340789] [c6f7ba60] [c03683c0] lookup_slow+0xe0/0x240
[   12.340840] [c6f7bae0] [c036ccb8] walk_component+0x268/0x3f0
[   12.340896] [c6f7bb60] [c036d018] link_path_walk+0x1d8/0x5c0
[   12.340950]

[Kernel-packages] [Bug 1710601] Re: bluetoothctl fails to connect [USB 0930:0506 Toshiba Corp. Integrated Bluetooth]

** Summary changed:

- bluetoothctl fails to connect
+ bluetoothctl fails to connect [USB 0930:0506 Toshiba Corp. Integrated 
Bluetooth]

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

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

Title:
  bluetoothctl fails to connect [USB 0930:0506 Toshiba Corp. Integrated
  Bluetooth]

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth stopped working after some update, probably to bluez5
  before it was working flawlessly following 
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI
  now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well 
until I try to connect the device:
  [bluetooth]# connect A8:7E:33:FC:6D:15
  Attempting to connect to A8:7E:33:FC:6D:15
  [CHG] Device A8:7E:33:FC:6D:15 Connected: yes
  Failed to connect: org.bluez.Error.NotAvailable
  [CHG] Device A8:7E:33:FC:6D:15 Connected: no
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63

  I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to
  the day.

  I found errors in logs:
  aug 13 17:34:25 george bluetoothd[752]: Starting SDP server
  aug 13 17:34:26 george ModemManager[738]:   ModemManager (version 
1.4.12) starting in system bus...
  aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast
  aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized
  aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 
initialized
  aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.fre
  aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service 
Changed" characteristic
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be 
registered
  aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error 
(5)
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed.
  aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted 
(1)

  aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched 
rules; type="method_call", sender=":1.22" (uid=100
  aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; 
USER=root ; COMMAND=/usr/bin/bluetoothctl
  aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
  aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection...
  aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection.
  aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance.
  aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for 
user root
  aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 
192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz
  aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for 
user user by (uid=0)
  aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user.
  aug 13 17:47:44 george systemd[1]: Started Session 2 of user user.
  aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; 
USER=root ; COMMAND=/usr/bin/bluetoothctl
  aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
  aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to 
auto-refresh found
  aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary 
Directories...
  aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: 
No snaps to auto-refresh found
  aug 13 17:49:30 george systemd-tmpfiles[1459]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories.
  aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ;

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

Will sit, and think, and talk to you soon.

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  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.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

Post script: these warnings do not crash or otherwise interfere with
system operation.  ZoneMinder, in particular, `seems to function just
fine.

It's just...annoying and it seems the fix should be simple. Either this
chipset needs quirk, or not.

Does that sound crazy?

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  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.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

Thank you, Joseph!

I did test upstream at v4.13-rcr4 as you suggested. Same complaints. I
tried v4.13-rcr4 "lowlatency" as well, same complaints.

What seems strange to me is that I don't think I was getting these
complaints under 16.04 LTS Desktop with Studio (ie
lowlatency)/LAMP/ZoneMinder overlays. This same machine, same H/W, was
subject to intense scrutiny under 16.04 schema as described for at least
3 months after installing the NEC/Renasas 27xxx2 based Startech card.

Very hard to believe I didn't pull a DMESG in all that time.

But stranger things have happened.

Will try to follow on this report as suggested.

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  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:

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

Placeholder for attachment

** Attachment added: "dmesg.4.13.0rc4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4933122/+files/dmesg.4.13.0rc4

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  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.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

-- 
Mailing list:

[Kernel-packages] [Bug 1604900] Re: reboot instead of shutdown

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

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

** Changed in: ubuntu
   Status: Confirmed => Invalid

** Changed in: ubuntu-mate
   Status: Incomplete => Invalid

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

Title:
  reboot instead of shutdown

Status in ubuntu-mate:
  Invalid
Status in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu MATE is working good on my acer aspire v5-571 laptop but I
  cannot shutdown the system. After shutdown I always get a reboot after
  waiting 4 secs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1604900/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1689035

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

Title:
  Installation Error - Noveau - Last Kernel

Status in ubuntu-mate:
  Invalid
Status in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in nouveau-kernel-source package in Ubuntu:
  New

Bug description:
  Hi, pretty not sure this is the right area...but let's try

  On an Asus N552VW-FY059T the installation fails and i'm pretty sure its cause 
of the kernel...
  when i use an older version the installation and system work fine...but then 
start the upgrade and everything get fucked up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1689035/+subscriptions

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

[Kernel-packages] [Bug 1709296] Re: linux: 4.4.0-93.116 -proposed tracker

2017-08-15 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-93.116 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: 1709297
  derivatives: 1709298,1709299,1709300,1709301
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

2017-08-15 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.10.0-33.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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 Zesty:
  Confirmed

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

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

  backports: 1709304
  derivatives: 1709305
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1689035] Re: Installation Error - Noveau - Last Kernel

** Changed in: ubuntu-mate
   Status: New => Invalid

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

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  Installation Error - Noveau - Last Kernel

Status in ubuntu-mate:
  Invalid
Status in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New
Status in nouveau-kernel-source package in Ubuntu:
  New

Bug description:
  Hi, pretty not sure this is the right area...but let's try

  On an Asus N552VW-FY059T the installation fails and i'm pretty sure its cause 
of the kernel...
  when i use an older version the installation and system work fine...but then 
start the upgrade and everything get fucked up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1689035/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1694168

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

Title:
  logitech camera not working in 16.04.2 onwards

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed UM 16.04.2 last week and my logitech UVC Camera  wasn't
  being picked up and when I used cheese the camera option was greyed
  out as if the webcam was not present.

  I installed 16.10 and the same problem.

  I then installed UM 16.04.1 and the webcam is working again.

  So, I am guessing some change in UM from 16.04.2 onwards has caused
  the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1694168/+subscriptions

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

[Kernel-packages] [Bug 1694168] Re: logitech camera not working in UM 16.04.2 onwards

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

** Changed in: ubuntu-mate
   Status: New => Invalid

** Summary changed:

- logitech camera not working in UM 16.04.2 onwards
+ logitech camera not working in 16.04.2 onwards

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

Title:
  logitech camera not working in 16.04.2 onwards

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed UM 16.04.2 last week and my logitech UVC Camera  wasn't
  being picked up and when I used cheese the camera option was greyed
  out as if the webcam was not present.

  I installed 16.10 and the same problem.

  I then installed UM 16.04.1 and the webcam is working again.

  So, I am guessing some change in UM from 16.04.2 onwards has caused
  the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1694168/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1707416

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

** Tags added: xenial

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

Title:
  Wifi driver rtl8723be doesnt work on ubuntu 16.04 to 17.10

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of ubuntu doesnt let you connect to wifi with driver
  rtl8723be. you have to install from another newer source and the use
  echo "options rtl8723be ant_sel=2" | sudo tee -a
  /etc/modprobe.d/rtl8723be.conf for it to actually work. I attached the
  new wifi files that you use to make the driver work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1707416/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1695738

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

Title:
  Webcam isn't identified at system start

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using a Logitech C922 Webcam. It's always pluged in. At system
  start the webcam isn't identified. So i can not use it. I have to
  restart the computer or plug off and re-plugin the webcam. Then it
  works fine.

  The further problem is that i cannot set this webcam to system
  default.

  Ubuntu MATE 16.04
  MATE 1.12.1
  Logitech C922

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1695738/+subscriptions

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

[Kernel-packages] [Bug 1695738] Re: Webcam isn't identified at system start (Ubuntu MATE 16.04)

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

** Changed in: ubuntu-mate
   Status: New => Invalid

** Summary changed:

- Webcam isn't identified at system start (Ubuntu MATE 16.04)
+ Webcam isn't identified at system start

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

Title:
  Webcam isn't identified at system start

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using a Logitech C922 Webcam. It's always pluged in. At system
  start the webcam isn't identified. So i can not use it. I have to
  restart the computer or plug off and re-plugin the webcam. Then it
  works fine.

  The further problem is that i cannot set this webcam to system
  default.

  Ubuntu MATE 16.04
  MATE 1.12.1
  Logitech C922

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1695738/+subscriptions

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

2017-08-15 Thread Keary Parinis

apport information

** Description changed:

  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4
+ Architecture: amd64
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-01-18 (208 days ago)
+ InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_US
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags:  zesty
+ Uname: Linux 4.13.0-rc5-elan0602 x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1658345/+attachment/4933112/+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/1658345

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older

[Kernel-packages] [Bug 1658345] ProcCpuinfoMinimal.txt

2017-08-15 Thread Keary Parinis

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1658345/+attachment/4933113/+files/ProcCpuinfoMinimal.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/1658345

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (208 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-rc5-elan0602 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

2017-08-15 Thread Keary Parinis

No luck with touch screen. Same as before, the touchpad works but no
touchsreen. I posted apport info. Also got an error indicating headers
were missing b/c you only posted the single deb image. Not sure if that
has something to do with 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/1658345

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (208 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-rc5-elan0602 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04

2017-08-15 Thread fossfreedom

just wondering if this is a TLP / bluetooth interaction issue

Can you have a look here - http://linrunner.de/en/tlp/docs/tlp-
faq.html#btusb

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

Title:
  Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie
  17.04

Status in bluez package in Ubuntu:
  New

Bug description:
  It happens at every reset, after using bluetooth mouse for a few
  minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Aug  6 16:42:56 2017
  InstallationDate: Installed on 2017-08-05 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80E5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic 
root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN97WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: B4:6D:83:B1:A7:87  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:301634 acl:15117 sco:0 events:1578 errors:0
TX bytes:2425 acl:31 sco:0 commands:169 errors:0

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

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

[Kernel-packages] [Bug 1707416] Re: Wifi driver rtl8723be doesnt work on ubuntu 16.04 to 17.10

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  Wifi driver rtl8723be doesnt work on ubuntu 16.04 to 17.10

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  Fresh install of ubuntu doesnt let you connect to wifi with driver
  rtl8723be. you have to install from another newer source and the use
  echo "options rtl8723be ant_sel=2" | sudo tee -a
  /etc/modprobe.d/rtl8723be.conf for it to actually work. I attached the
  new wifi files that you use to make the driver work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1707416/+subscriptions

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

[Kernel-packages] [Bug 1710978] Re: bluetooth stack looses connection to bluetooth devices

2017-08-15 Thread fossfreedom

just wondering if this is a TLP / bluetooth interaction issue

Can you have a look here - http://linrunner.de/en/tlp/docs/tlp-
faq.html#btusb

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

Title:
  bluetooth stack looses connection to bluetooth devices

Status in bluez package in Ubuntu:
  New

Bug description:
  In Ubuntu Budgie bluetooth connection is lost in regular intervals
  (5mins).

  Thus my mouse stops working, my headset stops playing music.

  Reconnecting my mouse takes ages requiring a restart of bluez and
  reconnecting the mouse.

  This issue became worse ever since installing budgie (17.04) in May.

  (during writing this, the mouse stopped working again)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Aug 15 23:02:08 2017
  InstallationDate: Installed on 2017-05-25 (81 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:10:9F:D2:25:F8  ACL MTU: 1021:6  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0
TX bytes:14741 acl:474 sco:0 commands:583 errors:0

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

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

[Kernel-packages] [Bug 1707185] Re: I wish “Firmware Package” had the RTL8821AE wireless network adaptor driver.

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

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

** Changed in: ubuntu-mate
   Status: New => Invalid

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: linux-firmware-nonfree (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  I wish “Firmware Package” had the RTL8821AE wireless network adaptor
  driver.

Status in ubuntu-mate:
  Invalid
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-nonfree package in Ubuntu:
  New

Bug description:
  My Wife’s laptop is an Asus X555L, it has a RTL8821AE 802.11ac PCIe
  Wireless Network Adapter. When I first installed Ubuntu-Mate 16.04 for
  her, the Wireless Network adaptor driver was part of the Kernel. Her
  wireless connection reliability was terrible, continually dropping
  connection.   It also connects sometimes at really low data rate,
  sometimes as low as 6bits/s (my laptop always connects at min
  150Mb/s). She has been Ethernet cabled to my LAN Switch for the last 6
  months until I Googled for a driver and found a post pointing to a
  driver by Lwfinger on github. See:

  http://github.com/lwfinger/rtlwifi_new.git

  Please can the Mate “Firmware Package” include a driver for RTL8821AE
  wireless network adaptor. This would help all users with an Asus x555
  series Laptops.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1707185/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1708875

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

Title:
  mute microphone button not working

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I don't remember if that button ever worked in previous releases but
  on my X230 pressing this button doesn't mute the microphone.

  Anyone else with the same problem?

  Attached the button I am referring to.

  To the contrary, the button to mute the audio works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1708875/+subscriptions

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

[Kernel-packages] [Bug 1708875] Re: 17.10 Alpha 2: mute microphone button not working

I can't reproduce this on my hardware. I believe Thinkpad require some
tuning.

** Changed in: ubuntu-mate
   Status: New => Incomplete

** Summary changed:

- 17.10 Alpha 2: mute microphone button not working
+ mute microphone button not working

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

** Changed in: ubuntu-mate
   Status: Incomplete => Invalid

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

Title:
  mute microphone button not working

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I don't remember if that button ever worked in previous releases but
  on my X230 pressing this button doesn't mute the microphone.

  Anyone else with the same problem?

  Attached the button I am referring to.

  To the contrary, the button to mute the audio works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1708875/+subscriptions

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

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu > 1500 by themselves

2017-08-15 Thread engin

64bit xenial, same issue here;

it's sad, not able to use jumbo frames with in lxd guests.

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

Title:
  bridges cannot have a mtu > 1500 by themselves

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500
  3) ip link show dev br-test0 # confirm MTU

  Here, 2) returns "RTNETLINK answers: Invalid argument". One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
    Installed: 3.13.0-41.70
    Candidate: 3.13.0-41.70
    Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
    Installed: 3.12.0-2
    Candidate: 3.12.0-2
    Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

2017-08-15 Thread Michael Stucki

@negge The fix for Ubuntu 16.04 (linux-generic-hwe-16.04) has been
merged and will be part of the next update (4.10.0-33.37).

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe source package in Zesty:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 
00016942 CR4: 003406f0
  Apr  7 11:20:28 doe

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

2017-08-15 Thread Michael Stucki

see also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616

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

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

Status in linux package in Ubuntu:
  Invalid

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

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

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

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

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

[Kernel-packages] [Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3

2017-08-15 Thread Adam Smith

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

** This bug has been marked a duplicate of bug 1652270
   Could not boot into RPi3 with kernel 4.4.0-1038-raspi2

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

Title:
  Recent updates broke Ubuntu on Raspberry Pi 3

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've been running Raspberry Pi 3 with Ubuntu as described here 
https://wiki.ubuntu.com/ARM/RaspberryPi

  I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been
  using this setup successfully since October up until last week.
  Unfortunately one of the latest kernel updates broke the installation
  and I found out the same happened for Ubuntu 16.04 LTS - and therefore
  I can no longer run up-to-date Ubuntu installation (with updated
  kernel) on my RPI.

  I am getting this error:
  Error image is not a fdt - must reset the board to recover

  I also tried this but it didn't help me:
  https://www.raspberrypi.org/forums/viewtopic.php?f=28=168838

  Now I know running Ubuntu on RPI3 this way is not officially
  supported, but since Ubuntu Snappy is supported I thought someone here
  could know what is going on.

  Thank you very much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions

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

[Kernel-packages] [Bug 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.

2017-08-15 Thread Steve Langasek

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

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

Title:
  Livepatch motd enhancement to show people how livepatch can help
  protect systems.

Status in linux package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  New

Bug description:
  This is a request to add an enhancement in our motd.d to inform users
  of the following:

  1) that livepatch is available for their platform/kernel if they don't
  have it set up and installed right now.

  2) When a system is protected by livepatch, and the system is
  currently patched (i.e., canonical-livepatch has active patches
  applied).

  3) when a system is protected by livepatch and no livepatches exist
  yet for the kernel version, a single line message of 'This system is
  protected by canonical-livepatch." or similar.

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

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

[Kernel-packages] [Bug 1710985] Re: BUG: unable to handle kernel paging request at ffffffffc05441d7

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

Title:
  BUG: unable to handle kernel paging request at c05441d7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occurs randomly, usually recovering from sleep, although sometimes
  after boot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1536 F pulseaudio
  Date: Tue Aug 15 11:45:23 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:report_bug+0x94/0x120
  Failure: oops
  MachineType: Sony Corporation VGN-FZ140E
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=068b20f7-3833-4ca4-9b9b-580786fff4a8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at c05441d7
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0050J7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0050J7:bd04/18/2007:svnSonyCorporation:pnVGN-FZ140E:pvrC3LPLMJ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-FZ140E
  dmi.product.version: C3LPLMJ8
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1710985] Re: BUG: unable to handle kernel paging request at ffffffffc05441d7

2017-08-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel paging request at c05441d7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occurs randomly, usually recovering from sleep, although sometimes
  after boot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1536 F pulseaudio
  Date: Tue Aug 15 11:45:23 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:report_bug+0x94/0x120
  Failure: oops
  MachineType: Sony Corporation VGN-FZ140E
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=068b20f7-3833-4ca4-9b9b-580786fff4a8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at c05441d7
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0050J7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0050J7:bd04/18/2007:svnSonyCorporation:pnVGN-FZ140E:pvrC3LPLMJ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-FZ140E
  dmi.product.version: C3LPLMJ8
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1710985] Status changed to Confirmed

This change was made by a bot.

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

Title:
  BUG: unable to handle kernel paging request at c05441d7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occurs randomly, usually recovering from sleep, although sometimes
  after boot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1536 F pulseaudio
  Date: Tue Aug 15 11:45:23 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:report_bug+0x94/0x120
  Failure: oops
  MachineType: Sony Corporation VGN-FZ140E
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=068b20f7-3833-4ca4-9b9b-580786fff4a8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at c05441d7
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0050J7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0050J7:bd04/18/2007:svnSonyCorporation:pnVGN-FZ140E:pvrC3LPLMJ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-FZ140E
  dmi.product.version: C3LPLMJ8
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1710985] [NEW] BUG: unable to handle kernel paging request at ffffffffc05441d7

2017-08-15 Thread grenouille

Public bug reported:

Occurs randomly, usually recovering from sleep, although sometimes after
boot.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-11-generic 4.12.0-11.12
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mike   1536 F pulseaudio
Date: Tue Aug 15 11:45:23 2017
DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:report_bug+0x94/0x120
Failure: oops
MachineType: Sony Corporation VGN-FZ140E
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=068b20f7-3833-4ca4-9b9b-580786fff4a8 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at c05441d7
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0050J7
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0050J7:bd04/18/2007:svnSonyCorporation:pnVGN-FZ140E:pvrC3LPLMJ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: N/A
dmi.product.name: VGN-FZ140E
dmi.product.version: C3LPLMJ8
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-kerneloops artful kernel-oops package-from-proposed

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

Title:
  BUG: unable to handle kernel paging request at c05441d7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occurs randomly, usually recovering from sleep, although sometimes
  after boot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1536 F pulseaudio
  Date: Tue Aug 15 11:45:23 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:report_bug+0x94/0x120
  Failure: oops
  MachineType: Sony Corporation VGN-FZ140E
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=068b20f7-3833-4ca4-9b9b-580786fff4a8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at c05441d7
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0050J7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0050J7:bd04/18/2007:svnSonyCorporation:pnVGN-FZ140E:pvrC3LPLMJ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-FZ140E
  dmi.product.version: C3LPLMJ8
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1709296] Re: linux: 4.4.0-93.116 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1709297
  derivatives: 1709298,1709299,1709300,1709301
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Tuesday, 15. August 2017 21:02 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1709297
  derivatives: 1709298,1709299,1709300,1709301
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Tuesday, 15. August 2017 21:02 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-93.116 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Confirmed
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  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: 1709297
  derivatives: 1709298,1709299,1709300,1709301
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1709304
  derivatives: 1709305
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 11. August 2017 11:32 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Tuesday, 15. August 2017 21:04 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1709304
  derivatives: 1709305
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Tuesday, 15. August 2017 21:04 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.10.0-33.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Confirmed
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 Zesty:
  Confirmed

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

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

  backports: 1709304
  derivatives: 1709305
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1710978] [NEW] bluetooth stack looses connection to bluetooth devices

2017-08-15 Thread Wolf Rogner

Public bug reported:

In Ubuntu Budgie bluetooth connection is lost in regular intervals
(5mins).

Thus my mouse stops working, my headset stops playing music.

Reconnecting my mouse takes ages requiring a restart of bluez and
reconnecting the mouse.

This issue became worse ever since installing budgie (17.04) in May.

(during writing this, the mouse stopped working again)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: bluez 5.43-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Tue Aug 15 23:02:08 2017
InstallationDate: Installed on 2017-05-25 (81 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 14:10:9F:D2:25:F8  ACL MTU: 1021:6  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0
TX bytes:14741 acl:474 sco:0 commands:583 errors:0

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


** Tags: amd64 apport-bug zesty

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

Title:
  bluetooth stack looses connection to bluetooth devices

Status in bluez package in Ubuntu:
  New

Bug description:
  In Ubuntu Budgie bluetooth connection is lost in regular intervals
  (5mins).

  Thus my mouse stops working, my headset stops playing music.

  Reconnecting my mouse takes ages requiring a restart of bluez and
  reconnecting the mouse.

  This issue became worse ever since installing budgie (17.04) in May.

  (during writing this, the mouse stopped working again)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Aug 15 23:02:08 2017
  InstallationDate: Installed on 2017-05-25 (81 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:10:9F:D2:25:F8  ACL MTU: 1021:6  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0
TX bytes:14741 acl:474 sco:0 commands:583 errors:0

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1710976

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

Title:
  Livepatch motd enhancement to show people how livepatch can help
  protect systems.

Status in linux package in Ubuntu:
  Incomplete
Status in update-notifier package in Ubuntu:
  New

Bug description:
  This is a request to add an enhancement in our motd.d to inform users
  of the following:

  1) that livepatch is available for their platform/kernel if they don't
  have it set up and installed right now.

  2) When a system is protected by livepatch, and the system is
  currently patched (i.e., canonical-livepatch has active patches
  applied).

  3) when a system is protected by livepatch and no livepatches exist
  yet for the kernel version, a single line message of 'This system is
  protected by canonical-livepatch." or similar.

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

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

[Kernel-packages] [Bug 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.

2017-08-15 Thread David Britton

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

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

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

Title:
  Livepatch motd enhancement to show people how livepatch can help
  protect systems.

Status in linux package in Ubuntu:
  Incomplete
Status in update-notifier package in Ubuntu:
  New

Bug description:
  This is a request to add an enhancement in our motd.d to inform users
  of the following:

  1) that livepatch is available for their platform/kernel if they don't
  have it set up and installed right now.

  2) When a system is protected by livepatch, and the system is
  currently patched (i.e., canonical-livepatch has active patches
  applied).

  3) when a system is protected by livepatch and no livepatches exist
  yet for the kernel version, a single line message of 'This system is
  protected by canonical-livepatch." or similar.

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

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

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

2017-08-15 Thread bugproxy

--- Comment From dougm...@us.ibm.com 2017-08-15 16:36 EDT---
I will start a test with that kernel tomorrow. I will be adding my debug code 
to it, so that I can track delayed I/Os if they occur. I see you posted source 
code, so I can do that easily.

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may

[Kernel-packages] [Bug 1710967] [NEW] Following kernel upgrades, the bcmwl kernel module requires re-installation.

2017-08-15 Thread Jon "The Nice Guy" Spriggs

Public bug reported:

I have recently noticed that when I perform `sudo apt update && sudo apt
dist-upgrade -y` I'm having to separately run `sudo apt-get install
--reinstall bcmwl-kernel-source` because otherwise the module isn't
loading, and I have no wifi connections.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Aug 15 21:11:40 2017
InstallationDate: Installed on 2017-04-06 (131 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Following kernel upgrades, the bcmwl kernel module requires re-
  installation.

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I have recently noticed that when I perform `sudo apt update && sudo
  apt dist-upgrade -y` I'm having to separately run `sudo apt-get
  install --reinstall bcmwl-kernel-source` because otherwise the module
  isn't loading, and I have no wifi connections.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Aug 15 21:11:40 2017
  InstallationDate: Installed on 2017-04-06 (131 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1709616] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (5th Gen., 2017)

2017-08-15 Thread Michael Stucki

Two things:

- Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug 
happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th 
Gen.
- The bug was fixed in kernel 4.13 but not in 4.10. This means that users who 
run the HWE kernel on Ubuntu 16.04 LTS will have this problem too!

I can reproduce it on my local system which has "linux-image-generic-
hwe-16.04" installed (4.10.0.32.34).

Reading through the comments, it's not exactly clear to me which of the
commits has fixed this problem, but I guess that the following two
changes have made the difference:

https://patchwork.kernel.org/patch/9835823/
https://patchwork.kernel.org/patch/9835825/

So, will this bug be reopened or should I create a separate issue for
the 16.04 HWE kernel?

** Bug watch added: Linux Kernel Bug Tracker #191181
   https://bugzilla.kernel.org/show_bug.cgi?id=191181

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

Title:
  CPU fan goes full throttle triggered by waking up from suspend on
  Lenovo X1 Carbon (5th Gen., 2017)

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

Bug description:
  Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU
  running Ubuntu 17.04 has its fan go full steam if the laptop is woken
  up from sleep/suspend. Without any sleep/suspend the laptop's fan is
  basically "off" or silent, even for hours.

  The bug has been fixed upstream, see

  6625914 ACPI / EC: Drop EC noirq hooks to fix a regression
  9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

  and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129
  (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181)

  and I hope this fix will make its way into a near-future kernel update
  to ubuntu :)

  Many thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  micha  1783 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Aug  9 12:55:20 2017
  HibernationDevice: RESUME=UUID=d258b78e-8853-44ea-adac-c2c837859e92
  InstallationDate: Installed on 2017-06-25 (44 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
   Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HQS03P00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HQS03P00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HQS03P00:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HQS03P00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HQS03P00
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset

It's included in 1.157.12, which was uploaded last week but is currently
sitting in the unapproved queue.

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

Title:
  Add firmware for Redpine 9113 chipset

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The redpine driver in xenial has been updated, and a
  corresponding firmware update is also required.

  Fix: Add new firmware files.

  Test case: Test with affected hw and with a kernel which has the
  driver update.

  Regression potential: These are new files used by a single driver, so
  no regressions are possible outside of that driver.

  ---

  Latest firmware images provided by Redpine in 1.2 production release
  are updated to ubuntu's linux-firmware.git

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

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

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

2017-08-15 Thread Colin Ian King

I've rolled three patches into a test kernel to test. I believe the best
fix is probably "cfq: Disable writeback throttling by default"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=142bbdfccc8b3e9f7342f2ce8422e76a3b45beae

The commits are:
4d608baac5f4e72b033a122b2d6d9499532c3afc "block: Initialize cfqq->ioprio_class
in cfq_get_queue()"
142bbdfccc8b3e9f7342f2ce8422e76a3b45beae "cfq: Disable writeback throttling by
default"
5be6b75610cefd1e21b98a218211922c2feb6e08 "cfq-iosched: fix the delay of
cfq_group's vdisktime under
iops mode"

You can download the packages from:
http://kernel.ubuntu.com/~cking/lp1709889/

Let me know if this helps with the issue.

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

Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.

Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress

Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.

---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.

---uname output---
4.10.0-11-generic

The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:

root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#

So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.

This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.

Tests are running again, will see what happens next.

Update from JIRA:

I have run some more experiments. Not sure what it tells us, but
here's what I've seen.

First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.

I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.

So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.

Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.

Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.

Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:

1. apt install make gcc g++ git

[Kernel-packages] [Bug 1709929] Re: linux: 4.12.0-11.12 -proposed tracker

** Changed in: kernel-development-workflow/automated-testing
   Status: Incomplete => Fix Released

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

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.12.0-11.12 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1710947] Re: MacBookPro11, 4 patch no longer needed in 4.12.4+

2017-08-15 Thread Joe Barnett

Logs not relevant, but I have confirmed that suspend works with a
mainline kernel build that includes the new patch

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

Title:
  MacBookPro11,4 patch no longer needed in 4.12.4+

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The patch applied in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no
  longer needed in artful kernels 4.12.0-11.12 and above, as a fix has
  made it in upstream 4.12.4+ and 4.13rc1+ kernels.

  The new fix is in arch/x86/pci/fixup.c, while the applied patch was in
  drivers/pci/quirks.c, so the conflict between the two may not be
  apparent using automatic merge tools.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1710947

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

Title:
  MacBookPro11,4 patch no longer needed in 4.12.4+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The patch applied in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no
  longer needed in artful kernels 4.12.0-11.12 and above, as a fix has
  made it in upstream 4.12.4+ and 4.13rc1+ kernels.

  The new fix is in arch/x86/pci/fixup.c, while the applied patch was in
  drivers/pci/quirks.c, so the conflict between the two may not be
  apparent using automatic merge tools.

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

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

[Kernel-packages] [Bug 1710947] [NEW] MacBookPro11, 4 patch no longer needed in 4.12.4+

2017-08-15 Thread Joe Barnett

Public bug reported:

The patch applied in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no
longer needed in artful kernels 4.12.0-11.12 and above, as a fix has
made it in upstream 4.12.4+ and 4.13rc1+ kernels.

The new fix is in arch/x86/pci/fixup.c, while the applied patch was in
drivers/pci/quirks.c, so the conflict between the two may not be
apparent using automatic merge tools.

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

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

Title:
  MacBookPro11,4 patch no longer needed in 4.12.4+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The patch applied in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no
  longer needed in artful kernels 4.12.0-11.12 and above, as a fix has
  made it in upstream 4.12.4+ and 4.13rc1+ kernels.

  The new fix is in arch/x86/pci/fixup.c, while the applied patch was in
  drivers/pci/quirks.c, so the conflict between the two may not be
  apparent using automatic merge tools.

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

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

[Kernel-packages] [Bug 1710941] [NEW] Bluetooth stopped working after update

2017-08-15 Thread Doug Morse

Public bug reported:

Bluetooth connection to Bose Soundlink II have been fine for years.
Applied a few new updates in the last day or two --- system was
generally up to date, I don't often wait more than a week or so --- and
now I can no longer connect.  Removed the device and re-paired just
fine, although the speaker did not connect as it usually does after the
pairing (i.e., it stayed in pairing mode).

Messages in syslog:

Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
Uname: Linux 4.4.0-91-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 15 20:34:34 2017
InstallationDate: Installed on 2015-12-26 (597 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterestingModules: rfcomm bnep btusb bluetooth
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
dmi.board.name: NUC5i5RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H40999-504
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:6896 acl:46 sco:0 events:294 errors:0
TX bytes:4254 acl:32 sco:0 commands:156 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bluetooth stopped working after update

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth connection to Bose Soundlink II have been fine for years.
  Applied a few new updates in the last day or two --- system was
  generally up to date, I don't often wait more than a week or so ---
  and now I can no longer connect.  Removed the device and re-paired
  just fine, although the speaker did not connect as it usually does
  after the pairing (i.e., it stayed in pairing mode).

  Messages in syslog:

  Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when 
attempting to remove it
  Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when 
attempting to remove it
  Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111)
  Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112)
  Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when 
attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 15 20:34:34 2017
  InstallationDate: Installed on 2015-12-26 (597 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias:

[Kernel-packages] [Bug 1710922] Re: Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream

2017-08-15 Thread Andrew Cloke

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

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a
  "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with
  QEMU upstream

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

Bug description:
  == Comment: #0 - Daniel Henrique Barboza  - 2017-08-08 
09:13:31 ==
  - Host information: Ubuntu 16.10 running upstream QEMU

  $ uname -a
  Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  $ cat /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)
  (...)
  timebase  : 51200
  platform  : PowerNV
  model : 8247-42L
  machine   : PowerNV 8247-42L
  firmware  : OPAL

  
  - qemu command line that launched the Ubuntu 17.10 ppc64el guest:

  sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable-
  kvm -device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-
  vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1
  --machine pseries,accel=kvm,usb=off,dump-guest-core=off -m
  4G,slots=32,maxmem=32G -drive
  file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id
  =drive-virtio-disk0,cache=none -device virtio-blk-
  pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-
  disk0,bootindex=1 -nographic

  
  - guest information: Ubuntu 17.10 ppc64el:

  root@ubuntu1710:~# uname -a
  Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
  root@ubuntu1710:~# 

  
  - Problem: hotplugging a LMB generates a guest kernel Oops:

  root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information
  (qemu) 
  (qemu) object_add memory-backend-ram,id=ram1,size=1G
  (qemu) device_add pc-dimm,id=dimm1,memdev=ram1
  (qemu) [  126.850952] kernel BUG at 
/build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185!
  [  126.851285] Oops: Exception in kernel mode, sig: 5 [#1]
  [  126.851428] SMP NR_CPUS=2048 
  [  126.851428] NUMA 
  [  126.851546] pSeries
  [  126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm 
ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi 
crc32c_vpmsum virtio_blk
  [  126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic 
#15-Ubuntu
  [  126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn
  [  126.852828] task: c000fea8 task.stack: c000fe118000
  [  126.853000] NIP: c0350268 LR: c03501e0 CTR: 

  [  126.853190] REGS: c000fe11b780 TRAP: 0700   Not tainted  
(4.11.0-10-generic)
  [  126.853390] MSR: 8282b033 
  [  126.853396]   CR: 42002422  XER: 2000
  [  126.853672] CFAR: c03501e4 SOFTE: 1 
  [  126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00 
0001 
  [  126.853672] GPR04: c000f9901480 c000ffe21c00 003e 
0003 
  [  126.853672] GPR08: 0002 0003 0003 
303078302d303030 
  [  126.853672] GPR12: 2200 cfb8 c0110008 
c000fe1810c0 
  [  126.853672] GPR16: c000fe050ea8 0010 c000fc30 
c000fea0 
  [  126.853672] GPR20: c000f951a1a4 0004 0001 
0010 
  [  126.853672] GPR24: 0001 c000f951a1a0 0004 
 
  [  126.853672] GPR28:  0001 1000 
00014000 
  [  126.855221] NIP [c0350268] remove_memory+0xf8/0x100
  [  126.855338] LR [c03501e0] remove_memory+0x70/0x100
  [  126.855453] Call Trace:
  [  126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100 
(unreliable)
  [  126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0
  [  126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20
  [  126.855959] [c000fe11bbf0] [c00a9af8] 
handle_dlpar_errorlog+0xa8/0x170
  [  126.856118] [c000fe11bc60] [c00a9c54] 
pseries_hp_work_fn+0x94/0xa0
  [  126.856275] [c000fe11bc90] [c01071d0] 
process_one_work+0x2b0/0x5a0
  [  126.856430] [c000fe11bd20]

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

2017-08-15 Thread Kamal Mostafa

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

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

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1709296] Re: linux: 4.4.0-93.116 -proposed tracker

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

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

Title:
  linux: 4.4.0-93.116 -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:
  Fix Committed
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  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: 1709297
  derivatives: 1709298,1709299,1709300,1709301
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1645951] Re: [Feature] GLK:New device IDs

2017-08-15 Thread Leann Ogasawara

Moving this to Fix Committed for artful since we have a 4.12 kernel
available in artful-proposed.

f80e78aa11ad754de20104233af1ce4cea8f16a5 mfd: intel-lpss: Add Intel Gemini Lake 
PCI IDs
v4.11-rc1~105^2~16

8f8983a5683623b62b339d159573f95a1fce44f3 usb: dwc3: pci: add Intel Gemini Lake 
PCI ID
v4.10-rc3~1^2~21^2~3

a6450cb0388ee58659be5a54a7bfe5bff09532c7 mfd: lpc_ich: Add support for Intel 
Gemini Lake SoC
v4.12-rc1~113^2~10

ae2520540cb0090eb8cdba559bcb6a82266f0308 pwm: lpss: Add Intel Gemini Lake PCI ID
v4.11-rc1~40^2^2~9

9827f9eb79c56424eac6409197a290601cf78eee i2c: i801: Add support for Intel 
Gemini Lake
v4.11-rc1~72^2~10

e18a80acd1365e91e3efcd69942d9073936cf851 spi: pxa2xx: Add support for Intel 
Gemini Lake
v4.11-rc1~153^2~7^2

6693f9f96a0936488dd7876b8079933786e27b1b pinctrl: intel: Add Intel Gemini Lake 
pin controller support
v4.11-rc1~133^2~17

2d1956d0a4e0fd586e1c72c642929e15b5f23226 mmc: sdhci-pci: Add support for Intel 
GLK
v4.10-rc1~127^2~59

340837f985c2cb87ca0868d4aa9ce42b0fab3a21 intel_th: pci: Add Gemini Lake support
v4.11-rc4~1^2~13^2


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

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

** Changed in: intel
   Status: New => Fix Committed

** Changed in: intel
   Importance: Undecided => High

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

Title:
  [Feature] GLK:New device IDs

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

Bug description:
  Placeholder for GLK(Gemini Lake) IDs that should be published.

  
https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?id=9d887e444fa59198e6c5b54d253e8f63fe08a808
  commit f80e78aa11ad ("mfd: intel-lpss: Add Intel Gemini Lake PCI IDs")

  USB device/xDCI: 0x31aa v4.10 8f8983a5683623b62b339d159573f95a1fce44f3

  SPI-NOR: (0x3196) enumerated from LPC device | v4.12
  |a6450cb0388ee58659be5a54a7bfe5bff09532c7  |

  LPC: 0x3197 | v4.12 | a6450cb0388ee58659be5a54a7bfe5bff09532c7 |

  PWM: 0x31c8 v4.11-rc1 ae2520540cb0090eb8cdba559bcb6a82266f0308

  SMBus: 0x31d4 v4.11-rc1 9827f9eb79c56424eac6409197a290601cf78eee

  I2C: 0x31ac 0x31ae 0x31b0 0x31b2 0x31b4 0x31b6 0x31b8 0x31ba v4.11-rc1
  f80e78aa11ad

  HS-UART: 0x31bc 0x31be 0x31c0 0x31ee v4.11-rc1 f80e78aa11ad

  SPI: 0x31c2 0x31c4 0x31c6 v4.11-rc1 f80e78aa11ad, e18a80acd136

  GPIO: INT3453 v4.11-rc1 6693f9f96a0936488dd7876b8079933786e27b1b

  SD Card: 0x31ca v4.10 2d1956d0a4e0fd586e1c72c642929e15b5f23226

  eMMC: 0x31cc v4.10 2d1956d0a4e0fd586e1c72c642929e15b5f23226

  SDIO: 0x31d0 v4.10 2d1956d0a4e0fd586e1c72c642929e15b5f23226

  NPK: 0x318e v4.11-rc4 340837f985

  HW:
  Gemini Lake

  Removed: Not POR
  UFS: 0x31ce

  Upstream Schedule:
  kernel: 4.13

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

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

[Kernel-packages] [Bug 1685707] Re: [Feature] CNL:UFS 2.0

2017-08-15 Thread Leann Ogasawara

Thanks, moving this to In Progress since we are currently working on the
4.13 rebase for Artful (17.10).

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

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

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

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

Title:
  [Feature] CNL:UFS 2.0

Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  UFS 2.0 - Universal Flash Storage.
  The Universal Flash System (UFS) is the next generation storage standard that 
is to replace eMMC. UFS includes the feature set of eMMC as a subset and 
defines a unique feature set that provides low power consumption, high data 
throughput, low electromagnetic interference and optimization for mass memory 
subsystem efficiency. UFS adopts the latest technology from other industrial 
standards.
  UFS 1 and UFS 1.1 are already supported in upstream kernel.
  Add the delta features between 1.1 and 2.0.

  
  Target Kernel:4.13

  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

2017-08-15 Thread Kamal Mostafa

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

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

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

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

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

Title:
  linux: 4.10.0-33.37 -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:
  Fix Committed
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 Zesty:
  Confirmed

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

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

  backports: 1709304
  derivatives: 1709305
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 11. August 2017 11:32 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

2017-08-15 Thread Kamal Mostafa

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

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

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

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

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1709296] Re: linux: 4.4.0-93.116 -proposed tracker

2017-08-15 Thread Andy Whitcroft

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

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

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

Title:
  linux: 4.4.0-93.116 -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:
  In Progress
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  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: 1709297
  derivatives: 1709298,1709299,1709300,1709301
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1627828] Re: iwl3945 crashes randomly

2017-08-15 Thread Sebastian Muniz

It looks like it is indeed a power management issue. Last threee days I made 
and manually run this script when I login;
seba@D630:~$ cat $HOME/bin/iwl_power_save.sh 
sudo iw dev wlp12s0 get power_save
sudo iw dev wlp12s0 set power_save off
sudo iw dev wlp12s0 get power_save

and I haven't had any issue.
Everytime I boot power management is on and I switch it off.
I will report in a week. Maybe I will also switch back to the HWE kernel to 
make sure this is reproducible with the ubuntu kernel.

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

Title:
  iwl3945 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Out of nothing a once properly working 
  0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  started to crash with:
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320032] iwl3945 
:0c:00.0: Error sending C_POWER_TBL: time out after 500ms.
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320039] iwl3945 
:0c:00.0: set power fail, ret = -110
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012031] iwl3945 
:0c:00.0: Queue 2 stuck for 2500 ms.
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012039] iwl3945 
:0c:00.0: On demand firmware reload
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.050333] ieee80211 phy0: 
Hardware restart was requested
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.084769] retire_capture_urb: 
33 callbacks suppressed
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098359] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098364] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145087] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145089] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191802] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191805] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238526] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238528] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285272] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285275] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.322030] iwl3945 
:0c:00.0: Unable to initialize device after 5 attempts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seba   1421 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 26 16:38:18 2016
  HibernationDevice: RESUME=UUID=64d7608d-53a8-46a6-884c-0ccf1814fb03
  InstallationDate: Installed on 2016-08-28 (29 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude D630
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=dce979b5-6a44-48cf-a87a-d314263a895c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1700941] Re: Redpine vendor driver - Switching to AP mode causes kernel panic

2017-08-15 Thread Shrirang Bagul

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

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

Title:
  Redpine vendor driver - Switching to AP mode causes kernel panic

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

Bug description:
  Switching from STA to AP mode on RS9113 Redpine Wifi-BT combo device,
  system reports a kernel panic.

  The Redpine driver (ver. 1.2 RC12) doesn't track the Linux 4.4.69 stable 
release
  which introduced following patches to mac80211 subsystem:
  - mac80211: pass RX aggregation window size to driver
  - mac80211: pass block ack session timeout to to driver
  - mac80211: RX BA support for sta max_rx_aggregation_subframes

  The Redpine driver ver. 1.2RC12 needs to be updated to handle the changes 
introduced
  in the patch:
  - mac80211: pass block ack session timeout to to driver
  (more details here: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=U
  buntu-4.4.0-82.105=0b2141bd007213cc9c4228786f773a3c35c41c56 and 
https://bugs.launc
  hpad.net/bugs/1692900)

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

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

[Kernel-packages] [Bug 1710922] [NEW] Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream

2017-08-15 Thread bugproxy

Public bug reported:

== Comment: #0 - Daniel Henrique Barboza  - 2017-08-08 
09:13:31 ==
- Host information: Ubuntu 16.10 running upstream QEMU

$ uname -a
Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

$ cat /proc/cpuinfo
processor   : 0
cpu : POWER8E (raw), altivec supported
clock   : 2061.00MHz
revision: 2.1 (pvr 004b 0201)
(...)
timebase: 51200
platform: PowerNV
model   : 8247-42L
machine : PowerNV 8247-42L
firmware: OPAL


- qemu command line that launched the Ubuntu 17.10 ppc64el guest:

sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable-kvm
-device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-
vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1
--machine pseries,accel=kvm,usb=off,dump-guest-core=off -m
4G,slots=32,maxmem=32G -drive
file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id=drive-
virtio-disk0,cache=none -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -nographic


- guest information: Ubuntu 17.10 ppc64el:

root@ubuntu1710:~# uname -a
Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu1710:~# 


- Problem: hotplugging a LMB generates a guest kernel Oops:

root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information
(qemu) 
(qemu) object_add memory-backend-ram,id=ram1,size=1G
(qemu) device_add pc-dimm,id=dimm1,memdev=ram1
(qemu) [  126.850952] kernel BUG at 
/build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185!
[  126.851285] Oops: Exception in kernel mode, sig: 5 [#1]
[  126.851428] SMP NR_CPUS=2048 
[  126.851428] NUMA 
[  126.851546] pSeries
[  126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm 
ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi 
crc32c_vpmsum virtio_blk
[  126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic 
#15-Ubuntu
[  126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn
[  126.852828] task: c000fea8 task.stack: c000fe118000
[  126.853000] NIP: c0350268 LR: c03501e0 CTR: 
[  126.853190] REGS: c000fe11b780 TRAP: 0700   Not tainted  
(4.11.0-10-generic)
[  126.853390] MSR: 8282b033 
[  126.853396]   CR: 42002422  XER: 2000
[  126.853672] CFAR: c03501e4 SOFTE: 1 
[  126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00 
0001 
[  126.853672] GPR04: c000f9901480 c000ffe21c00 003e 
0003 
[  126.853672] GPR08: 0002 0003 0003 
303078302d303030 
[  126.853672] GPR12: 2200 cfb8 c0110008 
c000fe1810c0 
[  126.853672] GPR16: c000fe050ea8 0010 c000fc30 
c000fea0 
[  126.853672] GPR20: c000f951a1a4 0004 0001 
0010 
[  126.853672] GPR24: 0001 c000f951a1a0 0004 
 
[  126.853672] GPR28:  0001 1000 
00014000 
[  126.855221] NIP [c0350268] remove_memory+0xf8/0x100
[  126.855338] LR [c03501e0] remove_memory+0x70/0x100
[  126.855453] Call Trace:
[  126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100 
(unreliable)
[  126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0
[  126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20
[  126.855959] [c000fe11bbf0] [c00a9af8] 
handle_dlpar_errorlog+0xa8/0x170
[  126.856118] [c000fe11bc60] [c00a9c54] 
pseries_hp_work_fn+0x94/0xa0
[  126.856275] [c000fe11bc90] [c01071d0] 
process_one_work+0x2b0/0x5a0
[  126.856430] [c000fe11bd20] [c0107568] worker_thread+0xa8/0x670
[  126.856563] [c000fe11bdc0] [c0110164] kthread+0x164/0x1b0
[  126.856695] [c000fe11be30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
[  126.856846] Instruction dump:
[  126.856931] 6000 387f0060 48824b19 6000 38210040 e8010010 eb81ffe0 
eba1ffe8 
[  126.857088] ebc1fff0 ebe1fff8 7c0803a6 4e800020 <0fe0>  3c4c0115 
3842e890 
[  126.857243] ---[ end trace 76fab848b8f01d0a ]---
[  126.859577] 


Investigating the cause I've found this kernel commit:

commit 943db62c316c578f8e2cc6fb81a5f641096b29bf
Author: Nathan Fontenot 
Date:   Wed Feb 15 13:45:30 2017 -0500

powerpc/pseries: Revert 'Auto-online hotplugged memory'

This reverts commit ec999072442a ("powerpc/pseries: Auto-online

[Kernel-packages] [Bug 1710922] [NEW] Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream

You have been subscribed to a public bug:

== Comment: #0 - Daniel Henrique Barboza  - 2017-08-08 
09:13:31 ==
- Host information: Ubuntu 16.10 running upstream QEMU

$ uname -a
Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

$ cat /proc/cpuinfo
processor   : 0
cpu : POWER8E (raw), altivec supported
clock   : 2061.00MHz
revision: 2.1 (pvr 004b 0201)
(...)
timebase: 51200
platform: PowerNV
model   : 8247-42L
machine : PowerNV 8247-42L
firmware: OPAL


- qemu command line that launched the Ubuntu 17.10 ppc64el guest:

sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable-kvm
-device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-
vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1
--machine pseries,accel=kvm,usb=off,dump-guest-core=off -m
4G,slots=32,maxmem=32G -drive
file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id=drive-
virtio-disk0,cache=none -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -nographic


- guest information: Ubuntu 17.10 ppc64el:

root@ubuntu1710:~# uname -a
Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu1710:~# 


- Problem: hotplugging a LMB generates a guest kernel Oops:

root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information
(qemu) 
(qemu) object_add memory-backend-ram,id=ram1,size=1G
(qemu) device_add pc-dimm,id=dimm1,memdev=ram1
(qemu) [  126.850952] kernel BUG at 
/build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185!
[  126.851285] Oops: Exception in kernel mode, sig: 5 [#1]
[  126.851428] SMP NR_CPUS=2048 
[  126.851428] NUMA 
[  126.851546] pSeries
[  126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm 
ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi 
crc32c_vpmsum virtio_blk
[  126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic 
#15-Ubuntu
[  126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn
[  126.852828] task: c000fea8 task.stack: c000fe118000
[  126.853000] NIP: c0350268 LR: c03501e0 CTR: 
[  126.853190] REGS: c000fe11b780 TRAP: 0700   Not tainted  
(4.11.0-10-generic)
[  126.853390] MSR: 8282b033 
[  126.853396]   CR: 42002422  XER: 2000
[  126.853672] CFAR: c03501e4 SOFTE: 1 
[  126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00 
0001 
[  126.853672] GPR04: c000f9901480 c000ffe21c00 003e 
0003 
[  126.853672] GPR08: 0002 0003 0003 
303078302d303030 
[  126.853672] GPR12: 2200 cfb8 c0110008 
c000fe1810c0 
[  126.853672] GPR16: c000fe050ea8 0010 c000fc30 
c000fea0 
[  126.853672] GPR20: c000f951a1a4 0004 0001 
0010 
[  126.853672] GPR24: 0001 c000f951a1a0 0004 
 
[  126.853672] GPR28:  0001 1000 
00014000 
[  126.855221] NIP [c0350268] remove_memory+0xf8/0x100
[  126.855338] LR [c03501e0] remove_memory+0x70/0x100
[  126.855453] Call Trace:
[  126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100 
(unreliable)
[  126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0
[  126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20
[  126.855959] [c000fe11bbf0] [c00a9af8] 
handle_dlpar_errorlog+0xa8/0x170
[  126.856118] [c000fe11bc60] [c00a9c54] 
pseries_hp_work_fn+0x94/0xa0
[  126.856275] [c000fe11bc90] [c01071d0] 
process_one_work+0x2b0/0x5a0
[  126.856430] [c000fe11bd20] [c0107568] worker_thread+0xa8/0x670
[  126.856563] [c000fe11bdc0] [c0110164] kthread+0x164/0x1b0
[  126.856695] [c000fe11be30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
[  126.856846] Instruction dump:
[  126.856931] 6000 387f0060 48824b19 6000 38210040 e8010010 eb81ffe0 
eba1ffe8 
[  126.857088] ebc1fff0 ebe1fff8 7c0803a6 4e800020 <0fe0>  3c4c0115 
3842e890 
[  126.857243] ---[ end trace 76fab848b8f01d0a ]---
[  126.859577] 


Investigating the cause I've found this kernel commit:

commit 943db62c316c578f8e2cc6fb81a5f641096b29bf
Author: Nathan Fontenot 
Date:   Wed Feb 15 13:45:30 2017 -0500

powerpc/pseries: Revert 'Auto-online hotplugged memory'

This reverts commit ec999072442a

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

2017-08-15 Thread Andy Whitcroft

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

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

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

Title:
  linux: 4.10.0-33.37 -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:
  In Progress
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 Zesty:
  Confirmed

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

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

  backports: 1709304
  derivatives: 1709305
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 11. August 2017 11:32 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop

2017-08-15 Thread gp

Also, now that I am back to kernel 4.10, wireless is back but the volume
keys still do not work. Some other updates were performed as well so
that might be a coincidence.

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

Title:
  Brightness control keys not working on Gigabyte P57 laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My
  brightness control keys (fn+F3, fn+F4) are not getting detected. After
  reading about how keypresses are handled by the Linux kernel, I used
  showkey to check the scancodes of these keys. I did not get any
  output. Similarly no output from xev, evtest and acpi_listen.

  Just for your reference, other keys like volume up (fn+F9) are working 
alright.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-12-14 (65 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.8.0-040800-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop

2017-08-15 Thread gp

It was never set in the first place

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

Title:
  Brightness control keys not working on Gigabyte P57 laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My
  brightness control keys (fn+F3, fn+F4) are not getting detected. After
  reading about how keypresses are handled by the Linux kernel, I used
  showkey to check the scancodes of these keys. I did not get any
  output. Similarly no output from xev, evtest and acpi_listen.

  Just for your reference, other keys like volume up (fn+F9) are working 
alright.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-12-14 (65 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.8.0-040800-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

2017-08-15 Thread bugproxy

--- Comment From jhop...@us.ibm.com 2017-08-15 12:06 EDT---
Thanks! Seeing good improvements with this build based on some unixbench 
microbenchmarks:

baseline = 4.10.0-32-generic
RPT fixes = 4.10.0-32.36~lp1709220

Unixbench baseline RPT fixesimprovement
SMToff  SMT4SMToff  SMT4SMToff  SMT4
Execl ? single   656.2   963.0  1583.0  1507.1  141.2%  56.5%
Execl ? multi   2522.9  6527.3  4720.2 11766.7   87.1%  80.3%
Sysexec ? single 487.2   715.5   787.0  1082.2   61.5%  51.3%
Sysexec ? multi 1783.0  4845.2  2738.6  8029.3   53.6%  65.7%
Spawn ? single  1645.0  2546.8  2632.9  3168.8   60.1%  24.4%
Spawn ? multi   5877.5 17688.8  8459.9 23650.1   43.9%  33.7%

Note this was on a 4core DD1 system running at 1.6GHz.

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

Title:
  RPT related fixes missing in Ubuntu 16.04.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  The following patches are missing in the ubuntu 16.04.3 kernel

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156104.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156105.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/157130.html
   
  ---uname output---
  4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 UTC 2017 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = power9 
   
  ---Steps to Reproduce---
  Did a fork and exec benchmark to look at the performance and they pointed to 
radix routines.
   
  Upstream commits mentioned:

  commitf7327e0ba3805470cced2acfa053e795362ee41d 
  powerpc/mm/radix: Remove unnecessary ptesync

  commitf6b0df55cad252fedd60aa2ba75a0207d0006283 
  powerpc/mm/radix: Don't do page walk cache flush when doing full mm flush

  commita5998fcb92552a18713b6aa5c146aa400e4d75ee
  powerpc/mm/radix: Optimise tlbiel flush all case

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

-- 
Mailing list: https://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 1710501] Re: can't open synaptic package manager

2017-08-15 Thread kevinek

I am not really able to do this I have downloaded the mainline kernel 
packages and put them in a separate folder (within download folder). 
Then I do sudo dpkg -i *.deb, then I get error telling me no such file 
or directory. Do I point it at the folder somehow and if so how? Can you 
give me the actual terminal commands? I am sorry I am not much of an 
expert, in fact I am not much of a anything much, so need step by step!

Thanks.

On 14/08/17 20:07, Joseph Salisbury wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.13 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>

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

Title:
  can't open synaptic package manager

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I try and open synaptic package man. I get this message.
  E: The package linux-image-4.10.0-23-generic needs to be reinstalled, but I 
can't find an archive for it.
  E: Internal error opening cache (1). Please report.

  Before this the software updater is showing 1 update but does not
  update it, I click on install and it says installing a few moments but
  then returns to showing one update to be done?

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

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

[Kernel-packages] [Bug 1710904] Re: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12

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

Title:
  linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz

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

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

[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset

2017-08-15 Thread Shrirang Bagul

@Seth,

When will the Redpine RS9113 firmware available in linux-firmware for
Xenial? Is anything blocking the release?

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

Title:
  Add firmware for Redpine 9113 chipset

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The redpine driver in xenial has been updated, and a
  corresponding firmware update is also required.

  Fix: Add new firmware files.

  Test case: Test with affected hw and with a kernel which has the
  driver update.

  Regression potential: These are new files used by a single driver, so
  no regressions are possible outside of that driver.

  ---

  Latest firmware images provided by Redpine in 1.2 production release
  are updated to ubuntu's linux-firmware.git

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

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

[Kernel-packages] [Bug 1710799] Re: missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build failure

The removal was intentional. In fact it was supposed to be removed from
the exported headers in 4.2 but a mistake was made, and this was just
now fixed in 4.12. The justification is in the original commit message.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b72e7464e4cf80117938e6adb8c22fdc1ca46d42

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

Title:
  missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build
  failure

Status in collectd package in Ubuntu:
  Confirmed

Bug description:
  The collectd package fails to build in artful-proposed on x86 because
  linux-libc-dev 4.12.0-11.12 has dropped the asm/msr-index.h header
  that was previously present and which collectd's turbostat plugin
  relied on.

  Please re-add this header if possible.  If there is a reason that it
  should not be exposed to userspace and this is a deliberate change,
  please reassign this bug and I will arrange to bundle it with the
  collectd source instead.

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

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

[Kernel-packages] [Bug 1710799] Re: missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build failure

Reassigning to collectd package, which will need to start bundling this
header.

** Package changed: linux (Ubuntu) => collectd (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/1710799

Title:
  missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build
  failure

Status in collectd package in Ubuntu:
  Confirmed

Bug description:
  The collectd package fails to build in artful-proposed on x86 because
  linux-libc-dev 4.12.0-11.12 has dropped the asm/msr-index.h header
  that was previously present and which collectd's turbostat plugin
  relied on.

  Please re-add this header if possible.  If there is a reason that it
  should not be exposed to userspace and this is a deliberate change,
  please reassign this bug and I will arrange to bundle it with the
  collectd source instead.

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

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

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

apport information

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

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD

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

apport information

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name:

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

apport information

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD

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

apport information

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD

[Kernel-packages] [Bug 1710877] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1710877/+attachment/4932866/+files/ProcCpuinfoMinimal.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/1710877

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:

[Kernel-packages] [Bug 1710877] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1710877/+attachment/4932862/+files/IwConfig.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/1710877

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD

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

apport information

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode). 

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1 

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD

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