date:20180323

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 1757584

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

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==
  [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  [Fix]
  one commit from mainline kernel.

  [Regression Potential]
  very low, since this patch only applies to the specific Dell machine 
Precision 3930.

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

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

[Kernel-packages] [Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

2018-03-23 Thread Hui Wang

** Description changed:

  == SRU Justification ==
- 
+ [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.
  
  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.
  
- == Test Case ==
- 
+ [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.
  
- == Fix ==
- 
+ [Fix]
  one commit from mainline kernel.
  
- == Regression Potential ==
- 
- very low, since this patch only applies to the specific Dell machine
- Precision 3930.
+ [Regression Potential]
+ very low, since this patch only applies to the specific Dell machine 
Precision 3930.

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

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==
  [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  [Fix]
  one commit from mainline kernel.

  [Regression Potential]
  very low, since this patch only applies to the specific Dell machine 
Precision 3930.

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

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

[Kernel-packages] [Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

2018-03-23 Thread Hui Wang

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

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

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  == Test Case ==

  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  == Fix ==

  one commit from mainline kernel.

  == Regression Potential ==

  very low, since this patch only applies to the specific Dell machine
  Precision 3930.

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

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

[Kernel-packages] [Bug 1758491] Re: package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to install/upgrade: package linux-signed-image-4.4.0-72-generic is not ready for configuration cannot

2018-03-23 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-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1758491

Title:
  package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to
  install/upgrade: package linux-signed-image-4.4.0-72-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux-signed package in Ubuntu:
  New

Bug description:
  cannot install update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-72-generic 4.4.0-72.93
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 24 17:00:30 2018
  DuplicateSignature:
   package:linux-signed-image-4.4.0-72-generic:4.4.0-72.93
   Processing triggers for menu (2.1.47ubuntu1) ...
   dpkg: error processing package linux-signed-image-4.4.0-72-generic 
(--configure):
package linux-signed-image-4.4.0-72-generic is not ready for configuration
  ErrorMessage: package linux-signed-image-4.4.0-72-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-06-21 (641 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to 
install/upgrade: package linux-signed-image-4.4.0-72-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1758491] [NEW] package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to install/upgrade: package linux-signed-image-4.4.0-72-generic is not ready for configuration cann

2018-03-23 Thread Hasso

Public bug reported:

cannot install update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-signed-image-4.4.0-72-generic 4.4.0-72.93
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sat Mar 24 17:00:30 2018
DuplicateSignature:
 package:linux-signed-image-4.4.0-72-generic:4.4.0-72.93
 Processing triggers for menu (2.1.47ubuntu1) ...
 dpkg: error processing package linux-signed-image-4.4.0-72-generic 
(--configure):
  package linux-signed-image-4.4.0-72-generic is not ready for configuration
ErrorMessage: package linux-signed-image-4.4.0-72-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-06-21 (641 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: linux-signed
Title: package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to 
install/upgrade: package linux-signed-image-4.4.0-72-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to
  install/upgrade: package linux-signed-image-4.4.0-72-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux-signed package in Ubuntu:
  New

Bug description:
  cannot install update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-72-generic 4.4.0-72.93
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 24 17:00:30 2018
  DuplicateSignature:
   package:linux-signed-image-4.4.0-72-generic:4.4.0-72.93
   Processing triggers for menu (2.1.47ubuntu1) ...
   dpkg: error processing package linux-signed-image-4.4.0-72-generic 
(--configure):
package linux-signed-image-4.4.0-72-generic is not ready for configuration
  ErrorMessage: package linux-signed-image-4.4.0-72-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-06-21 (641 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.4.0-72-generic 4.4.0-72.93 failed to 
install/upgrade: package linux-signed-image-4.4.0-72-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1153618]

2018-03-23 Thread Laura

*** MASS BUG UPDATE **
This bug is being closed with INSUFFICIENT_DATA as there has not been a 
response in 4 weeks. If you did actually update, we apologize for the 
inconvenience (there are a lot of bugs). If you are still experiencing this 
issue, please reopen and attach the relevant data from the latest kernel you 
are running and any data that might have been requested previously.

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

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux package in Fedora:
  Expired

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

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

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

[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader

2018-03-23 Thread Bug Watch Updater

** Changed in: linux (Fedora)
   Status: Confirmed => 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/1153618

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux package in Fedora:
  Expired

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

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

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

[Kernel-packages] [Bug 1367366] Re: [DELL XPS 15 L502X] internal sd card reader problem

2018-03-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  [DELL XPS 15 L502X] internal sd card reader problem

Status in linux package in Ubuntu:
  Expired

Bug description:
  The internal SD-card reader is not working in a DELL XPS 15 L502X.

  messages at the system log:
  kernel: [  332.414191] mmc0: error -110 whilst initialising SD card
  kernel: [  332.763919] mmc0: error -110 whilst initialising SD card

  After several tries, the card is recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chuck-game   2122 F lxpanel
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  CurrentDesktop: LXDE
  Date: Tue Sep  9 18:24:58 2014
  HibernationDevice: RESUME=UUID=031c1bfb-a99f-45ff-b7fc-eeaa254f9a2a
  InstallationDate: Installed on 2013-08-10 (394 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=50751449-1f90-4151-bc30-329f3b22e2cf ro quiet 
rcutree.rcu_idle_gp_delay=1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (144 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1744337] Re: USB devices not recognized after suspend to RAM

2018-03-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  USB devices not recognized after suspend to RAM

Status in linux package in Ubuntu:
  Expired

Bug description:
  After a fresh reboot, USB devices / hard disks are recognized
  correctly.

  After the first suspend to RAM, this recognition does not work any
  more.

  USB Flash drives are recognized as xhci_hdc:
  ...
  Jan 19 16:29:39 mbpr13b kernel: [ 4312.095869] usb 2-1: new SuperSpeed USB 
device number 20 using xhci_hcd
  Jan 19 16:29:44 mbpr13b kernel: [ 4317.199585] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:44 mbpr13b kernel: [ 4317.307436] usb 2-1: new SuperSpeed USB 
device number 20 using xhci_hcd
  Jan 19 16:29:49 mbpr13b kernel: [ 4322.575395] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:49 mbpr13b kernel: [ 4322.891260] usb 2-1: new SuperSpeed USB 
device number 21 using xhci_hcd
  Jan 19 16:29:55 mbpr13b kernel: [ 4327.951076] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:55 mbpr13b kernel: [ 4328.058970] usb 2-1: new SuperSpeed USB 
device number 21 using xhci_hcd
  ...
  but do not mount

  Hard disks freeze the system

  Android Phones don't get recognized as xhci_hdc instead of an external 
storage device:
  ...
  Jan 19 16:34:17 mbpr13b kernel: [ 4589.93] usb 1-1: new high-speed USB 
device number 4 using xhci_hcd
  Jan 19 16:34:22 mbpr13b kernel: [ 4595.066102] usb 1-1: device descriptor 
read/64, error -110
  Jan 19 16:34:37 mbpr13b kernel: [ 4610.681476] usb 1-1: device descriptor 
read/64, error -110
  Jan 19 16:34:37 mbpr13b kernel: [ 4610.909265] usb 1-1: new high-speed USB 
device number 5 using xhci_hcd
  Jan 19 16:34:43 mbpr13b kernel: [ 4616.057120] usb 1-1: device descriptor 
read/64, error -110

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   1317 F pulseaudio
   /dev/snd/controlC0:  wolf   1317 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 16:30:16 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (91 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1757021] Re: ubuntu restarts on resume from hibernate

final update. after closing the lid for over a minute, it's back to
rebooting. when i closed the lid a few seconds then re-opened, it simply
shut down.

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

Title:
  ubuntu restarts on resume from hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever I sleep the computer, upon waking/opening the lid, it
  reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm,
  adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to
  /etc/default/grub. Nothing seems to help. I believe this started after
  updating to 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eric   1809 F pulseaudio
   /dev/snd/controlC0:  eric   1809 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 20:50:52 2018
  HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691
  InstallationDate: Installed on 2017-05-29 (294 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 7352
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0H9K1J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08:
  dmi.product.name: Inspiron 7352
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1757021] Re: ubuntu restarts on resume from hibernate

i keep seeing acpi bios error (bug) in dmesg. attaching dmesg.log if it
helps any.

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757021/+attachment/5088778/+files/dmesg.log

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

Title:
  ubuntu restarts on resume from hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever I sleep the computer, upon waking/opening the lid, it
  reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm,
  adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to
  /etc/default/grub. Nothing seems to help. I believe this started after
  updating to 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eric   1809 F pulseaudio
   /dev/snd/controlC0:  eric   1809 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 20:50:52 2018
  HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691
  InstallationDate: Installed on 2017-05-29 (294 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 7352
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0H9K1J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08:
  dmi.product.name: Inspiron 7352
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1757021] Re: ubuntu restarts on resume from hibernate

not sure exactly how to add a tag. just add the tag to a comment and
post?

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

Title:
  ubuntu restarts on resume from hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever I sleep the computer, upon waking/opening the lid, it
  reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm,
  adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to
  /etc/default/grub. Nothing seems to help. I believe this started after
  updating to 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eric   1809 F pulseaudio
   /dev/snd/controlC0:  eric   1809 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 20:50:52 2018
  HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691
  InstallationDate: Installed on 2017-05-29 (294 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 7352
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0H9K1J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08:
  dmi.product.name: Inspiron 7352
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1757021] Re: ubuntu restarts on resume from hibernate

kernel-bug-exists-upstream

With the latest rc6 kernel, now my computer stalls a moment on resume
and then shuts down instead of rebooting.

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

Title:
  ubuntu restarts on resume from hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever I sleep the computer, upon waking/opening the lid, it
  reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm,
  adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to
  /etc/default/grub. Nothing seems to help. I believe this started after
  updating to 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eric   1809 F pulseaudio
   /dev/snd/controlC0:  eric   1809 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 20:50:52 2018
  HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691
  InstallationDate: Installed on 2017-05-29 (294 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 7352
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0H9K1J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08:
  dmi.product.name: Inspiron 7352
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

Can see the difference in the dmesg output

16.04:
Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1049-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295

18.04:
Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

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

apport information

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

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

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

apport information

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

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

apport information

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

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

apport information

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

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

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

apport information

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

apport information

** Tags added: apport-collected ec2-images

** Description changed:

  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html
  
  It appears this is done for 16.04, but in 18.04 it is the default.
  
  Test done by spinning up an m5.large instance in ap-southeast-2.
  
  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):
  
  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295
  
  $ uname -r
  4.4.0-1049-aws
  
  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):
  
  $ cat /sys/module/nvme_core/parameters/io_timeout
  255
  
  $ uname -r
  4.15.0-1001-aws
  
  Perhaps as part of the move to nvme_core this got lost.
+ --- 
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.8-0ubuntu10
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ CRDA: N/A
+ DistroRelease: Ubuntu 18.04
+ Ec2AMI: ami-5c5d903e
+ Ec2AMIManifest: (unknown)
+ Ec2AvailabilityZone: ap-southeast-2b
+ Ec2InstanceType: m5.large
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ JournalErrors:
+  -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
+  Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: Amazon EC2 m5.large
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
+ ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-1001-aws N/A
+  linux-backports-modules-4.15.0-1001-aws  N/A
+  linux-firmware   N/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic ec2-images
+ Uname: Linux 4.15.0-1001-aws x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
+ _MarkForUpload: False
+ dmi.bios.date: 10/16/2017
+ dmi.bios.vendor: Amazon EC2
+ dmi.bios.version: 1.0
+ dmi.board.asset.tag: i-0d27cecf4877dafa7
+ dmi.board.vendor: Amazon EC2
+ dmi.chassis.asset.tag: Amazon EC2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Amazon EC2
+ dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
+ dmi.product.name: m5.large
+ dmi.sys.vendor: Amazon EC2

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1758466/+attachment/5088754/+files/AudioDevicesInUse.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/1758466

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.

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

apport information

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

[Kernel-packages] [Bug 1758471] Re: apparmor: fix bad __initdata tagging on, apparmor_initialized

2018-03-23 Thread John Johansen

No logs needed as its a build warning


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

Title:
  apparmor: fix bad __initdata tagging on, apparmor_initialized

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

Bug description:
  When building the Xenial kernel we get the following warning

  WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
  the function param_set_aauint() to the variable
  .init.data:apparmor_initialized

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

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

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

apport information

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

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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

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

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

Title:
  apparmor: fix bad __initdata tagging on, apparmor_initialized

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

Bug description:
  When building the Xenial kernel we get the following warning

  WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
  the function param_set_aauint() to the variable
  .init.data:apparmor_initialized

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

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

[Kernel-packages] [Bug 1758471] Re: apparmor: fix bad __initdata tagging on, apparmor_initialized

2018-03-23 Thread John Johansen

This only affect Xenial.


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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  apparmor: fix bad __initdata tagging on, apparmor_initialized

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

Bug description:
  When building the Xenial kernel we get the following warning

  WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
  the function param_set_aauint() to the variable
  .init.data:apparmor_initialized

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

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

[Kernel-packages] [Bug 1758471] [NEW] apparmor: fix bad __initdata tagging on, apparmor_initialized

2018-03-23 Thread John Johansen

Public bug reported:

When building the Xenial kernel we get the following warning

WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
the function param_set_aauint() to the variable
.init.data:apparmor_initialized

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

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: John Johansen (jjohansen)
 Status: Confirmed

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

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

Title:
  apparmor: fix bad __initdata tagging on, apparmor_initialized

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

Bug description:
  When building the Xenial kernel we get the following warning

  WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
  the function param_set_aauint() to the variable
  .init.data:apparmor_initialized

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

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

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-03-23 Thread Nicolas Krzywinski

Same problem on Gigabyte GA-T1028X
Intel® Atom™ Processor N280(1.66GHz)
Mobile Intel® GS945 Express Chipsets
Intel® GMA 950

Adding this to /etc/default/grub helped me too:
GRUB_GFXPAYLOAD_LINUX=text

Additionally adding this to the GRUB_CMDLINE_LINUX_DEFAULT line enabled the 
touchpad (which wasn't working before):
i8042.noloop=1 usbhid.quirks=0xeef:0x1:0x40

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

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: bionic

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.

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

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

[Kernel-packages] [Bug 1758466] [NEW] bionic: default io_timeout for nvme is 255 on AWS

Public bug reported:

According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

It appears this is done for 16.04, but in 18.04 it is the default.

Test done by spinning up an m5.large instance in ap-southeast-2.

Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

$ cat /sys/module/nvme/parameters/io_timeout
4294967295

$ uname -r
4.4.0-1049-aws

Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

$ cat /sys/module/nvme_core/parameters/io_timeout
255

$ uname -r
4.15.0-1001-aws

Perhaps as part of the move to nvme_core this got lost.

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

** Summary changed:

- default io_timeout for nvme is 255 on AWS
+ bionic: default io_timeout for nvme is 255 on AWS

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in linux package in Ubuntu:
  New

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.

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

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

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

Title:
  DVD drive works under Win dows 10 but not Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Drive does not mount when any supported media type is inserted and is
  unusable. Older drive(NEC DVD+/-RW ND-6650A) with newer motherboard
  (Z370N-WIFI).

  greg@greg-Z370N-WIFI:~$ dmesg |grep -i ata3
  [0.660472] ata3: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b200 
irq 129
  [0.980029] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [0.983555] ata3.00: ATAPI: _NEC DVD+/-RW ND-6650A, 103D, max UDMA/33
  [0.983556] ata3.00: applying bridge limits
  [0.990656] ata3.00: configured for UDMA/33
  [6.112005] ata3.00: qc timeout (cmd 0xa0)
  [6.116004] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [6.432011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.442649] ata3.00: configured for UDMA/33
  [   11.488004] ata3.00: qc timeout (cmd 0xa0)
  [   11.488008] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [   11.488009] ata3: limiting SATA link speed to 1.5 Gbps
  [   11.488010] ata3.00: limiting speed to UDMA/33:PIO3
  [   11.804011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   11.814638] ata3.00: configured for UDMA/33
  [   16.864003] ata3.00: qc timeout (cmd 0xa0)
  [   16.864007] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [   16.864008] ata3.00: disabled
  [   16.868004] ata3: hard resetting link
  [   17.184011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   17.184014] ata3: EH complete
  greg@greg-Z370N-WIFI:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   1651 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 17:17:43 2018
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=c0e62877-bafa-4694-b2c3-8f4f2e1df82f
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2018-03-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Gigabyte Technology Co., Ltd. Z370N WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=4b0ef4f1-040a-46c5-af19-f012da1ef057 ro quiet splash acpi=off 
i915.alpha_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   17:18:20.743: The udisks-daemon is running (name-owner :1.2).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd11/09/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370N WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1758463] [NEW] DVD drive works under Win dows 10 but not Ubuntu 17.10

2018-03-23 Thread G Money

Public bug reported:

Drive does not mount when any supported media type is inserted and is
unusable. Older drive(NEC DVD+/-RW ND-6650A) with newer motherboard
(Z370N-WIFI).

greg@greg-Z370N-WIFI:~$ dmesg |grep -i ata3
[0.660472] ata3: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b200 
irq 129
[0.980029] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[0.983555] ata3.00: ATAPI: _NEC DVD+/-RW ND-6650A, 103D, max UDMA/33
[0.983556] ata3.00: applying bridge limits
[0.990656] ata3.00: configured for UDMA/33
[6.112005] ata3.00: qc timeout (cmd 0xa0)
[6.116004] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[6.432011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[6.442649] ata3.00: configured for UDMA/33
[   11.488004] ata3.00: qc timeout (cmd 0xa0)
[   11.488008] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[   11.488009] ata3: limiting SATA link speed to 1.5 Gbps
[   11.488010] ata3.00: limiting speed to UDMA/33:PIO3
[   11.804011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   11.814638] ata3.00: configured for UDMA/33
[   16.864003] ata3.00: qc timeout (cmd 0xa0)
[   16.864007] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[   16.864008] ata3.00: disabled
[   16.868004] ata3: hard resetting link
[   17.184011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   17.184014] ata3: EH complete
greg@greg-Z370N-WIFI:~$

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-37-generic 4.13.0-37.42
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  greg   1651 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 17:17:43 2018
GvfsMonitorError:
 This tool has been deprecated, use 'gio mount' instead.
 See 'gio help mount' for more info.
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=c0e62877-bafa-4694-b2c3-8f4f2e1df82f
HotplugNewDevices:
 
HotplugNewMounts:
 
InstallationDate: Installed on 2018-03-17 (6 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Gigabyte Technology Co., Ltd. Z370N WIFI
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=4b0ef4f1-040a-46c5-af19-f012da1ef057 ro quiet splash acpi=off 
i915.alpha_support=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-37-generic N/A
 linux-backports-modules-4.13.0-37-generic  N/A
 linux-firmware 1.169.3
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 17:18:20.743: The udisks-daemon is running (name-owner :1.2).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: Default string
dmi.board.name: Z370N WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd11/09/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370N WIFI
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  DVD drive works under Win dows 10 but not Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Drive does not mount when any supported media type is inserted and is
  unusable. Older drive(NEC DVD+/-RW ND-6650A) with newer motherboard
  (Z370N-WIFI).

  greg@greg-Z370N-WIFI:~$ dmesg |grep -i ata3
  [0.660472] ata3: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b200 
irq 129
  [0.980029] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [0.983555] ata3.00: ATAPI: _NEC DVD+/-RW ND-6650A, 103D, max UDMA/33
  [0.983556] ata3.00: applying bridge limits
  [0.990656] ata3.00: configured for UDMA/33
  [6.112005] ata3.00: qc timeout (cmd 0xa0)
  [6.116004] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [6.432011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 30

[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!

2018-03-23 Thread r.stricklin

I was able to install the ppc64el 4.4.0-117 kernel from xenial-proposed.
It boots and passes at least enough traffic to make an interactive ssh
session function.

I'm having some DKMS issues, however, which are preventing me from
validating the patch prevents crash as expected (one of the modules we
need has BUILD_EXCLUSIVE for 4.8 and 4.10 only). I am working with the
IBM development team who publishes these modules to get that resolved
ASAP (they were surprised by this, so we are waiting for answers from
individual engineers, probably Monday).

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

Title:
  bnx2x_attn_int_deasserted3:4323 MC assert!

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

Bug description:
  SRU Justification
  =

  A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
  card attached, and uses openvswitch to bridge an ibmveth interface for
  traffic from other LPARs.

  We see the following crash sometimes when running netperf:
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert!
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 
0x25e42a7e 0x00462a38 0x00010052
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump -
  ... (dump of registers follows) ...

  Subsequent debugging reveals that the packets causing the issue come
  through the ibmveth interface - from the AIX LPAR. The veth protocol
  is 'special' - communication between LPARs on the same chassis can use
  very large (64k) frames to reduce overhead. Normal networks cannot
  handle such large packets, so traditionally, the VIOS partition would
  signal to the AIX partitions that it was 'special', and AIX would send
  regular, ethernet-sized packets to VIOS, which VIOS would then send
  out.

  This signalling between VIOS and AIX is done in a way that is not
  standards-compliant, and so was never made part of Linux. Instead, the
  Linux driver has always understood large frames and passed them up the
  network stack.

  In some cases (e.g. with TCP), multiple TCP segments are coalesced
  into one large packet. In Linux, this goes through the generic receive
  offload code, using a similar mechanism to GSO. These segments can be
  very large which presents as a very large MSS (maximum segment size)
  or gso_size.

  Normally, the large packet is simply passed to whatever network
  application on Linux is going to consume it, and everything is OK.

  However, in this case, the packets go through Open vSwitch, and are
  then passed to the bnx2x driver. The bnx2x driver/hardware supports
  TSO and GSO, but with a restriction: the maximum segment size is
  limited to around 9700 bytes. Normally this is more than adequate.
  However, if a large packet with very large (>9700 byte) TCP segments
  arrives through ibmveth, and is passed to bnx2x, the hardware will
  panic.

  [Impact]

  bnx2x card panics, requiring power cycle to restore functionality.

  The workaround is turning off TSO, which prevents the crash as the
  kernel resegments *all* packets in software, not just ones that are
  too big. This has a performance cost.

  [Fix]

  Test packet size in bnx2x feature check path and disable GSO if it is
  too large. To do this we move a function from one file to another and
  add another in the networking core.

  [Regression Potential]

  A/B/X: The changes to the network core are easily reviewed. The changes to 
behaviour are limited to the bnx2x card driver.
  The most likely failure case is a false-positive on the size check, which 
would lead to a performance regression only.

  T: This also involves a different change to the networking core to add
  the old-style GSO checking, which is more invasive. However the
  changes are simple and easily reviewed.

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

I think this bug may actually be INVALID.

It turns out the root cause is setting this in /etc/default/grub, which I had 
done in order to change the Grub keyboard layout:
GRUB_TERMINAL_INPUT=at_keyboard

After removing this line (and updating grub), the brightness keys work
correctly and none of the other keys trigger brightness changes.

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt5.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088637/+files/ssdt5.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt6.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088638/+files/ssdt6.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt7.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088639/+files/ssdt7.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt3.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088635/+files/ssdt3.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt9.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088641/+files/ssdt9.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt4.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088636/+files/ssdt4.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt8.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088640/+files/ssdt8.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt2.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088634/+files/ssdt2.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088615/+files/acpidump.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/1758442

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "dsdt.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088618/+files/dsdt.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "dsdt.dsl"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088629/+files/dsdt.dsl

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "fwts"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088630/+files/fwts

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "results.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088632/+files/results.log

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "iasl-output.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088631/+files/iasl-output.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/1758442

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "backlight"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088616/+files/backlight

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "ssdt1.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088633/+files/ssdt1.dat

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

** Attachment added: "dmidecode.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442/+attachment/5088617/+files/dmidecode.log

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1758442] [NEW] [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Public bug reported:

Three of the "function" keys on this laptop don't work at all: "Mute",
"Brightness Down", and "Brightness Up". I believe these keys are
controlled by WMI. Other buttons not controlled by WMI, such as "Volume
Up" and "Volume Down" (both by ACPI), work fine. Setting display
brightness via software (e.g., GUI slider) works fine.

Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are interpreted
as "Brightness Down". This behavior seems to come and go randomly after
each reboot.

I have tried setting (separately) acpi_osi=Linux and
acpi_backlight=vendor without effect.

The hp_wmi driver raises these message at each boot:
[   19.610528] hp_wmi: query 0xd returned error 0x5
[   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

This system has the latest BIOS (1.43A, released 2018-01-25) and the
latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

No output is generated when pressing these buttons with evtest (choosing
option 8, "HP WMI hotkeys"), xev, or acpi_listen).

I have attached the debugging information requested at
,
although fwts method does not seem to be a valid command (anymore?).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vectro 1415 F pulseaudio
 /dev/snd/controlC0:  vectro 1415 F pulseaudio
CurrentDesktop: KDE
Date: Fri Mar 23 17:15:19 2018
HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
InstallationDate: Installed on 2018-03-23 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
MachineType: Hewlett-Packard HP ProBook 640 G1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-12-generic N/A
 linux-backports-modules-4.15.0-12-generic  N/A
 linux-firmware 1.173
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L78 Ver. 01.43
dmi.board.name: 2101
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.3C
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 640 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

** Attachment added: "acpi"
   https://bugs.launchpad.net/bugs/1758442/+attachment/5088597/+files/acpi

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  New

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10

[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel

2018-03-23 Thread Steve Langasek

Hello Po-Hsu, or anyone else affected,

Accepted lttng-modules into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/lttng-
modules/2.9.0-1ubuntu3.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lttng-modules (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-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/1756240

Title:
  Unable to build lttng-module with Artful kernel

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in lttng-modules source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Invalid
Status in lttng-modules source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in lttng-modules source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * The 4.13.0-38 artful kernel included a change (backported from
  4.15) that modifies the definition of kvm_mmio(). This breaks the
  lttng-modules-dkms package because it is using the old (<4.15)
  definition.

   * lttng-modules-dkms already has a list of kernel version
  "exceptions" with which it uses the >=4.15 definition. Proposed
  solution is to add the Ubuntu kernel range 4.13.0-38 up to
  4.14.255-255 to that list of exceptions.

  
  [Test Case]

   * Tested by first successfully building lttng-modules-dkms on
  4.13.0-37, then reproducing the problem described here on 4.13.0-38,
  then applying the code-change and confirming that I can successfully
  build on both 4.13.0-37 and 4.13.0-38 after that.

  [Regression Potential]

   * Low-regression potential. Could prevent lttng-modules-dkms from
  being built for specific kernel versions, but this is unlikely as the
  change was tested to confirm that it works as expected on 4.13.0-37
  and 4.13.0-38 - and should work fine for other Ubuntu kernels as well.




  The lttng module failed to build with the proposed Artful kernel
  (4.13.0-38), it works with 4.13.0-37

  Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 16 04:13 seq
   crw-rw 1 root audio 116, 33 Mar 16 04:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Fri Mar 16 04:17:14 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ...

[Kernel-packages] [Bug 1755979] Re: Cpu utilization showing system time for kvm guests (performance) (sysstat)

SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090973.html

** Description changed:

+ == SRU Justification ==
+ All KVM guest cpu utilization is being reported as sys% time in the host.
+ It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has
+ been broken since v4.13 by commit 8b24e69fc47e436.
+
+ Commit 61bd0f66ff92 fixes this bug and is included in mainline as of
v4.16-rc5.
+ The commit was cc'd to upstream stable, but has not yet landed in upstream
4.15.
+
+ == Fix ==
+ 61bd0f66ff92 ("KVM: PPC: Book3S HV: Fix guest time accounting with
VIRT_CPU_ACCOUNTING_GEN")
+
+ == Regression Potential ==
+ Low. Also cc'd to stable, so it has had additionl upstream review. Limited
to powerpc.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
== Comment: #0 - JENIFER HOPPER - 2018-03-14 16:20:47 ==
+++ This bug was initially created as a clone of Bug #163375 +++

---Problem Description---
All KVM guest cpu utilization is being reported as sys% time in the host.
It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has been
broken since v4.13 by commit:

commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5
Author: Paul Mackerras
Date: Mon Jun 26 15:45:51 2017 +1000

KVM: PPC: Book3S HV: Close race with testing for signals on guest entry

---

That is now fixed and upstream accepted in Paulus' tree as git commit:

https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-fixes&id=61bd0f66ff92d5ce765ff9850fd3cbfec773c560
("KVM: PPC: Book3S HV: Fix guest time accounting with
VIRT_CPU_ACCOUNTING_GEN")

- Please include this patch in Ubuntu so that guest cpu accounting is correct.
-
- Contact Information = jhop...@us.ibm.com
-
+ Please include this patch in Ubuntu so that guest cpu accounting is
+ correct.
+
+ Contact Information = jhop...@us.ibm.com
+
---uname output---
Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
-
- Machine Type = 5104-22C
-
+
+ Machine Type = 5104-22C
+
---Debugger---
A debugger is not configured
-
+
---Steps to Reproduce---
- Start a KVM guest, run something that generates cpu utilization in the
guest, observe mpstat on the host.
+ Start a KVM guest, run something that generates cpu utilization in the
guest, observe mpstat on the host.

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

Title:
Cpu utilization showing system time for kvm guests (performance)
(sysstat)

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

Bug description:
== SRU Justification ==
All KVM guest cpu utilization is being reported as sys% time in the host.
It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has
been broken since v4.13 by commit 8b24e69fc47e436.

Commit 61bd0f66ff92 fixes this bug and is included in mainline as of
v4.16-rc5.
The commit was cc'd to upstream stable, but has not yet landed in upstream
4.15.

== Fix ==
61bd0f66ff92 ("KVM: PPC: Book3S HV: Fix guest time accounting with
VIRT_CPU_ACCOUNTING_GEN")

== Regression Potential ==
Low. Also cc'd to stable, so it has had additionl upstream review. Limited
to powerpc.

== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.

== Comment: #0 - JENIFER HOPPER - 2018-03-14 16:20:47 ==
+++ This bug was initially created as a clone of Bug #163375 +++

commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5
Author: Paul Mackerras
Date: Mon Jun 26 15:45:51 2017 +1000

KVM: PPC: Book3S HV: Close race with testing for signals on guest
entry

---

That is now fixed and upstream accepted in Paulus' tree as git commit:

Please include this patch in Ubuntu so that guest cpu accounting is
correct.

Contact Information = jhop...@us.ibm.com

---uname output---
Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 5104-22C

---Debugger---
A debugger is not configu

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in tar source package in Artful:
  New

Bug description:
  
  == SRU Justification ==
  This bug causes btrfs and tar sparse to truncate archives.  This bug has been 
  fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of 
f48bf66b662e.

  These commits were cc'd to upstream stable and are already in Bionic.  
However, upstream
  4.13 is EOL, so Artful never recieved the fixes, which is the reason for
  the SRU request.

  == Fixes ==
  f48bf66b662e ("Btrfs: move definition of the function 
btrfs_find_new_delalloc_bytes")
  e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered 
append writes")

  == Regression Potential ==
  Low.  This fix was also sent and accepted to stable, so it has had additional 
upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 4.13.0.37.40
    Candidate: 4.13.0.37.40
    Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/
  https://www.spinics.net/lists/linux-btrfs/msg56768.html
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  d

[Kernel-packages] [Bug 1758375] Re: efifb broken on ThunderX-based Gigabyte nodes

** Description changed:

  [Impact]
  The following error is reported on boot:
  
  [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
  efifb!
  
  This results in the efifb not being activated at boot. On this platform,
  the same device will be  initialized by the astdrmfb driver later in
  boot, so this isn't fatal, so the real SRU justification here is getting
  rid of the error message. It is possible that there are platforms where
  the efifb is behind a PCI bridge, and there is no accelerated
  alternative that will load later. This (theoretical) issue is most
  likely to impact d-i installs, where only a subset of fb drivers are
  included.
  
  [Test Case]
  dmesg | grep "failed to claim resource for efifb"
  
  [Regression Risk]
- The fix for this has been upstream since v4.14 with no known regressions. The 
driver is only used on EFI systems, which limits the risk to a subset of 
x86/ARM platforms. 
+ The fix for this has been upstream since v4.14 with no known regressions. The 
driver is only used on EFI systems, which limits the risk to a subset of 
x86/ARM platforms. Regression tested on a Dell PowerEdge T610 (x86/UEFI).
  
  I have a test fix in ppa:dannf/efifb for regression testing.

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

Title:
  efifb broken on ThunderX-based Gigabyte nodes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  The following error is reported on boot:

  [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
  efifb!

  This results in the efifb not being activated at boot. On this
  platform, the same device will be  initialized by the astdrmfb driver
  later in boot, so this isn't fatal, so the real SRU justification here
  is getting rid of the error message. It is possible that there are
  platforms where the efifb is behind a PCI bridge, and there is no
  accelerated alternative that will load later. This (theoretical) issue
  is most likely to impact d-i installs, where only a subset of fb
  drivers are included.

  [Test Case]
  dmesg | grep "failed to claim resource for efifb"

  [Regression Risk]
  The fix for this has been upstream since v4.14 with no known regressions. The 
driver is only used on EFI systems, which limits the risk to a subset of 
x86/ARM platforms. Regression tested on a Dell PowerEdge T610 (x86/UEFI).

  I have a test fix in ppa:dannf/efifb for regression testing.

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

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

[Kernel-packages] [Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial

2018-03-23 Thread Jeff Lane

Hi Joeseph, I got the tester to try 4.16 and the tests still fail for
the same reason.  This is the test output indicating that
/sys/class/net/DEVICENAME/speed still reports a -1 for the second port.

ERROR:root:Detected link speed (-1) is lower than detected max speed (1)
ERROR:root:Check your device configuration and try again.
ERROR:root:If you want to override and test despite this under-speed link, use
ERROR:root:the --underspeed-ok option.

And just to verify, dmesg shows we are booted into 4.16:
[0.00] Linux version 4.16.0-041600rc6-generic (kernel@gloin) (gcc 
version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #201803182230 SMP Mon Mar 19 02:32:18 
UTC 2018
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600rc6-generic 
root=UUID=fcac9914-96c0-49b0-803b-269db52c3756 ro

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

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

Title:
  Intel NICs not properly reporting link speed in SysFS in Xenial

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Triaged

Bug description:
  This was discovered during certification testing of 16.04.4 (I've now
  seen this behaviour at least 2 times)

  A system under test has a 2 port Intel X550 NIC (10Gb)

  Udev reports the NIC as this:
  Category: NETWORK
  Interface: enp94s0f0
  Product: Ethernet Controller 10G X550T
  Vendor: Intel Corporation
  Driver: ixgbe (ver: 5.1.0-k)
  Path: /devices/pci:5d/:5d:00.0/:5e:00.0
  ID:   [8086:1563]
  Subsystem ID: [152d:8a13]

  Ethtool shows this info (this is for the second port, which has the issue)
  Settings for enp94s0f1:
   Supported ports: [ TP ]
   Supported link modes:   100baseT/Full
   1000baseT/Full
   1baseT/Full
   Supported pause frame use: Symmetric
   Supports auto-negotiation: Yes
   Advertised link modes:  100baseT/Full
   1000baseT/Full
   1baseT/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Speed: 1Mb/s
   Duplex: Full
   Port: Twisted Pair
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   MDI-X: Unknown
   Supports Wake-on: umbg
   Wake-on: g
   Current message level: 0x0007 (7)
    drv probe link
   Link detected: yes

  Note ethtool shows an active 10Gb link.

  The test tool determines the NIC speed by introspecting the sysfs data
  for each NIC port.  In this case, by looking at
  /sys/class/net/DEVICENAME/speed

  I've now seen this on a couple different NICs using the ixgbe driver.
  The first port will properly show connected link speed in
  /sys/class/net/DEVICENAME/speed but the second port shows -1 in that
  file.

  Because of this, certification tests are failing because the tool
  believes that the link speed is incorrect.

  This current example is using kernel 4.13.0-37.42~16.04.1

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

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

[Kernel-packages] [Bug 1756455] Re: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

** Description changed:

+ 
+ == SRU Justification ==
+ This bug causes btrfs and tar sparse to truncate archives.  This bug has been 
+ fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of 
f48bf66b662e.
+ 
+ These commits were cc'd to upstream stable and are already in Bionic.  
However, upstream
+ 4.13 is EOL, so Artful never recieved the fixes, which is the reason for
+ the SRU request.
+ 
+ == Fixes ==
+ f48bf66b662e ("Btrfs: move definition of the function 
btrfs_find_new_delalloc_bytes")
+ e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered 
append writes")
+ 
+ == Regression Potential ==
+ Low.  This fix was also sent and accepted to stable, so it has had additional 
upstream review.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
- root@ubuntu:~# apt-cache policy linux-image-virtual 
+ root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
-   Installed: 4.13.0.37.40
-   Candidate: 4.13.0.37.40
-   Version table:
-  *** 4.13.0.37.40 500
- 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  4.13.0.16.17 500
- 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
+   Installed: 4.13.0.37.40
+   Candidate: 4.13.0.37.40
+   Version table:
+  *** 4.13.0.37.40 500
+ 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  4.13.0.16.17 500
+ 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  
  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs
  
  To reproduce, run an Artful system with one spare disk:
  
  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
- - grep sda /proc/mounts 
+ - grep sda /proc/mounts
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
  
  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.
  
- % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
+ % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -
  
  And now without the sparse flag:
  
- # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
+ # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -
- 
  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.
  
  References:
  
- https://patchwork.kernel.org/patch/10151037/ 
- https://www.spinics.net/lists/linux-btrfs/msg56768.html 
+ https://patchwork.kernel.org/patch/10151037/
+ https://www.spinics.net/lists/linux-btrfs/msg56768.html
  https://www.spinics.net/lists/linux-btrfs/msg57111.html
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
-  crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
+  crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] fai

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

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

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

** Changed in: linux (Ubuntu Bionic)
   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/1749040

Title:
  KPTI support for arm64 systems

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1758375] Re: efifb broken on ThunderX-based Gigabyte nodes

** Description changed:

  [Impact]
  The following error is reported on boot:
  
  [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
  efifb!
  
  This results in the efifb not being activated at boot. On this platform,
  the same device will be  initialized by the astdrmfb driver later in
  boot, so this isn't fatal, so the real SRU justification here is getting
  rid of the error message. It is possible that there are platforms where
  the efifb is behind a PCI bridge, and there is no accelerated
  alternative that will load later. This (theoretical) issue is most
  likely to impact d-i installs, where only a subset of fb drivers are
  included.
  
  [Test Case]
  dmesg | grep "failed to claim resource for efifb"
  
  [Regression Risk]
- The fix for this has been upstream since v4.14. I have a test fix in 
ppa:dannf/efifb for regression testing.
+ The fix for this has been upstream since v4.14 with no known regressions. The 
driver is only used on EFI systems, which limits the risk to a subset of 
x86/ARM platforms. 
+ 
+ I have a test fix in ppa:dannf/efifb for regression testing.

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

Title:
  efifb broken on ThunderX-based Gigabyte nodes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  The following error is reported on boot:

  [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
  efifb!

  This results in the efifb not being activated at boot. On this
  platform, the same device will be  initialized by the astdrmfb driver
  later in boot, so this isn't fatal, so the real SRU justification here
  is getting rid of the error message. It is possible that there are
  platforms where the efifb is behind a PCI bridge, and there is no
  accelerated alternative that will load later. This (theoretical) issue
  is most likely to impact d-i installs, where only a subset of fb
  drivers are included.

  [Test Case]
  dmesg | grep "failed to claim resource for efifb"

  [Regression Risk]
  The fix for this has been upstream since v4.14 with no known regressions. The 
driver is only used on EFI systems, which limits the risk to a subset of 
x86/ARM platforms. 

  I have a test fix in ppa:dannf/efifb for regression testing.

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

That's great news.  I'll SRU those two commits to the Artful 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/1757565

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

2018-03-23 Thread Øystein Alværvik

In *Bionic*, the kernel in proposed (4.15.0-13.14) and in release
(4.15.0-12.13) both fix this regression.

I won't test the fix on Artful; I don't have the system installed and I
don't want to spend the time since Artful won't be supported for very
long anyway (and this bug affects only very few users).

** Tags added: verification-done-bionic

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

Title:
[regression] Colour banding and artefacts appear system-wide on an
Asus Zenbook UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Released

Bug description:
=== SRU Justification ===
[Impact]
Color dithering not working correctly because the graphics driver
assumes the panel support 8bpc, but the panel only supports 6bpc.

[Test]
User reports the issue start appearing from v4.8-rc2.
The issue is fixed with the patch.

[Fix]
Add a quirk to tell DRM that this panel only supports 6bpc.

[Regression Potential]
Low. This fix matches a very specific panel.

=== Original Bug Report ===
- Ubuntu 18.04 (with updates as of 14 Feb 2018).
- Laptop: Asus Zenbook UX303
- CPU: Intel i5 4210U
- Graphics: Intel HD 4400

Problem description: Colour artefacts and banding in all apps.
Graphics, photos and videos display as though the colour range is
improperly configured.

See this photo of a 1080p video taken with a camera (poor quality, but
illustrates the issue): https://ubuntucommunity.s3-us-

east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

Look at the sky’s light colours. They display with smooth gradients on
Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
video with a smaller range of white colours. This is the most apparent
with either very dark or very light colours. Even on window titlebars
the banding is visible (displayed as lines with different shades of
grey/black).

Compared with a PrtSc shot of the same image:
https://i.imgur.com/VkOSCaQ.png

The artefacts are not present on PrtSc shots that are taken on Ubuntu
18.04 but viewed on a different system (16.04 and Windows).

Installing a previous kernel version fixes the issue completely. I
used UKUU Update Utility to install kernel 4.4 (the same that I use in
Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
18.04 everything displayed smoothly. So this indicates that the system
might be using a sub-optimal colour depth with the newer kernel?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified:
boot/vmlinuz-4.13.0-32-generic]
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ystein 1344 F pulseaudio
/dev/snd/controlC1: ystein 1344 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 11:25:43 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
InstallationDate: Installed on 2018-02-12 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:07dc Intel Corp.
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-generic N/A
linux-backports-modules-4.13.0-32-generic N/A
linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LA
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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX303LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

To ma

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-03-23 Thread albertoiNET

I tried a lot of thing. Please see this topic for see the list that
things than doesn't work

https://askubuntu.com/questions/1010405/the-brightness-of-laptop-screen-
cannot-be-adjusted-with-either-the-buttons-or-th/1011557

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

Title:
  The brightness of the screen cannot be adjusted with either the
  buttons or the slider.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness is always at 100% and cannot be adjusted with either the FN
  brightness buttons or the Unity top bar slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  albertoinet   1199 F pulseaudio
   /dev/snd/controlC0:  albertoinet   1199 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 20:49:16 2018
  HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f
  InstallationDate: Installed on 2018-02-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. GT72VR 7RD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1785IMS.30E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1785
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.family: GT
  dmi.product.name: GT72VR 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

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

apport information

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

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1756455] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1756455/+attachment/5088491/+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/1756455

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1756455] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1756455/+attachment/5088498/+files/RfKill.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/1756455

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1756455/+attachment/5088489/+files/CRDA.txt

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux-signed
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1756455] Re: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery

apport information

** Tags added: apport-collected bionic

** Description changed:

  Ubuntu 18.04, installed from beta 1 ISO + all updates to date
  
  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.
  
  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.
  
- I am not attaching any logs because I cannot see anything unusual there,
- kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in
- fact, there is only one entry there "msr: Direct access to MSR 1b0").
- Please let me know what additional information you may need.
+ I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
+ --- 
+ ApportVersion: 2.20.8-0ubuntu10
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dmitry 1568 F pulseaudio
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
+ InstallationDate: Installed on 2018-03-10 (13 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: HP HP Spectre x360 Convertible 13-ae0xx
+ Package: linux-signed
+ ProcEnviron:
+  LANGUAGE=en_GB:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-12-generic N/A
+  linux-backports-modules-4.15.0-12-generic  N/A
+  linux-firmware 1.173
+ Tags:  bionic
+ Uname: Linux 4.15.0-12-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 02/22/2018
+ dmi.bios.vendor: AMI
+ dmi.bios.version: F.15
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 83B9
+ dmi.board.vendor: HP
+ dmi.board.version: 56.37
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV HP Spectre
+ dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
+ dmi.sys.vendor: HP

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

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual there, 
kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, 
there is only one entry there "msr: Direct access to MSR 1b0"). Please let me 
know what additional information you may need.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1568 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.

[Kernel-packages] [Bug 1755245] Re: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42

2018-03-23 Thread Colin Ian King

This failure was probably an OOM kill on the test, the stress-ng update
as mentioned in comment #2 will be able to identify these and not mark
them as a test failure.

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

Title:
  linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180309_144848_e1b37@/log.gz

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

2018-03-23 Thread Ryan Harper

Test kernel: GOOD

root@ubuntu:~# cat /proc/version_signature 
Ubuntu 4.13.0-37.42~lp1757565-generic 4.13.13
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /proc/mounts 
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir 
-p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.prod

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

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual
  there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be
  identical (in fact, there is only one entry there "msr: Direct access
  to MSR 1b0"). Please let me know what additional information you may
  need.

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

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

[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!

2018-03-23 Thread r.stricklin

Ok, that works. I should be able to provide basic validation much more
easily.

We are having trouble reproducing the crash with the unpatched kernel,
as we've put many remediating workarounds in place and it's been an
adventure to remember where they all are and how exactly they all
interacted (and also there are some other bugs currently being worked on
in our test environment that affect our ability to reproduce as well).
We know it will crash though, and as soon as we get the test setup in
place to reproduce the crash I'm confident we can repeat it every time
and get a good validation that the patch is solving our problem as well.

If we still can't reproduce the crash by COB Monday, I'll switch gears
to provide just a basic boot/function validation and will make sure I
get that to you by Tuesday at the latest.

We only have the environment to test xenial ppc64el. We have xenial and
trusty x86_64, but not with bnx2x. We don't have artful anywhere that I
can test with. Based on that, I was only planning to provide a report
for xenial ppc64el. Does the smoke testing make sense to perform without
bnx2x hardware present?

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

Title:
  bnx2x_attn_int_deasserted3:4323 MC assert!

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

Bug description:
  SRU Justification
  =

  A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
  card attached, and uses openvswitch to bridge an ibmveth interface for
  traffic from other LPARs.

  We see the following crash sometimes when running netperf:
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert!
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 
0x25e42a7e 0x00462a38 0x00010052
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump -
  ... (dump of registers follows) ...

  Subsequent debugging reveals that the packets causing the issue come
  through the ibmveth interface - from the AIX LPAR. The veth protocol
  is 'special' - communication between LPARs on the same chassis can use
  very large (64k) frames to reduce overhead. Normal networks cannot
  handle such large packets, so traditionally, the VIOS partition would
  signal to the AIX partitions that it was 'special', and AIX would send
  regular, ethernet-sized packets to VIOS, which VIOS would then send
  out.

  This signalling between VIOS and AIX is done in a way that is not
  standards-compliant, and so was never made part of Linux. Instead, the
  Linux driver has always understood large frames and passed them up the
  network stack.

  In some cases (e.g. with TCP), multiple TCP segments are coalesced
  into one large packet. In Linux, this goes through the generic receive
  offload code, using a similar mechanism to GSO. These segments can be
  very large which presents as a very large MSS (maximum segment size)
  or gso_size.

  Normally, the large packet is simply passed to whatever network
  application on Linux is going to consume it, and everything is OK.

  However, in this case, the packets go through Open vSwitch, and are
  then passed to the bnx2x driver. The bnx2x driver/hardware supports
  TSO and GSO, but with a restriction: the maximum segment size is
  limited to around 9700 bytes. Normally this is more than adequate.
  However, if a large packet with very large (>9700 byte) TCP segments
  arrives through ibmveth, and is passed to bnx2x, the hardware will
  panic.

  [Impact]

  bnx2x card panics, requiring power cycle to restore functionality.

  The workaround is turning off TSO, which prevents the crash as the
  kernel resegments *all* packets in software, not just ones that are
  too big. This has a performance cost.

  [Fix]

  Test packet size in bnx2x feature check path and disable GSO if it is
  too large. To do this we move a function from one file to another and
  add another in the networking core.

  [Regression Potential]

  A/B/X: The changes to the network core are easily reviewed. The changes to 
behaviour are limited to the bnx2x card driver.
  The most likely failure case is a false-positive on the size check, which 
would lead to a performance regression only.

  T: This also involves a different change to the

[Kernel-packages] [Bug 1756455] Re: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery

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

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

Title:
  Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360
  13-ae004 on battery

Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, installed from beta 1 ISO + all updates to date

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-12 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot. Booting with previous kernel 4.15.0-10 resolves the issue,
  system turns off power as expected.

  I am not attaching any logs because I cannot see anything unusual
  there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be
  identical (in fact, there is only one entry there "msr: Direct access
  to MSR 1b0"). Please let me know what additional information you may
  need.

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

I built an Artful test kernel with commit e3b8a48.  It also needed
commit f48bf66b6 as a prereq.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1757565

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

-- 
Maili

[Kernel-packages] [Bug 1750388] Re: 17.10 - BPF test tool build with errors

2018-03-23 Thread Steve Langasek

This bug report shows that you are using the clang-4.0 package from the
Ubuntu archive and that it fails to find architecture-specific headers
under /usr/include/s390x-linux-gnu, so that is certainly a valid bug in
that package.  However, clang is not a supported package in Ubuntu main.

In Ubuntu 18.04, the default version of clang is clang-6.0, not
clang-4.0.  Does this build work with clang-6.0?

** Package changed: linux (Ubuntu) => llvm-toolchain-4.0 (Ubuntu)

** Changed in: llvm-toolchain-4.0 (Ubuntu)
   Status: Invalid => New

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

Title:
  17.10 - BPF test tool build with errors

Status in Ubuntu on IBM z Systems:
  Triaged
Status in llvm-toolchain-4.0 package in Ubuntu:
  New

Bug description:
  Rebuild problem of BPFC test tool with Ubuntu 17.10

  uname -a
  Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 
s390x s390x s390x GNU/Linux

  cat ./etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.10
  DISTRIB_CODENAME=artful
  DISTRIB_DESCRIPTION="Ubuntu 17.10"
  root@s8360046:/#

  When I compile file test_pkt_access.c in directory
  linux/tools/testing/selftest/bpf I get a compile error.

  root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi 
-I../../../include/uapi  -Wno-compare-distinct-pointer-types  -O2 -target bpf 
-emit-llvm -c test_pkt_access.c -o - 
  In file included from test_pkt_access.c:8:
  /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not
found
  #include 
   ^~
  1 error generated.
  # 

  
  File bits/libc-header-start.h is located in directory 
/usr/include/s390x-linux-gnu which is not part of the include directory list:

  # find /usr/ -name libc-header-start.h
  /usr/include/s390x-linux-gnu/bits/libc-header-start.h
  # 

  
  When I add this directory to the include pathes of the compile, I get another 
error:

  # clang -I. -I./include/uapi -I../../../include/uapi 
-I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types  -O2 -target 
bpf -emit-llvm -c test_pkt_access.c -o - 
  In file included from test_pkt_access.c:12:
  In file included from /usr/include/linux/ip.h:20:
  In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4:
  In file included from /usr/include/linux/byteorder/big_endian.h:12:
  In file included from /usr/include/linux/swab.h:6:
  /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint
'=&d' in asm
  : "=&d" (result) : "Q" (*x) : "cc");
^
  /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint
'=&d' in asm
  : "=&d" (result) : "Q" (*x) : "cc");
^
  2 errors generated.

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

2018-03-23 Thread Ryan Harper

Yeah, rc2 was fine.

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1730770] Re: [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs

2018-03-23 Thread Kamal Mostafa

** Changed in: intel
   Status: Incomplete => In Progress

** Changed in: intel
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

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

Title:
  [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Description:

  Need to enable pmc_core driver for Coffee Lake so we can get at the
  slp_s0# counter, which measures S0ix residency.

  Target Kernel:4.16
  Target Release: 18.04

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

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

[Kernel-packages] [Bug 1739498] Re: Ubuntu 17.10 crashes on vmalloc.c

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

Title:
  Ubuntu 17.10 crashes on vmalloc.c

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM is seeing a crash on Power9 when running on Artful. 
  This issue happens only when disabling RPT ("disable_radix"), which is not 
the default in Artful.

  
  These fixes are already in Bionic master-next, so they are only being 
requested 
  in Artful.

  == Fixes ==
  63ee9b2ff9d3 ("powerpc/mm/book3s64: Make KERN_IO_START a variable")
  b5048de04b32 ("powerpc/mm/slb: Move comment next to the code it's")
  21a0e8c14bf6 ("powerpc/mm/hash64: Make vmalloc 56T on hash")

  == Regression Potential ==
  These commits are specific to powerpc and fix a crash.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  == Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
  When running Ubuntu 17.10 on POWER9, I got the following error:

  [409038.118908] WARNING: CPU: 47 PID: 294 at 
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
  [409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler 
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv 
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum 
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
ttm drm tg3 ahci libahci
  [409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW   
4.13.0-12-generic #13-Ubuntu
  [409038.118934] Workqueue: events pcpu_balance_workfn
  [409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
  [409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR: 

  [409038.118937] REGS: c03fe3be3810 TRAP: 0700   Tainted: GW   
 (4.13.0-12-generic)
  [409038.118938] MSR: 9282b033 
  [409038.118944]   CR: 24024828  XER: 2004
  [409038.118944] CFAR: c032bdb8 SOFTE: 1
  GPR00: 2df0 c03fe3be3a90 c15e3000 
c000203fff6b6880
  GPR04: c000203fff223608 0008 c000203fff6b6888 

  GPR08: 2df0 0800 0160 
c000203fff6b6888
  GPR12: 0002 cfaded80 c0f6c050 
c03fe3be3bc0
  GPR16: 0010  c189daf8 
c000203fff223608
  GPR20: 2f50 c000203fff2235f8 c000203fff223600 

  GPR24:  c000203fff6b6888 0001 
2f50
  GPR28: 0002 000f d800 
d000
  [409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
  [409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
  [409038.118965] Call Trace:
  [409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0 
(unreliable)
  [409038.118968] [c03fe3be3b60] [c02f5fd4] 
pcpu_create_chunk+0xb4/0x1b0
  [409038.118970] [c03fe3be3ba0] [c02f7890] 
pcpu_balance_workfn+0x600/0x960
  [409038.118972] [c03fe3be3ca0] [c01205d8] 
process_one_work+0x298/0x5a0
  [409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
  [409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
  [409038.118979] [c03fe3be3e30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [409038.118980] Instruction dump:
  [409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 
3b40 e953

  ---uname output---
  4.13.0-12-generic

  == Comment: #3 - ANEESH K. K V  - 2017-12-20 05:59:13 ==
  https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au

  The above may be related?

  Related discussions
  https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz

  -aneesh

  == Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
  I just tested with kernel 4.15.0-041500rc4 and I didn't see a problem so far.

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

-- 
Mailing list:

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

Title:
  [Acer AO532h] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I put the computer in hibernation using sudo pm-hibernate. Computer
  seemed to go into hibernation normally but didn't wake up properly.
  System hibernates properly under Artful. Disk has a proper 2gb swap
  partition.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ka1ssr 1005 F pulseaudio
  Date: Fri Mar 23 12:36:52 2018
  DuplicateSignature: hibernate/resume:Acer AO532h:V1.26
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Acer AO532h
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [Acer AO532h] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/28/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AO532h
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.26
  dmi.modalias: 
dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26:
  dmi.product.family: Intel_Mobile
  dmi.product.name: AO532h
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1745508] Re: Please backport vmd suspend/resume patches to 16.04 hwe

2018-03-23 Thread Jonathan Derrick

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

Title:
  Please backport vmd suspend/resume patches to 16.04 hwe

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

Bug description:
  == SRU Justification ==

  This bug was opened to request commit e2b1820bd5d0 be backported from 4.14 to
  the 4.13 kernel in Artful.  Without this patch, servers with VMD enabled 
  run into issues suspending and resuming.

  Commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f is in mainline as of
  v4.14-rc1.


  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
  PCI: vmd: Free up IRQs on suspend path

  [Impact]
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming

  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

  [Regression Potential]
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

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

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

[Kernel-packages] [Bug 1758384] Re: [Acer AO532h] hibernate/resume failure

2018-03-23 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/1758384

Title:
  [Acer AO532h] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I put the computer in hibernation using sudo pm-hibernate. Computer
  seemed to go into hibernation normally but didn't wake up properly.
  System hibernates properly under Artful. Disk has a proper 2gb swap
  partition.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ka1ssr 1005 F pulseaudio
  Date: Fri Mar 23 12:36:52 2018
  DuplicateSignature: hibernate/resume:Acer AO532h:V1.26
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Acer AO532h
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [Acer AO532h] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/28/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AO532h
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.26
  dmi.modalias: 
dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26:
  dmi.product.family: Intel_Mobile
  dmi.product.name: AO532h
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1758384] [NEW] [Acer AO532h] hibernate/resume failure

2018-03-23 Thread Bill Hammond

Public bug reported:

I put the computer in hibernation using sudo pm-hibernate. Computer
seemed to go into hibernation normally but didn't wake up properly.
System hibernates properly under Artful. Disk has a proper 2gb swap
partition.

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ka1ssr 1005 F pulseaudio
Date: Fri Mar 23 12:36:52 2018
DuplicateSignature: hibernate/resume:Acer AO532h:V1.26
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e
InstallationDate: Installed on 2018-03-23 (0 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
InterpreterPath: /usr/bin/python3.6
MachineType: Acer AO532h
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-12-generic N/A
 linux-backports-modules-4.15.0-12-generic  N/A
 linux-firmware 1.173
SourcePackage: linux
Title: [Acer AO532h] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/28/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AO532h
dmi.board.vendor: Acer
dmi.board.version: V1.26
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.26
dmi.modalias: 
dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26:
dmi.product.family: Intel_Mobile
dmi.product.name: AO532h
dmi.product.version: V1.26
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-kerneloops bionic hibernate resume

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

Title:
  [Acer AO532h] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I put the computer in hibernation using sudo pm-hibernate. Computer
  seemed to go into hibernation normally but didn't wake up properly.
  System hibernates properly under Artful. Disk has a proper 2gb swap
  partition.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ka1ssr 1005 F pulseaudio
  Date: Fri Mar 23 12:36:52 2018
  DuplicateSignature: hibernate/resume:Acer AO532h:V1.26
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Acer AO532h
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173

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

2018-03-23 Thread bugproxy

--- Comment From frede...@fr.ibm.com 2018-03-23 12:29 EDT---
Hi,
I got my hands on a WS system and could boot kernel 4.13.0-38.43 with 
disable_radix kernel option
and I confirm that this issue does not appear anymore.
(I checked before that I actually got it with 4.13.0-37.42)

Regards,

F.

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

Title:
  Ubuntu 17.10 crashes on vmalloc.c

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM is seeing a crash on Power9 when running on Artful. 
  This issue happens only when disabling RPT ("disable_radix"), which is not 
the default in Artful.

  
  These fixes are already in Bionic master-next, so they are only being 
requested 
  in Artful.

  == Fixes ==
  63ee9b2ff9d3 ("powerpc/mm/book3s64: Make KERN_IO_START a variable")
  b5048de04b32 ("powerpc/mm/slb: Move comment next to the code it's")
  21a0e8c14bf6 ("powerpc/mm/hash64: Make vmalloc 56T on hash")

  == Regression Potential ==
  These commits are specific to powerpc and fix a crash.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  == Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
  When running Ubuntu 17.10 on POWER9, I got the following error:

  [409038.118908] WARNING: CPU: 47 PID: 294 at 
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
  [409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler 
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv 
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum 
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
ttm drm tg3 ahci libahci
  [409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW   
4.13.0-12-generic #13-Ubuntu
  [409038.118934] Workqueue: events pcpu_balance_workfn
  [409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
  [409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR: 

  [409038.118937] REGS: c03fe3be3810 TRAP: 0700   Tainted: GW   
 (4.13.0-12-generic)
  [409038.118938] MSR: 9282b033 
  [409038.118944]   CR: 24024828  XER: 2004
  [409038.118944] CFAR: c032bdb8 SOFTE: 1
  GPR00: 2df0 c03fe3be3a90 c15e3000 
c000203fff6b6880
  GPR04: c000203fff223608 0008 c000203fff6b6888 

  GPR08: 2df0 0800 0160 
c000203fff6b6888
  GPR12: 0002 cfaded80 c0f6c050 
c03fe3be3bc0
  GPR16: 0010  c189daf8 
c000203fff223608
  GPR20: 2f50 c000203fff2235f8 c000203fff223600 

  GPR24:  c000203fff6b6888 0001 
2f50
  GPR28: 0002 000f d800 
d000
  [409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
  [409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
  [409038.118965] Call Trace:
  [409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0 
(unreliable)
  [409038.118968] [c03fe3be3b60] [c02f5fd4] 
pcpu_create_chunk+0xb4/0x1b0
  [409038.118970] [c03fe3be3ba0] [c02f7890] 
pcpu_balance_workfn+0x600/0x960
  [409038.118972] [c03fe3be3ca0] [c01205d8] 
process_one_work+0x298/0x5a0
  [409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
  [409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
  [409038.118979] [c03fe3be3e30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [409038.118980] Instruction dump:
  [409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 
3b40 e953

  ---uname output---
  4.13.0-12-generic

  == Comment: #3 - ANEESH K. K V  - 2017-12-20 05:59:13 ==
  https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au

  The above may be related?

  Related discussions
  https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz

  -aneesh

  == Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
  I j

[Kernel-packages] [Bug 1755509] Re: Xenial update to 4.4.115 stable release

2018-03-23 Thread Kleber Sacilotto de Souza

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

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

Title:
  Xenial update to 4.4.115 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.115 stable release shall be
     applied:

 * loop: fix concurrent lo_open/lo_release
 * bpf: fix branch pruning logic
 * x86: bpf_jit: small optimization in emit_bpf_tail_call()
 * bpf: fix bpf_tail_call() x64 JIT
 * bpf: introduce BPF_JIT_ALWAYS_ON config
 * bpf: arsh is not supported in 32 bit alu thus reject it
 * bpf: avoid false sharing of map refcount with max_entries
 * bpf: fix divides by zero
 * bpf: fix 32-bit divide by zero
 * bpf: reject stores into ctx via st and xadd
 * x86/pti: Make unpoison of pgd for trusted boot work for real
 * kaiser: fix intel_bts perf crashes
 * ALSA: seq: Make ioctls race-free
 * crypto: aesni - handle zero length dst buffer
 * crypto: af_alg - whitelist mask and type
 * power: reset: zx-reboot: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
 * gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
 * gpio: ath79: add missing MODULE_DESCRIPTION/LICENSE
 * mtd: nand: denali_pci: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
 * igb: Free IRQs when device is hotplugged
 * KVM: x86: emulator: Return to user-mode on L1 CPL=0 emulation failure
 * KVM: x86: Don't re-execute instruction when not passing CR2 value
 * KVM: X86: Fix operand/address-size during instruction decoding
 * KVM: x86: ioapic: Fix level-triggered EOI and IOAPIC reconfigure race
 * KVM: x86: ioapic: Clear Remote IRR when entry is switched to 
edge-triggered
 * KVM: x86: ioapic: Preserve read-only values in the redirection table
 * ACPI / bus: Leave modalias empty for devices which are not present
 * cpufreq: Add Loongson machine dependencies
 * bcache: check return value of register_shrinker
 * drm/amdgpu: Fix SDMA load/unload sequence on HWS disabled mode
 * drm/amdkfd: Fix SDMA ring buffer size calculation
 * drm/amdkfd: Fix SDMA oversubsription handling
 * openvswitch: fix the incorrect flow action alloc size
 * mac80211: fix the update of path metric for RANN frame
 * btrfs: fix deadlock when writing out space cache
 * KVM: VMX: Fix rflags cache during vCPU reset
 * xen-netfront: remove warning when unloading module
 * nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0)
 * nfsd: Ensure we check stateid validity in the seqid operation checks
 * grace: replace BUG_ON by WARN_ONCE in exit_net hook
 * nfsd: check for use of the closed special stateid
 * lockd: fix "list_add double add" caused by legacy signal interface
 * hwmon: (pmbus) Use 64bit math for DIRECT format values
 * net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit
 * quota: Check for register_shrinker() failure.
 * SUNRPC: Allow connect to return EHOSTUNREACH
 * kmemleak: add scheduling point to kmemleak_scan()
 * drm/omap: Fix error handling path in 'omap_dmm_probe()'
 * xfs: ubsan fixes
 * scsi: aacraid: Prevent crash in case of free interrupt during scsi EH 
path
 * scsi: ufs: ufshcd: fix potential NULL pointer dereference in 
ufshcd_config_vreg
 * media: usbtv: add a new usbid
 * usb: gadget: don't dereference g until after it has been null checked
 * staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID
 * usb: option: Add support for FS040U modem
 * USB: serial: pl2303: new device id for Chilitag
 * USB: cdc-acm: Do not log urb submission errors on disconnect
 * CDC-ACM: apply quirk for card reader
 * USB: serial: io_edgeport: fix possible sleep-in-atomic
 * usbip: prevent bind loops on devices attached to vhci_hcd
 * usbip: list: don't list devices attached to vhci_hcd
 * USB: serial: simple: add Motorola Tetra driver
 * usb: f_fs: Prevent gadget unbind if it is already unbound
 * usb: uas: unconditionally bring back host after reset
 * selinux: general protection fault in sock_has_perm
 * serial: imx: Only wakeup via RTSDEN bit if the system has RTS/CTS
 * spi: imx: do not access

[Kernel-packages] [Bug 1756121] Re: Xenial update to 4.4.116 stable release

2018-03-23 Thread Kleber Sacilotto de Souza

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

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

Title:
  Xenial update to 4.4.116 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.116 stable release shall be
 applied:

 * Linux 4.4.116
 * ftrace: Remove incorrect setting of glob search field
 * mn10300/misalignment: Use SIGSEGV SEGV_MAPERR to report a failed user 
copy
 * ovl: fix failure to fsync lower dir
 * ACPI: sbshc: remove raw pointer from printk() message
 * nvme: Fix managing degraded controllers
 * btrfs: Handle btrfs_set_extent_delalloc failure in fixup worker
 * pktcdvd: Fix pkt_setup_dev() error path
 * EDAC, octeon: Fix an uninitialized variable warning
 * xtensa: fix futex_atomic_cmpxchg_inatomic
 * alpha: fix reboot on Avanti platform
 * alpha: fix crash if pthread_create races with signal delivery
 * signal/sh: Ensure si_signo is initialized in do_divide_error
 * signal/openrisc: Fix do_unaligned_access to send the proper signal
 * Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" 
version
 * Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"
 * Bluetooth: btsdio: Do not bind to non-removable BCM43341
 * HID: quirks: Fix keyboard + touchpad on Toshiba Click Mini not working
 * kernel/async.c: revert "async: simplify lowest_in_progress()"
 * media: cxusb, dib0700: ignore XC2028_I2C_FLUSH
 * media: ts2020: avoid integer overflows on 32 bit machines
 * watchdog: imx2_wdt: restore previous timeout after suspend+resume
 * KVM: nVMX: Fix races when sending nested PI while dest enters/leaves L2
 * arm: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls
 * crypto: caam - fix endless loop when DECO acquire fails
 * media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic
 * media: v4l2-compat-ioctl32.c: don't copy back the result for certain 
errors
 * media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type
 * media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32
 * media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha
 * media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs
 * media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer
 * media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32
 * media: v4l2-compat-ioctl32.c: avoid sizeof(type)
 * media: v4l2-compat-ioctl32.c: move 'helper' functions to 
__get/put_v4l2_format32
 * media: v4l2-compat-ioctl32.c: fix the indentation
 * media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF
 * vb2: V4L2_BUF_FLAG_DONE is set after DQBUF
 * media: v4l2-ioctl.c: don't copy back the result for -ENOTTY
 * nsfs: mark dentry with DCACHE_RCUACCESS
 * crypto: poly1305 - remove ->setkey() method
 * crypto: cryptd - pass through absence of ->setkey()
 * crypto: hash - introduce crypto_hash_alg_has_setkey()
 * ahci: Add Intel Cannon Lake PCH-H PCI ID
 * ahci: Add PCI ids for Intel Bay Trail, Cherry Trail and Apollo Lake AHCI
 * ahci: Annotate PCI ids for mobile Intel chipsets as such
 * kernfs: fix regression in kernfs_fop_write caused by wrong type
 * NFS: reject request for id_legacy key without auxdata
 * NFS: commit direct writes even if they fail partially
 * NFS: Add a cond_resched() to nfs_commit_release_pages()
 * nfs/pnfs: fix nfs_direct_req ref leak when i/o falls back to the mds
 * ubi: block: Fix locking for idr_alloc/idr_remove
 * mtd: nand: sunxi: Fix ECC strength choice
 * mtd: nand: Fix nand_do_read_oob() return value
 * mtd: nand: brcmnand: Disable prefetch by default
 * mtd: cfi: convert inline functions to macros
 * media: dvb-usb-v2: lmedm04: move ts2020 attach to dm04_lme2510_tuner
 * media: dvb-usb-v2: lmedm04: Improve logic checking of warm start
 * dccp: CVE-2017-8824: use-after-free in DCCP code
 * sched/rt: Up the root domain ref count when passing it around via IPIs
 * sched/rt: Use container_of() to get root domain in 
rto_push_irq_work_func()
 * usb: gadget: uvc: Missing files for configfs interface
 * posix-timer: Properly

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

2018-03-23 Thread Launchpad Bug Tracker

** Merge proposal linked:
   https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/341982

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT

2018-03-23 Thread Timo Aaltonen

** Changed in: amd
   Status: Confirmed => 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/1742759

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16&id=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

It looks like that commit landed in -rc3:

git describe --contains e3b8a48
v4.15-rc3~3^2~11

However, -rc2 is good, correct?  I'll have a look at the other btrfs
commits in -rc2 and see if any stick out.

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

Hmm, even though git describe returns that tag, it seem s-rc2 has that
commit.

I'll still build an Artful test kernel with that commit to see if it
fixes the bug and figure out the tagging in the background.

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Triaged
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in tar source package in Artful:
  New

Bug description:
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts 
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  
  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/ 
  https://www.spinics.net/lists/linux-btrfs/msg56768.html 
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+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 1758375] [NEW] efifb broken on ThunderX-based Gigabyte nodes