[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-02-05 Thread Bib
Just tried : neither this issue with Trusty K4.4.0-112 nor K4.15.1 real 
installs.
Only met it with Bionic-dev-Live-K4

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  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.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM-E35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Bib
https://bugs.freedesktop.org/show_bug.cgi?id=104963

** Bug watch added: freedesktop.org Bugzilla #104963
   https://bugs.freedesktop.org/show_bug.cgi?id=104963

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

Title:
  Boot loop MSI A88XM-E35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-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-02-05 Thread Daniel Axtens
** Description changed:

  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.
+ Test packet size in bnx2x feature check path and disable GSO if it is
+ too large.
  
  Regression Potential
  
  
  Limited to bnx2x card driver.
  The most likely failure case is a false-positive on the size check, which 
would lead to a performance regression only.

-- 
You 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:
  Confirmed

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 

[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM-E35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Bib
** Summary changed:

- Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)
+ Boot loop MSI A88XM-E35 AMD APU A8-5600K (Aruba HD7560D)

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

Title:
  Boot loop MSI A88XM-E35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Bib
Kai-Heng, it seems you have a bug. Both videos play fine here with
firefox or VLC or Totem.

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-02-05 Thread Kai-Heng Feng
Do you have the issue on Trusty with Linux kernel v4.15?

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  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.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1747563] Re: Ubuntu18.04[P9, Boston]: while booting system with disable_radix as kernel boot parameter continuous cpu warn on seen in console

2018-02-05 Thread Frank Heimes
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

** Tags added: triage-g

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

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

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

Title:
  Ubuntu18.04[P9, Boston]: while booting system with disable_radix as
  kernel boot parameter   continuous  cpu warn on seen in console

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

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-01-16 
02:38:52 ==
  Problem Description :

   while booting Power9 Boston as ubuntu18.04  system with disable_radix
  as kernel boot parameter   continuous  cpu warn on seen in console

  Steps to reproduce:
  1- install P9 system with ubuntu 18.04
  2-  boot system with disable_radix as kernel boot parameter

  LOG:

  0
  [   47.953357] [c00febc3be30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [   47.953358] Instruction dump:
  [   47.953358] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 3b40 
e953 
  [   47.953360] 7d3f4850 7f7b5214 7fa9d840 409cfbc4 <0fe0> 3ae0 
4bfffcd4 7c0004ac 
  [   47.953363] ---[ end trace 69b8c2ab7570cdbf ]---
  [   47.953561] [ cut here ]
  [   47.953562] WARNING: CPU: 23 PID: 995 at 
/build/linux-268tGw/linux-4.13.0/mm/vmalloc.c:2521 pcpu_get_vm_areas+0x62c/0x660
  [   47.953563] Modules linked in: hid_generic crc32c_vpmsum ast i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm usbhid hid 
aac
  raid i40e(+)
  [   47.953567] CPU: 23 PID: 995 Comm: kworker/23:1 Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [   47.953569] Workqueue: events pcpu_balance_workfn
  [   47.953570] task: c00febb97000 task.stack: c00febc38000
  [   47.953570] NIP: c032fedc LR: c02f9c54 CTR: 

  [   47.953571] REGS: c00febc3b800 TRAP: 0700   Tainted: GW
(4.13.0-25-generic)
  [   47.953571] MSR: 92029033 
  [   47.953574]   CR: 24024828  XER: 2004
  [   47.953574] CFAR: c032fa98 SOFTE: 1 
  [   47.953574] GPR00: 21e0 c00febc3ba80 c15f6200 
c000200fff6da480 
  [   47.953574] GPR04: c000200fff356c08 0008 c000200fff6da488 
 
  [   47.953574] GPR08: 21e0 0800 0140 
c000200fff6da488 
  [   47.953574] GPR12: 0002 cfacf180 c0f7dbe0 
c00febc3bbb0 
  [   47.953574] GPR16: 0010  c18adff8 
c000200fff356c08 
  [   47.953574] GPR20: 2320 c000200fff356bf8 c000200fff356c00 
 
  [   47.953574] GPR24:  c000200fff6da488 0001 
2320 
  [   47.953574] GPR28: 0002 000f d800 
d000 
  [

  
  [   47.960515] GPR00: 21e0 c00febc5ba80 c15f6200 
c000200fff6da480 
  [   47.960515] GPR04: c000200fff356c08 0008 c000200fff6da488 
 
  [   47.960515] GPR08: 21e0 0800 0140 
c000200fff6da488 
  [   47.960515] GPR12: 0002 cfacdc80 c0f7dbe0 
c00febc5bbb0 
  [   47.960515] GPR16: 0010  c18adff8 
c000200fff356c08 
  [   47.960515] GPR20: 2320 c000200fff356bf8 c000200fff356c00 
 
  [   47.960515] GPR24:  c000200fff6da488 0001 
2320 
  [   47.960515] GPR28: 0002 000f d800 
d000 
  [   47.960527] NIP [c032fedc] pcpu_get_vm_areas+0x62c/0x660
  [   47.960528] LR [c02f9c54] pcpu_create_chunk+0xb4/0x1b0
  [   47.960528] Call Trace:
  [   47.960529] [c00febc5ba80] [c00febc5bac0] 0xc00febc5bac0 
(unreliable)
  [   47.960531] [c00febc5bb50] [c02f9c54] 
pcpu_create_chunk+0xb4/0x1b0
  [   47.960532] [c00febc5bb90] [c02fb510] 
pcpu_balance_workfn+0x600/0x960
  [   47.960534] [c00febc5bc90] [c0124018] 
process_one_work+0x298/0x5a0
  [   47.960536] [c00febc5bd20] [c01243a8] worker_thread+0x88/0x620
  [   47.960537] [c00febc5bdc0] [c012d21c] kthread+0x1ac/0x1c0
  [   47.960539] [c00febc5be30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [   47.960539] Instruction dump:
  [   47.960540] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 3b40 
e953 
  [   47.960542] 7d3f4850 7f7b5214 7fa9d840 409cfbc4 

[Kernel-packages] [Bug 1747563] [NEW] Ubuntu18.04[P9, Boston]: while booting system with disable_radix as kernel boot parameter continuous cpu warn on seen in console

2018-02-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #0 - Praveen K. Pandey  - 2018-01-16 
02:38:52 ==
Problem Description :

 while booting Power9 Boston as ubuntu18.04  system with disable_radix
as kernel boot parameter   continuous  cpu warn on seen in console

Steps to reproduce:
1- install P9 system with ubuntu 18.04
2-  boot system with disable_radix as kernel boot parameter

LOG:

0
[   47.953357] [c00febc3be30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
[   47.953358] Instruction dump:
[   47.953358] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 3b40 
e953 
[   47.953360] 7d3f4850 7f7b5214 7fa9d840 409cfbc4 <0fe0> 3ae0 4bfffcd4 
7c0004ac 
[   47.953363] ---[ end trace 69b8c2ab7570cdbf ]---
[   47.953561] [ cut here ]
[   47.953562] WARNING: CPU: 23 PID: 995 at 
/build/linux-268tGw/linux-4.13.0/mm/vmalloc.c:2521 pcpu_get_vm_areas+0x62c/0x660
[   47.953563] Modules linked in: hid_generic crc32c_vpmsum ast i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm usbhid hid 
aac
raid i40e(+)
[   47.953567] CPU: 23 PID: 995 Comm: kworker/23:1 Tainted: GW   
4.13.0-25-generic #29-Ubuntu
[   47.953569] Workqueue: events pcpu_balance_workfn
[   47.953570] task: c00febb97000 task.stack: c00febc38000
[   47.953570] NIP: c032fedc LR: c02f9c54 CTR: 
[   47.953571] REGS: c00febc3b800 TRAP: 0700   Tainted: GW
(4.13.0-25-generic)
[   47.953571] MSR: 92029033 
[   47.953574]   CR: 24024828  XER: 2004
[   47.953574] CFAR: c032fa98 SOFTE: 1 
[   47.953574] GPR00: 21e0 c00febc3ba80 c15f6200 
c000200fff6da480 
[   47.953574] GPR04: c000200fff356c08 0008 c000200fff6da488 
 
[   47.953574] GPR08: 21e0 0800 0140 
c000200fff6da488 
[   47.953574] GPR12: 0002 cfacf180 c0f7dbe0 
c00febc3bbb0 
[   47.953574] GPR16: 0010  c18adff8 
c000200fff356c08 
[   47.953574] GPR20: 2320 c000200fff356bf8 c000200fff356c00 
 
[   47.953574] GPR24:  c000200fff6da488 0001 
2320 
[   47.953574] GPR28: 0002 000f d800 
d000 
[


[   47.960515] GPR00: 21e0 c00febc5ba80 c15f6200 
c000200fff6da480 
[   47.960515] GPR04: c000200fff356c08 0008 c000200fff6da488 
 
[   47.960515] GPR08: 21e0 0800 0140 
c000200fff6da488 
[   47.960515] GPR12: 0002 cfacdc80 c0f7dbe0 
c00febc5bbb0 
[   47.960515] GPR16: 0010  c18adff8 
c000200fff356c08 
[   47.960515] GPR20: 2320 c000200fff356bf8 c000200fff356c00 
 
[   47.960515] GPR24:  c000200fff6da488 0001 
2320 
[   47.960515] GPR28: 0002 000f d800 
d000 
[   47.960527] NIP [c032fedc] pcpu_get_vm_areas+0x62c/0x660
[   47.960528] LR [c02f9c54] pcpu_create_chunk+0xb4/0x1b0
[   47.960528] Call Trace:
[   47.960529] [c00febc5ba80] [c00febc5bac0] 0xc00febc5bac0 
(unreliable)
[   47.960531] [c00febc5bb50] [c02f9c54] 
pcpu_create_chunk+0xb4/0x1b0
[   47.960532] [c00febc5bb90] [c02fb510] 
pcpu_balance_workfn+0x600/0x960
[   47.960534] [c00febc5bc90] [c0124018] 
process_one_work+0x298/0x5a0
[   47.960536] [c00febc5bd20] [c01243a8] worker_thread+0x88/0x620
[   47.960537] [c00febc5bdc0] [c012d21c] kthread+0x1ac/0x1c0
[   47.960539] [c00febc5be30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
[   47.960539] Instruction dump:
[   47.960540] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 3b40 
e953 
[   47.960542] 7d3f4850 7f7b5214 7fa9d840 409cfbc4 <0fe0> 3ae0 4bfffcd4 
7c0004ac 
[   47.960545] ---[ end trace 69b8c2ab7570ce02 ]---
[   47.960554] [ cut here ]
[   47.960556] WARNING: CPU: 21 PID: 994 at 
/build/linux-268tGw/linux-4.13.0/mm/vmalloc.c:2521 pcpu_get_vm_areas+0x62c/0x660
[   47.960556] Modules linked in: hid_generic crc32c_vpmsum ast i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm usbhid hid 
aacraid i40e(+)
[   47.960561] CPU: 21 PID: 994 Comm: kworker/21:1 Tainted: GW   
4.13.0-25-generic #29-Ubuntu
[   47.960562] Workqueue: events pcpu_balance_workfn
[   47.960563] task: c00febba1100 task.stack: c00febc58000
[   47.960564] NIP: c032fedc LR: c02f9c54 CTR: 
[   47.960564] REGS: c00febc5b800 TRAP: 0700   Tainted: GW
(4.13.0-25-generic)
[   47.960565] MSR: 92029033 

[Kernel-packages] [Bug 1637709] Re: Lenovo Ideapad 100 webcam always on

2018-02-05 Thread Kai-Heng Feng
When does the LED turn on during boot? Before or after GRUB?

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

Title:
  Lenovo Ideapad 100 webcam always on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovo Ideapad 100 model 15IBD 80 QQ
  The webcam led it stays always on from when i start the pc, it stops only, it 
seems, when i open some software that has a working with it in some way...like  
software or even google chrome (i think thanks to hangouts)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1361 F pulseaudio
   /dev/snd/controlC1:  ale1361 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=39a50866-e309-4acc-b70f-19f745ab0c9e
  InstallationDate: Installed on 2016-10-22 (6 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80QQ
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=86cd71e4-1562-488f-afa6-290f354d4f7a ro
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN61WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 5B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN61WW:bd08/12/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
  dmi.product.name: 80QQ
  dmi.product.version: Lenovo ideapad 100-15IBD
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2018-02-05 Thread Kai-Heng Feng
Does the issue happen after system suspend?

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 

[Kernel-packages] [Bug 1722677] Re: Touch Screen NOT working

2018-02-05 Thread Kai-Heng Feng
Please try this kernel,

people.canonical.com/~khfeng/lp1728244-2/

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

Title:
  Touch Screen NOT working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. 
  Touchscreen does not work after installing OS from live USB. It did not work 
on USB either. There is zero touchscreen functionality.

  Workaroud: Must put computer to sleep, and then wake from sleep for
  touchscreen to work.

  Please Note: In this edition of 17.10, tilt sensors work perfectly
  without having to put the computer to sleep (an old bug). Also note,
  wifi works perfectly after resuming from sleep (another old bug fixed
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  troll  1255 F pulseaudio
   /dev/snd/controlC0:  troll  1255 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 18:54:29 2017
  InstallationDate: Installed on 2017-09-30 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Venue 11 Pro 7139
  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-15-generic.efi.signed 
root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0RFDKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-02-05 Thread Kai-Heng Feng
Please try this kernel,

people.canonical.com/~khfeng/lp1728244-2/

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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


[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Kai-Heng Feng
Unfortunately, I can't play any video you attached

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1747421] Re: Bluetooth does not start (and also recurring "pcieport 0000:00:1c.5: PCIe Bus Error: ")

2018-02-05 Thread Daniel van Vugt
That means downloading and installing packages from here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

or more specifically, try installing these three packages together:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-
headers-4.15.1-041501_4.15.1-041501.201802031831_all.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-
headers-4.15.1-041501-generic_4.15.1-041501.201802031831_amd64.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-
image-4.15.1-041501-generic_4.15.1-041501.201802031831_amd64.deb

** Summary changed:

- Bluetooth does not start (and also recurring "pcieport :00:1c.5: PCIe Bus 
Error: ")
+ [rtl8723be] Bluetooth does not start (and also recurring "pcieport 
:00:1c.5: PCIe Bus Error: ")

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

Title:
  [rtl8723be] Bluetooth does not start (and also recurring "pcieport
  :00:1c.5: PCIe Bus Error: ")

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth does not start turn it on and notting happens 
  i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


  
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
  14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
  14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
  14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@Laurentiu:/home/laufer# apt-cache policy bluez
  bluez:
Installed: 5.46-0ubuntu3
Candidate: 5.46-0ubuntu3
Version table:
   *** 5.46-0ubuntu3 500
  500 http://ro.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  root@Laurentiu:/home/laufer#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  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
  Date: Mon Feb  5 15:00:42 2018
  InstallationDate: Installed on 2018-02-04 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=87b1ca1a-1586-47e4-83a2-c81e7e67ca79 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  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.:bvrX541UVK.304:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 64:6E:69:20:D4:7E  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1225 acl:0 sco:0 events:122 errors:0
TX bytes:23230 acl:0 sco:0 commands:124 errors:0

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

-- 
Mailing list: https://launchpad.net/~kernel-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-02-05 Thread Daniel Axtens
** Description changed:

- (This bug provides a place to track the progress of this issue upstream
- and then in to Ubuntu.)
+ 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 - 
+ 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 as jumbo frames
- are limited to 9000 bytes. However, if a large packet with large (>9700
- byte) TCP segments arrives through ibmveth, and is passed to bnx2x, the
- hardware will panic.
+ 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.
  
- Turning off TSO prevents the crash as the kernel resegments the data and
- assembles the packets in software. This has a performance cost.
+ Impact
+ --
  
- Clearly at the very least, bnx2x should not crash in this case.
+ bnx2x card panics, requiring power cycle to restore functionality.
  
- One patch to do this was sent upstream:
- https://www.spinics.net/lists/netdev/msg452932.html
+ 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.
+ 
+ Regression Potential
+ 
+ 
+ Limited to bnx2x card driver.
+ The most likely failure case is a false-positive on the size check, which 
would lead to a performance regression only.

-- 
You 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:
  Confirmed

Bug description:
  SRU Justification
  =

  A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
  card attached, and uses openvswitch 

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

2018-02-05 Thread Daniel Axtens
A set of 2 patches to fix this was accepted upstream:

https://github.com/torvalds/linux/commit/2b16f048729bf35e6c28a40cbfad07239f9dcd90
https://github.com/torvalds/linux/commit/8914a595110a6eca69a5e275b323f5d09e18f4f9

I will send an SRU shortly.

-- 
You 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:
  Confirmed

Bug description:
  (This bug provides a place to track the progress of this issue
  upstream and then in to Ubuntu.)

  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 as
  jumbo frames are limited to 9000 bytes. However, if a large packet
  with large (>9700 byte) TCP segments arrives through ibmveth, and is
  passed to bnx2x, the hardware will panic.

  Turning off TSO prevents the crash as the kernel resegments the data
  and assembles the packets in software. This has a performance cost.

  Clearly at the very least, bnx2x should not crash in this case.

  One patch to do this was sent upstream:
  https://www.spinics.net/lists/netdev/msg452932.html

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 1747421] Re: Bluetooth does not start (and also recurring "pcieport 0000:00:1c.5: PCIe Bus Error: ")

2018-02-05 Thread Kai-Heng Feng
Please try latest mainline kernel, the btusb issue might gets fixed.

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

Title:
  Bluetooth does not start (and also recurring "pcieport :00:1c.5:
  PCIe Bus Error: ")

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth does not start turn it on and notting happens 
  i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


  
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
  14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
  14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
  14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@Laurentiu:/home/laufer# apt-cache policy bluez
  bluez:
Installed: 5.46-0ubuntu3
Candidate: 5.46-0ubuntu3
Version table:
   *** 5.46-0ubuntu3 500
  500 http://ro.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  root@Laurentiu:/home/laufer#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  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
  Date: Mon Feb  5 15:00:42 2018
  InstallationDate: Installed on 2018-02-04 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=87b1ca1a-1586-47e4-83a2-c81e7e67ca79 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  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.:bvrX541UVK.304:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 64:6E:69:20:D4:7E  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1225 acl:0 sco:0 events:122 errors:0
TX bytes:23230 acl:0 sco:0 commands:124 errors:0

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

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


[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2018-02-05 Thread Lucas Zanella
I found a guy with same problem as mine and had a Razer Blade Stealth,
but he didn't post anything more after that. And he was in a thread with
you. I also found some people with this same problem on the same SSD.
Together with the fact that I had no problem on windows (ore than 24hrs
of usage by now) I think it can be fixed in the kernel.

I had no luck updating my SSD's firmware as it's OEM and Samsung's
updater won't work for it. Do you have any idea? I don't have money to
buy a new SSD, and I really need to work. I'd be so grateful if you
could help with a solution.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

2018-02-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1747488

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


** Summary changed:

- 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
+ [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting 
"EFI VGA"

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747488/+subscriptions

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


[Kernel-packages] [Bug 1747492] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering

2018-02-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1747492

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


** Summary changed:

- 17.10.1 DisplayPort 15m cable monitor flickering 
+ [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing 17.10.1, plugging in the 15m DisplayPort cable, it
  works, however, there is an unusable amount of screen tearing and
  flickering, and pixelated lines across the screen

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

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


[Kernel-packages] [Bug 1747421] Re: Bluetooth does not start

2018-02-05 Thread Daniel van Vugt
It appears you have recurring "pcieport" errors in your kernel log (see
CurrentDmesg.txt and JournalErrors.txt).

This looks like a hardware fault (I've had the same issue myself... with
a faulty PCIe card slot). But in case it's not a hardware fault, let's
start by assigning the issue to the Linux kernel.

P.S. You will also need to have package 'linux-firmware' installed. So
in case that makes a difference, please try 'sudo apt install linux-
firmware' and then reboot.


** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

** Summary changed:

- Bluetooth does not start
+ Bluetooth does not start (and also recurring "pcieport :00:1c.5: PCIe Bus 
Error: ")

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

Title:
  Bluetooth does not start (and also recurring "pcieport :00:1c.5:
  PCIe Bus Error: ")

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth does not start turn it on and notting happens 
  i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


  
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
  14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
  14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
  14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@Laurentiu:/home/laufer# apt-cache policy bluez
  bluez:
Installed: 5.46-0ubuntu3
Candidate: 5.46-0ubuntu3
Version table:
   *** 5.46-0ubuntu3 500
  500 http://ro.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  root@Laurentiu:/home/laufer#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  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
  Date: Mon Feb  5 15:00:42 2018
  InstallationDate: Installed on 2018-02-04 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=87b1ca1a-1586-47e4-83a2-c81e7e67ca79 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  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.:bvrX541UVK.304:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 64:6E:69:20:D4:7E  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1225 acl:0 sco:0 events:122 errors:0
TX bytes:23230 acl:0 sco:0 commands:124 errors:0

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

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


[Kernel-packages] [Bug 1747492] [NEW] [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering

2018-02-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After installing 17.10.1, plugging in the 15m DisplayPort cable, it
works, however, there is an unusable amount of screen tearing and
flickering, and pixelated lines across the screen

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


** Tags: gnome-17.10
-- 
[GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering
https://bugs.launchpad.net/bugs/1747492
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1747488] [NEW] [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

2018-02-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ubuntu 17.10.1 boots into a black screen with no display, when switching
into "EFI VGA" during boot up.

Modifying the boot menu to run in "text" mode, shows the last line as
below, before losing all monitor output:

"Switching to EFI VGA"

The 15m DisplayPort cable shouldn't be a problem, but using a
DisplayPort-to-DVI adapter and a 1m DVI cable works

PC Specs

CPU : Intel Core i9-7900X 4.3GHz 10-Core
MBO : ASRock X299 Taichi
RAM : Corsair Vengeance 32GB
GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3

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

-- 
[GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI 
VGA"
https://bugs.launchpad.net/bugs/1747488
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

2018-02-05 Thread Daniel van Vugt
In case it's not clear to all readers yet; Xwayland and gnome-shell are
co-dependent processes. If one crashes then the other will also crash.
So we need apport to be capable of handling both crashes simultaneously.

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: linux (Ubuntu)

** No longer affects: mutter (Ubuntu)

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1725416] Re: Elantech touch pad device not detected/working properly

2018-02-05 Thread Daniel van Vugt
OK, then that's either a kernel bug or libinput.

The kernel discussion will happen here. But in case it's a libinput bug then 
please also report the problem here:
  https://bugs.freedesktop.org/enter_bug.cgi?product=wayland=libinput

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

Title:
  Elantech touch pad device not detected/working properly

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some
  quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked
  flawlessly - especially the "natural scrolling" mode was working well.
  As I saw under Ubuntu Gnome 17.04, the corresponding setting in gnome-
  control-center "Natural scrolling" just targets the mouse and has no
  effect on the touchpad.

  I can see the touchpad using "xinput list":
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=14   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech Performance MX id=12   [slave  pointer 
 (2)]

  alongside my Logitech mouse on a Unifying receiver.

  Is there any chance that this touchpad is detected? Or should I forget about 
that (WONTFIX) as Xorg is already unsupported?
  ATM I am using the prop. nvidia drivers. Currently uninstalling them to see 
if Wayland is starting using nouveau...
  Thanks.
  What else do you need from me?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 20:20:04 2017
  InstallationDate: Installed on 2016-11-27 (327 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)

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

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


[Kernel-packages] [Bug 1725416] Re: Elantech touch pad device not detected/working properly

2018-02-05 Thread Daniel van Vugt
Please also try other kernel versions and tell us if some older or newer kernel 
fixes the problem for you:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

Title:
  Elantech touch pad device not detected/working properly

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some
  quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked
  flawlessly - especially the "natural scrolling" mode was working well.
  As I saw under Ubuntu Gnome 17.04, the corresponding setting in gnome-
  control-center "Natural scrolling" just targets the mouse and has no
  effect on the touchpad.

  I can see the touchpad using "xinput list":
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=14   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech Performance MX id=12   [slave  pointer 
 (2)]

  alongside my Logitech mouse on a Unifying receiver.

  Is there any chance that this touchpad is detected? Or should I forget about 
that (WONTFIX) as Xorg is already unsupported?
  ATM I am using the prop. nvidia drivers. Currently uninstalling them to see 
if Wayland is starting using nouveau...
  Thanks.
  What else do you need from me?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 20:20:04 2017
  InstallationDate: Installed on 2016-11-27 (327 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)

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

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


[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-02-05 Thread TJ
** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=198665
   Importance: Unknown
   Status: Unknown

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-05 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
7de295e2a47849488acec80fc7c9973a4dca204e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746806

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage

2018-02-05 Thread Iiridayn
** Also affects: linux (Arch Linux)
   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/159356

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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


[Kernel-packages] [Bug 1747507] Re: starting VMs causing retpoline4 to reboot

2018-02-05 Thread Bryan Quigley
Might be related, might not.  This is displayed before the reboot.

host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]

I did downgrade from the testing qemu packages, maybe that changed my
VMs, but that still shouldn't cause a host reboot (or kvm with no
options).

** Attachment added: "Warning.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747507/+attachment/5049442/+files/Warning.png

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

Title:
  starting VMs causing retpoline4 to reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.

  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.

  Steps to reproduce (has occurred both times I tried it):
  1.  Just run kvm with no options (or virsh start <> or start VM from GUI)
  Machine reboots

  Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64
  command works fine unless you use the enable kvm command.

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

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


[Kernel-packages] [Bug 1257547] Re: [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8

2018-02-05 Thread Christopher M. Penalver
Stefan Bethge, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Henrik Rydberg, and Dmitry Torokhov CC linux-input)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  [bcm5974] Apple touchpad fails to respond, dmesg contains multiple
  mesages of form: bcm5974: bad trackpad package, length: 8

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Have Apple Macbook pro 8,1. With Trusty devel, occasionally (i.e. twice in 
the last 3 weeks) my trackpad completely stopped functioning. From then on, 
dmesg is full of these messages:
  bcm5974: bad trackpad package, length: 8

  WORKAROUND: Remove and re-load bcm5974.

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

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


[Kernel-packages] [Bug 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M

2018-02-05 Thread Christopher M. Penalver
Hans Matros, to see if this is resolved upstream, could you use the
latest kernel 4.15.1 without the WORKAROUND?

If it has boot issues, please provide details via
https://wiki.ubuntu.com/DebuggingKernelBoot .

Also, when providing dmesg, please don't grep/cut/snip logs. Post them
in full.

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

Title:
  Black screen with iMac 2011 and ATI Radeon 6970M

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu 16.04 through 17.10, when I boot the screen is black,
  ping and ssh to the host does not work, and the fan is running. Same
  problem with kernel 4.14 and 4.15RC7.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1756 F pulseaudio
   /dev/snd/controlC1:  christian   1756 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/storage-swap
  InstallationDate: Installed on 2018-01-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  MachineType: Apple Inc. iMac12,2
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=/dev/mapper/storage-root ro rootflags=subvol=@ nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  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.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.004D.B00.1708080012
  dmi.board.name: Mac-942B59F58194171B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac12,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B59F58194171B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,2
  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/1743427/+subscriptions

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


[Kernel-packages] [Bug 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M

2018-02-05 Thread Christopher M. Penalver
** Description changed:

- Dear community!
+ Using Ubuntu 16.04 through 17.10, when I boot the screen is black, ping
+ and ssh to the host does not work, and the fan is running. Same problem
+ with kernel 4.14 and 4.15RC7.
  
- I have installed Ubuntu 17.10 (also tried 17.04 and 16.04), and the
- system gets a black screen on boot with all tested Ubuntu versions. Also
- ping and ssh to the host does not work. The fan's are running, the
- screen is black and nothing more.
+ WORKAROUND: Use kernel parameter:
+ nomodeset
  
- When i insert in Grub nomodeset, the system can boot.
- 
- I have also tested Kernel 4.14 and 4.15RC7.
- 
- Hardware Information:
- 
- 00:02.0 Display controller: Intel Corporation 2nd Generation Core
- Processor Family Integrated Graphics Controller (rev 09)
- 
- 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
- [AMD/ATI] Blackcomb [Radeon HD 6970M/6990M]
- 
- 
- Thanks for help or any hint.
- 
- Best regards,
- 
- Hans
- --- 
+ ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  christian   1756 F pulseaudio
-  /dev/snd/controlC1:  christian   1756 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  christian   1756 F pulseaudio
+  /dev/snd/controlC1:  christian   1756 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/storage-swap
  InstallationDate: Installed on 2018-01-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  MachineType: Apple Inc. iMac12,2
  Package: linux (not installed)
  ProcEnviron:
-  LANGUAGE=
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=/dev/mapper/storage-root ro rootflags=subvol=@ nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  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.
+  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.13.0-25-generic N/A
-  linux-backports-modules-4.13.0-25-generic  N/A
-  linux-firmware 1.169.1
+  linux-restricted-modules-4.13.0-25-generic N/A
+  linux-backports-modules-4.13.0-25-generic  N/A
+  linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.004D.B00.1708080012
  dmi.board.name: Mac-942B59F58194171B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac12,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B59F58194171B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

** Tags added: kernel-bug-exists-upstream-4.15-rc7 xenial zesty

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

Title:
  Black screen with iMac 2011 and ATI Radeon 6970M

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu 16.04 through 17.10, when I boot the screen is black,
  ping and ssh to the host does not work, and the fan is running. Same
  problem with kernel 4.14 and 4.15RC7.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1756 F pulseaudio
   /dev/snd/controlC1:  christian   1756 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/storage-swap
  InstallationDate: Installed on 2018-01-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  MachineType: Apple Inc. iMac12,2
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=/dev/mapper/storage-root ro rootflags=subvol=@ nomodeset
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Christopher M. Penalver
Bib, the issue you are reporting is an upstream one. Could you please report 
this to them via https://bugs.freedesktop.org/enter_bug.cgi?product=DRI :
Component: DRM/Radeon

Please post a link to the upstream report here so that it may be
tracked.

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

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


Re: [Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-05 Thread David JM Emmett
Given that the c5 instances are Skylake, and I read somewhere that
there’s some special edge-case for Skylake and later CPUs, is this
reproducible on proper hardware, or is it limited to KVM (prior to AWS’s
c5s, the hypervisors were xen).

I’ve got a couple of Skylake machines available, and will install sssd
and see what happens.

Cheers,
David

> On 5 Feb 2018, at 21:59, Paul Friel <1746...@bugs.launchpad.net> wrote:
> 
> @jsalisbury: I installed that kernel and rebooted using a c5.xl, it
> froze.  I booted into a c4.xl and it booted fine, disabled the apparmor
> service and rebooted into a c5.xl and it booted fine.  Re-enabled
> apparmor and rebooted into the c5.xl again and it froze on boot.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746806
> 
> Title:
>  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU
> 
> Status in cloud-images:
>  New
> Status in linux package in Ubuntu:
>  Confirmed
> Status in linux-aws package in Ubuntu:
>  Confirmed
> Status in sssd package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
>  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
>  EC2 instances after starting the service and CPU goes to 100%.
> 
>  We do not experience this issue with t2 or c4 instance types and we do
>  not see this issue on any instance types using Ubuntu Cloud images
>  from 20180109 or before. I have verified that this is kernel related
>  as I booted an image that we created using the Ubuntu cloud image from
>  20180109 which works fine on a c5. I then did a "apt update && apt
>  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
>  the server, verified I was on the new kernel and started sssd with
>  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
>  usage for that instance went to 100%.
> 
>  I haven't been able to find much in the syslog, kern.log, journalctl
>  logs, etc. The only thing I have been able to find is that when this
>  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
>  the syslog and sssd log files.  I have attached several log files and
>  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
>  anything else to help track this down.
> 
>  Thanks,
>  Paul
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 1257547] Re: [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8

2018-02-05 Thread Stefan Bethge
The issue is still happening with upstream kernel, tags added.

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

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

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

Title:
  [bcm5974] Apple touchpad fails to respond, dmesg contains multiple
  mesages of form: bcm5974: bad trackpad package, length: 8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Have Apple Macbook pro 8,1. With Trusty devel, occasionally (i.e. twice in 
the last 3 weeks) my trackpad completely stopped functioning. From then on, 
dmesg is full of these messages:
  bcm5974: bad trackpad package, length: 8

  WORKAROUND: Remove and re-load bcm5974.

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

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


[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Christopher M. Penalver
** Tags removed: kernel-bug-exists-upstream-4.15
** Tags added: kernel-bug-exists-upstream-4.15.1

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1747507] Re: starting VMs causing retpoline4 to reboot

2018-02-05 Thread Bryan Quigley
** Description changed:

  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
  
  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.
  
  Steps to reproduce (has occurred both times I tried it):
- 1. Run virsh start  (or start VM from GUI)
- Machine reboots 
+ 1.  Just run kvm with no options (or virsh start <> or start VM from GUI)
+ Machine reboots
  
- Going back to 4.13.0-32 has virsh working again
+ Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64
+ command works fine.

** Description changed:

  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
  
  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.
  
  Steps to reproduce (has occurred both times I tried it):
  1.  Just run kvm with no options (or virsh start <> or start VM from GUI)
  Machine reboots
  
  Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64
- command works fine.
+ command works fine unless you use the enable kvm command.

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

Title:
  starting VMs causing retpoline4 to reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.

  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.

  Steps to reproduce (has occurred both times I tried it):
  1.  Just run kvm with no options (or virsh start <> or start VM from GUI)
  Machine reboots

  Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64
  command works fine unless you use the enable kvm command.

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

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


[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-05 Thread Dan Streetman
Here is another Artful debug kernel, with just slightly more debug info; it may 
help a little while I work on adding more significant debug to track where the 
dst refcnt is getting leaked.  Same PPA:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1711407

New kernel version is 4.13.0-32.35+hf1711407v20180205b1.

Thanks again for testing these debug kernels!

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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


[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-05 Thread Paul Friel
@jsalisbury: I installed that kernel and rebooted using a c5.xl, it
froze.  I booted into a c4.xl and it booted fine, disabled the apparmor
service and rebooted into a c5.xl and it booted fine.  Re-enabled
apparmor and rebooted into the c5.xl again and it froze on boot.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 1747523] [NEW] support thunderx2 vendor pmu events

2018-02-05 Thread dann frazier
Public bug reported:

[Impact]
ThunderX2 vendor pmu events are not supported.

[Test Case]
Successful output:
$ sudo perf list | grep thunderx2
thunderx2 imp def:
$

[Regression Risk]
TBD

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  support thunderx2 vendor pmu events

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  ThunderX2 vendor pmu events are not supported.

  [Test Case]
  Successful output:
  $ sudo perf list | grep thunderx2
  thunderx2 imp def:
  $

  [Regression Risk]
  TBD

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

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


[Kernel-packages] [Bug 1498664] Re: Unity control center cannot detect Wacom CTH-661 tablet

2018-02-05 Thread Phsyron
How is basic device support "low" priority? how is the official work-
around to revert to a 3-year-old kernel version? either you want to
support wacom tablets, at which point this is *high* priority, or you
don't, at which point having "Wacom Tablet" as a first-level option
under system settings is probably not a great idea, considering it has
*literaly* no functionality.

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

Title:
  Unity control center cannot detect Wacom CTH-661 tablet

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the .3 release of Ubuntu 14.04 LTS unity control center can't
  see the Wacom Bamboo Fun tablet (CTH-661). The tablet works, both
  xsetwacom and lsusb detects it and allows to change settings.

  This problem occurs only in this release , tablet worked perfectly in
  14.04.2 and 15.04. My guess is it may be also connected to unity-
  settings-daemon, but its only a guess because i have no idea of how to
  check this.

  release/package info:
  Ubuntu 14.04.3 LTS

  unity-control-center:
   14.04.3+14.04.20140922-0ubuntu1.1

  unity-settings-daemon:
14.04.0+14.04.20150825-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-29.31~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 22 23:26:21 2015
  InstallationDate: Installed on 2015-09-20 (2 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

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

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


[Kernel-packages] [Bug 1746900] Re: linux: 3.13.0-142.191 -proposed tracker

2018-02-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746901
  derivatives:
- kernel-stable-phase-changed:Friday, 02. February 2018 14:33 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Monday, 05. February 2018 21:01 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

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

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

Title:
  linux: 3.13.0-142.191 -proposed tracker

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

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

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

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

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

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


[Kernel-packages] [Bug 1736145] Re: Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition table

2018-02-05 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089997.html

** Description changed:

+ == SRU Justification ==
+ Kexec can leave MMU registers set, PIDR in particular, when booting the
+ new kernel. The boot sequence does not zero PIDR ever, and it only gets
+ changed as CPUs first switch to userspace processes. This can leave a
+ window where speculative accesses from a CPU to quadrant 0 can pick up
+ translations in the partition table that may be set up for processes
+ running on other CPUs. These cached translations will not be involved in
+ the invalidation protocol, so we can end with stable TLB and PWC.
+ 
+ This commit was included in mailine as of v4.15-rc5 and fixes commit
+ 7e381c0ff618.
+ 
+ == Fix ==
+ commit 371b80447ff33ddac392c189cf884a5a3e18faeb
+ Author: Nicholas Piggin 
+ Date:   Wed Dec 6 18:21:14 2017 +1000
+ 
+ powerpc/64s: Initialize ISAv3 MMU registers before setting partition
+ table
+ 
+ == Regression Potential ==
+ Low. This fix is specific to powerpc.  It has also been cc'd to upstream 
stable, 
+ so it has had additional upstream review.
+ 
+ 
+ ==Original Bug Description: ==
  == Comment: #0 - Breno Leitao  - 2017-12-04 05:50:27 ==
  kexec can leave MMU registers set, PIDR in particular, when booting the
  new kernel. The boot sequence does not zero PIDR ever, and it only gets
  changed as CPUs first switch to userspace processes. This can leave a
  window where speculative accesses from a CPU to quadrant 0 can pick up
  translations in the partition table that may be set up for processes
  running on other CPUs. These cached translations will not be involved in
  the invalidation protocol, so we can end with stable TLB and PWC.
  
- 
  We need to have this patch included in Ubuntu kernel.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html
  
  We do not have commit id, but once we have, I will post here. There is
  no need to include the patch prior to upstream acceptance.
  
  == Comment: #2 - VIPIN K. PARASHAR  - 2017-12-04 
06:57:52 ==
  (In reply to comment #0)
- > 
+ >
  > We need to have this patch included in Ubuntu kernel.
  > https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html
- > 
+ >
  > We do not have commit id, but once we have, I will post here. There is no
  > need to include the patch prior to upstream acceptance.
  >
  
  .. Patch subject reads as follows:
  
  [PATCH] powerpc/64s: ISAv3 initialize MMU registers before setting
  partition table

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

Title:
  Ubuntu16.04.03: ISAv3 initialize MMU registers before setting
  partition table

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

Bug description:
  == SRU Justification ==
  Kexec can leave MMU registers set, PIDR in particular, when booting the
  new kernel. The boot sequence does not zero PIDR ever, and it only gets
  changed as CPUs first switch to userspace processes. This can leave a
  window where speculative accesses from a CPU to quadrant 0 can pick up
  translations in the partition table that may be set up for processes
  running on other CPUs. These cached translations will not be involved in
  the invalidation protocol, so we can end with stable TLB and PWC.

  This commit was included in mailine as of v4.15-rc5 and fixes commit
  7e381c0ff618.

  == Fix ==
  commit 371b80447ff33ddac392c189cf884a5a3e18faeb
  Author: Nicholas Piggin 
  Date:   Wed Dec 6 18:21:14 2017 +1000

  powerpc/64s: Initialize ISAv3 MMU registers before setting
  partition table

  == Regression Potential ==
  Low. This fix is specific to powerpc.  It has also been cc'd to upstream 
stable, 
  so it has had additional upstream review.


  ==Original Bug Description: ==
  == Comment: #0 - Breno Leitao  - 2017-12-04 05:50:27 ==
  kexec can leave MMU registers set, PIDR in particular, when booting the
  new kernel. The boot sequence does not zero PIDR ever, and it only gets
  changed as CPUs first switch to userspace processes. This can leave a
  window where speculative accesses from a CPU to quadrant 0 can pick up
  translations in the partition table that may be set up for processes
  running on other CPUs. These cached translations will not be involved in
  the invalidation protocol, so we can end with stable TLB and PWC.

  We need to have this patch included in Ubuntu kernel.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html

  We do not have commit id, but once we have, I will post here. There is
  no need to include the patch prior to upstream acceptance.

  == Comment: #2 - 

[Kernel-packages] [Bug 1735159] Re: powerpc/powernv: Flush console before platform error reboot

2018-02-05 Thread Joseph Salisbury
SRU request submitted for Artful:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089995.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/1735159

Title:
  powerpc/powernv: Flush console before platform error reboot

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  == SRU Justification ==
  IBM unrecovered MCE and HMI errors are sent through a special restart OPAL
  call to log the platform error. The downside is that they don't go
  through normal Linux crash paths, so they don't give much information
  to the Linux console.

  IBM is requesting to have the commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514
  in the Zesty kernel.

  Commit b746e3e01e70d2 is in mainline as of 4.14-rc1.

  Breno Leitao from IBM did a backport of this commit.

  == Fix ==
  commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514
  Author: Nicholas Piggin 
  Date:   Wed Jul 19 16:59:10 2017 +1000

  powerpc/powernv: Flush console before platform error reboot

  == Regression Potential ==
  This patch is specific to powerpc, and it has been backported, reviewed and 
  tested by IBM.

  == 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.

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

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


[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2018-02-05 Thread Lucas Zanella
I searched and found nothing.

So, even with APST disabled my ssd will fail on linux. What should I do?
Does it work normally for other people when they disable it?

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2018-02-05 Thread Thorsten Munsch
I noticed weird network problems on this system aswell, when plugging in
a USB3 external harddisk and on Friday even when I just plugged in my
mobile phone just to load the battery.

Don't know if this is connected in some way. Yesterday I updated the
UEFI/BIOS and will watch if this is still happening.

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2018-02-05 Thread Thorsten Munsch
Still present in (X)ubuntu 17.10 with kernel 4.13.0-32-generic.

The trigger is the onboard Realtek network chip on my Gigabyte GA-AB350
Gaming 3 (AMD Ryzen) mainboard:

+-01.3-[01-05]--+-00.0  Advanced Micro Devices, Inc. [AMD] USB 3.1 XHCI 
Controller
   |   +-00.1  Advanced Micro Devices, Inc. [AMD] Device 
43b7
   |   \-00.2-[02-05]--+-00.0-[03]00.0  Realtek 
Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   |   +-01.0-[04]--
   |   \-04.0-[05]--

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1747507] [NEW] starting VMs causing retpoline4 to reboot

2018-02-05 Thread Bryan Quigley
Public bug reported:

Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.

CPU: AMD Ryzen 7 1700 Eight-Core Processor
Ubuntu: 17.10.

Steps to reproduce (has occurred both times I tried it):
1. Run virsh start  (or start VM from GUI)
Machine reboots 

Going back to 4.13.0-32 has virsh working again

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

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

Title:
  starting VMs causing retpoline4 to reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.

  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.

  Steps to reproduce (has occurred both times I tried it):
  1. Run virsh start  (or start VM from GUI)
  Machine reboots 

  Going back to 4.13.0-32 has virsh working again

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

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


[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Bib
The (bad) Artist, v4.15.1. This is awful, how can you get info from this. I set 
resolution to highest possible and enabled auto-stabilization.
Don't we have in linux something like the /debug option of windows NT boot.ini 
that allows to dump boot to a serial port ?

** Attachment added: "20180205_194814.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746357/+attachment/5049377/+files/20180205_194814.mp4

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-05 Thread Bib
Another shoot. Should I remove the 2 previous ones?

** Attachment added: "20180205_200552.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746357/+attachment/5049378/+files/20180205_200552.mp4

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1722677] Re: Touch Screen NOT working

2018-02-05 Thread redx
hi, i have tested it with ubuntu 17.10 and kernel 15.1 but the
touchscreen continue to not work.

System: Host: NULL Kernel: 4.15.1-041501-generic x86_64 bits: 64

   Desktop: Gnome 3.26.2 Distro: Ubuntu 17.10

Machine: Device: portable System: Dell product: Venue 11 Pro 7139 v: 00
serial: N/A

   Mobo: Dell model: 0RFDKW v: A00 serial: N/A

   UEFI: Dell v: A21 date: 12/22/2016

Battery BAT0: charge: 35.2 Wh 162.5% condition: 21.7/35.2 Wh (62%)

   BAT1: charge: 26.2 Wh 132.4% condition: 19.8/26.2 Wh (76%)

CPU: Dual core Intel Core i5-4300Y (-HT-MCP-) cache: 3072 KB

   clock speeds: max: 2300 MHz 1: 847 MHz 2: 1153 MHz 3: 1180
MHz

   4: 1164 MHz

Graphics: Card: Intel Device 0a1e

   Display Server: wayland (X.Org 1.19.5 ) driver: i915

   Resolution: 1920x1080@59.96hz

   OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa
17.2.4

Audio: Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel

   Card-2 Intel Haswell-ULT HD Audio Controller driver:
snd_hda_intel

   Sound: Advanced Linux Sound Architecture v:
k4.15.1-041501-generic

Network: Card: Intel Wireless 7260 driver: iwlwifi

   IF: wlp1s0 state: up

Drives: HDD Total Size: 255.8GB (2.9% used)

Partition: ID-1: / size: 233G used: 7.0G (4%) fs: ext4 dev: /dev/sda2

RAID: No RAID devices: /proc/mdstat, md_mod kernel module present

Sensors: System Temperatures: cpu: 45.0C mobo: N/A

   Fan Speeds (in rpm): cpu: N/A

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

Title:
  Touch Screen NOT working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. 
  Touchscreen does not work after installing OS from live USB. It did not work 
on USB either. There is zero touchscreen functionality.

  Workaroud: Must put computer to sleep, and then wake from sleep for
  touchscreen to work.

  Please Note: In this edition of 17.10, tilt sensors work perfectly
  without having to put the computer to sleep (an old bug). Also note,
  wifi works perfectly after resuming from sleep (another old bug fixed
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  troll  1255 F pulseaudio
   /dev/snd/controlC0:  troll  1255 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 18:54:29 2017
  InstallationDate: Installed on 2017-09-30 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Venue 11 Pro 7139
  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-15-generic.efi.signed 
root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0RFDKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-05 Thread Joseph Salisbury
I started a kernel bisect between Ubuntu-4.4.0-109 and Ubuntu-4.4.0-110. The 
kernel bisect will require testing of about 5 test kernels.

I built the first test kernel, up to the following commit:
d3d0f0a209ee29cf553b8b5580eb954b0d4aa970

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746806

Can you test that kernel and report back if it has the bug or not?  I
will build the next test kernel based on your test results.

To test this kernel, 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/1746806

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 1722677] Re: Touch Screen NOT working

2018-02-05 Thread redx
hi, i have tested it with ubuntu 17.10 and kernel 15.1 but the
touchscreen continue to not work.


System:Host: NULL Kernel: 4.15.1-041501-generic x86_64 bits: 64

   Desktop: Gnome 3.26.2 Distro: Ubuntu 17.10

Machine:   Device: portable System: Dell product: Venue 11 Pro 7139 v:
00 serial: N/A

   Mobo: Dell model: 0RFDKW v: A00 serial: N/A

   UEFI: Dell v: A21 date: 12/22/2016

BatteryBAT0: charge: 35.2 Wh 162.5% condition: 21.7/35.2 Wh (62%)

   BAT1: charge: 26.2 Wh 132.4% condition: 19.8/26.2 Wh (76%)

CPU:   Dual core Intel Core i5-4300Y (-HT-MCP-) cache: 3072 KB

   clock speeds: max: 2300 MHz 1: 847 MHz 2: 1153 MHz 3: 1180
MHz

   4: 1164 MHz

Graphics:  Card: Intel Device 0a1e

   Display Server: wayland (X.Org 1.19.5 ) driver: i915

   Resolution: 1920x1080@59.96hz

   OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa
17.2.4

Audio: Card-1 Intel 8 Series HD Audio Controller driver:
snd_hda_intel

   Card-2 Intel Haswell-ULT HD Audio Controller driver:
snd_hda_intel

   Sound: Advanced Linux Sound Architecture v:
k4.15.1-041501-generic

Network:   Card: Intel Wireless 7260 driver: iwlwifi

   IF: wlp1s0 state: up mac: 7c:7a:91:eb:64:5a

Drives:HDD Total Size: 255.8GB (2.9% used)


Partition: ID-1: / size: 233G used: 7.0G (4%) fs: ext4 dev: /dev/sda2

RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present

Sensors:   System Temperatures: cpu: 45.0C mobo: N/A

   Fan Speeds (in rpm): cpu: N/A

Info:  Processes: 233 Uptime: 16 min Memory: 909.1/7882.0MB

   Client: Shell (bash) inxi: 2.3.37


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

Title:
  Touch Screen NOT working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. 
  Touchscreen does not work after installing OS from live USB. It did not work 
on USB either. There is zero touchscreen functionality.

  Workaroud: Must put computer to sleep, and then wake from sleep for
  touchscreen to work.

  Please Note: In this edition of 17.10, tilt sensors work perfectly
  without having to put the computer to sleep (an old bug). Also note,
  wifi works perfectly after resuming from sleep (another old bug fixed
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  troll  1255 F pulseaudio
   /dev/snd/controlC0:  troll  1255 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 18:54:29 2017
  InstallationDate: Installed on 2017-09-30 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Venue 11 Pro 7139
  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-15-generic.efi.signed 
root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0RFDKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-05 Thread Joseph Salisbury
** Tags added: pti

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 1746901] Re: linux-lts-trusty: 3.13.0-142.191~precise1 -proposed tracker

2018-02-05 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-lts-trusty: 3.13.0-142.191~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746900
  phase: Uploaded

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

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


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

2018-02-05 Thread Michael Hoff
apport information

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

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

[Kernel-packages] [Bug 1747273] RfKill.txt

2018-02-05 Thread Michael Hoff
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1747273/+attachment/5049330/+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/1747273

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1747273/+attachment/5049331/+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/1747273

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

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

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  

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

2018-02-05 Thread Michael Hoff
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1747273/+attachment/5049324/+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/1747273

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1747273/+attachment/5049327/+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/1747273

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

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

2018-02-05 Thread Michael Hoff
apport information

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

[Kernel-packages] [Bug 1747273] IwConfig.txt

2018-02-05 Thread Michael Hoff
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1747273/+attachment/5049320/+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/1747273

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  

[Kernel-packages] [Bug 1747273] Re: Can not control brightness on Thinkpad P51

2018-02-05 Thread Michael Hoff
apport information

** Tags added: apport-collected

** Description changed:

  I can not modify the screen brightness in Ubuntu 17.10. Controls aside,
  the classes in `proc` are either not available or non-functional
  depending on what arguments I provide in GRUB_CMDLINE_LINUX_DEFAULT.
  
  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.
  
  System Information
  --
  
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  
  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/type:platform
  /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/bl_power:0
  

[Kernel-packages] [Bug 1746551] Re: GPU HANG since package update

2018-02-05 Thread P
Bug also reported here:
https://bugs.freedesktop.org/show_bug.cgi?id=104953


** Bug watch added: freedesktop.org Bugzilla #104953
   https://bugs.freedesktop.org/show_bug.cgi?id=104953

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

Title:
  GPU HANG since package update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since today, I get occasional crashes freeze-ups of the GUI, followed
  by a restart of the X server. In syslog, I find entries like the ones
  below.

  The system was running stably before, so this is a new phenomenon...
  could this be related to the recent kernel updates?

  Obviously, this leads to data loss...

  Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 
9:0:0x86dd, in Xorg [870], reason: Hang on rcs0, action: reset
  Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
  Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
  Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
  Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on


  Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on


  Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on


  Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on


  Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected  


  Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke 
(error 1). Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 
1). Did the X11 server die?
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]:   after 2218 requests 
(2218 known processed) with 0 events remaining.
  Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process 
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
  Jan 31 11:23:21 TP systemd[1]: Stopping User Manager for UID 1000...
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Default.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Basic System.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Paths.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Sockets.

  

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-02-05 Thread varacanero
I also checked that my Laptop doesn't respond to ssh connects which
worked before.

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-02-05 Thread varacanero
Same for 4.13.0-32-generic on Ubuntu 17.10.

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1746551] Re: GPU HANG since package update

2018-02-05 Thread P
The problem occurs with the new mainline kernel (4.15.0-041500-generic
#201802011154 SMP Thu Feb 1 11:55:45 UTC 2018 x86_64 x86_64 x86_64
GNU/Linux). Here are the related dmesg lines:

[16127.462805] [drm] GPU HANG: ecode 9:0:0x85db, in Xorg [887], reason: 
Hang on rcs0, action: reset
[16127.462806] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[16127.462807] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[16127.462807] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[16127.462807] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[16127.462808] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[16127.462813] i915 :00:02.0: Resetting rcs0 after gpu hang
[16135.453438] i915 :00:02.0: Resetting rcs0 after gpu hang
[16143.452952] i915 :00:02.0: Resetting rcs0 after gpu hang
[16157.468290] i915 :00:02.0: Resetting rcs0 after gpu hang
[16171.451587] i915 :00:02.0: Resetting rcs0 after gpu hang
[

** Attachment added: "GPU crash dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746551/+attachment/5049295/+files/drm_card0_error

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

Title:
  GPU HANG since package update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since today, I get occasional crashes freeze-ups of the GUI, followed
  by a restart of the X server. In syslog, I find entries like the ones
  below.

  The system was running stably before, so this is a new phenomenon...
  could this be related to the recent kernel updates?

  Obviously, this leads to data loss...

  Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 
9:0:0x86dd, in Xorg [870], reason: Hang on rcs0, action: reset
  Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
  Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
  Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
  Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on


  Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on


  Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on


  Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on


  Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected  


  Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
  Jan 31 11:23:20 TP 

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

2018-02-05 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Status: Confirmed => Triaged

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

** Tags added: rls-bb-incoming

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working

2018-02-05 Thread TauSo
Thanks for your work, but the bug is still triggered - new codeline at
least ;-)

[5.405637] [ cut here ]
[5.405643] kernel BUG at 
/home/khfeng/Sources/linux-lp1742316-saa7146/drivers/media/common/saa7146/saa7146_core.c:164!
[5.405671] invalid opcode:  [#1] SMP
[5.405677] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek 
budget_av(+) snd_hda_codec_generic saa7146_vv snd_hda_intel budget_core 
ttpci_eeprom snd_hda_codec snd_hda_core saa7146 videobuf_dma_sg videobuf_core 
dvb_core snd_hwdep v4l2_common intel_powerclamp snd_pcm videodev snd_timer 
media joydev snd input_leds lpc_ich soundcore shpchp mac_hid nct6775 hwmon_vid 
coretemp ip_tables x_tables autofs4 hid_generic gma500_gfx usbhid hid 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci r8169 
fb_sys_fops libahci drm mii video
[5.405763] CPU: 0 PID: 288 Comm: systemd-udevd Not tainted 
4.14.0-17-generic #20
[5.405769] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./AD2700-ITX, BIOS P1.60 04/19/2013
[5.405776] task: f11b30c0 task.stack: f48c8000
[5.405789] EIP: saa7146_vmalloc_build_pgtable+0x190/0x1020 [saa7146]
[5.405794] EFLAGS: 00010246 CPU: 0
[5.405800] EAX: f22dd620 EBX: f8272000 ECX: 0002 EDX: fff1c000
[5.405806] ESI:  EDI: f84a4000 EBP: f48c9c44 ESP: f48c9c20
[5.405811]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[5.405817] CR0: 80050033 CR2: 017c7cf4 CR3: 313aa640 CR4: 06f0
[5.405822] Call Trace:
[5.405838]  ttpci_budget_init+0x26c/0x530 [budget_core]
[5.405851]  ? budget_av_attach+0x3e/0x4e8 [budget_av]
[5.405864]  budget_av_attach+0x75/0x4e8 [budget_av]
[5.405878]  ? vprintk_func+0x29/0x70
[5.405886]  ? printk+0x13/0x15
[5.405895]  ? saa7146_init_one+0x69f/0x770 [saa7146]
[5.405906]  saa7146_init_one+0x70b/0x770 [saa7146]
[5.405919]  ? __pm_runtime_resume+0x51/0x80
[5.405929]  pci_device_probe+0xc2/0x160
[5.405940]  driver_probe_device+0x2b9/0x410
[5.405949]  __driver_attach+0x99/0xe0
[5.405958]  ? driver_probe_device+0x410/0x410
[5.405966]  bus_for_each_dev+0x57/0x90
[5.405975]  driver_attach+0x19/0x20
[5.405982]  ? driver_probe_device+0x410/0x410
[5.405990]  bus_add_driver+0x187/0x230
[5.405997]  ? 0xf8727000
[5.406004]  driver_register+0x56/0xd0
[5.406011]  ? 0xf8727000
[5.406018]  __pci_register_driver+0x3a/0x40
[5.406029]  saa7146_register_extension+0x50/0x80 [saa7146]
[5.406043]  budget_av_init+0xd/0x1000 [budget_av]
[5.406053]  do_one_initcall+0x46/0x180
[5.406063]  ? kfree+0x155/0x170
[5.406071]  ? kfree+0x155/0x170
[5.406078]  ? kmem_cache_alloc_trace+0x165/0x1d0
[5.406086]  ? do_init_module+0x21/0x1cc
[5.406093]  ? do_init_module+0x21/0x1cc
[5.406102]  do_init_module+0x50/0x1cc
[5.406110]  load_module+0x1565/0x1a80
[5.406124]  SyS_finit_module+0x8a/0xe0
[5.406135]  do_fast_syscall_32+0x71/0x1d0
[5.406145]  entry_SYSENTER_32+0x4e/0x7c
[5.406151] EIP: 0xb7f3ecf9
[5.406156] EFLAGS: 0296 CPU: 0
[5.406162] EAX: ffda EBX: 0018 ECX: b7d2fa71 EDX: 
[5.406167] ESI: 017bc9d0 EDI: 017b9310 EBP:  ESP: bf9ab29c
[5.406173]  DS: 007b ES: 007b FS:  GS: 0033 SS: 007b
[5.406180] Code: e8 e8 b5 eb ff ff 85 c0 59 75 7c 8b 45 ec 8d 65 f4 5b 5e 
5f 5d c3 90 8d 74 26 00 83 3d f0 6d e5 c8 02 0f 85 08 ff ff ff 8d 76 00 <0f> 0b 
8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 c7 45 dc 00 00
[5.406289] EIP: saa7146_vmalloc_build_pgtable+0x190/0x1020 [saa7146] 
SS:ESP: 0068:f48c9c20
[5.406319] ---[ end trace e0fc7bfda2220079 ]---

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', 

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

2018-02-05 Thread Ubuntu Kernel Bot
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 1747273

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: artful

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  

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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1747463/+attachment/5049293/+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/1747463

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1747463/+attachment/5049290/+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/1747463

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1747463/+attachment/5049287/+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/1747463

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1747463] Re: kernel crashes unless IOMMU is disabled on Ryzen 1800X

2018-02-05 Thread Peridot
apport information

** Tags added: apport-collected bionic

** Description changed:

  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.
  
  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups with
  a normal boot. How I it to work is to disable IOMMU in the BIOS and add
  "iommu=soft" to the kernel booting options in grub.
  
  linux can then detect everything properly (all cores) and I've had zero
  crashes. The only issue is that it's using software IOMMU.
  
  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.
  
  I attached a kernel log.
  
  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
+ --- 
+ ApportVersion: 2.20.8-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  fixme  1487 F pulseaudio
+  /dev/snd/controlC0:  fixme  1487 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
+ InstallationDate: Installed on 2018-01-31 (4 days ago)
+ InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp3s0no wireless extensions.
+ MachineType: BIOSTAR Group B350GT5
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
+ 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
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 4.13.0-32-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/30/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 5.13
+ dmi.board.asset.tag: None
+ dmi.board.name: B350GT5
+ dmi.board.vendor: BIOSTAR Group
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: None
+ dmi.product.name: B350GT5
+ dmi.sys.vendor: BIOSTAR Group

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1747463/+attachment/5049281/+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/1747463

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip 

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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread Peridot
apport information

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

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


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

2018-02-05 Thread bugproxy
--- Comment From bren...@br.ibm.com 2018-02-05 12:31 EDT---
Hi Joseph,

> Hi Breno,
>
> It looks like you submitted the SRU request for Zesty.  Do you want to
> submit the request for Artful as well, or do you want me to do it?

Good catch, we need this for  Artful as well, since the commit just made
4.14, so, we need to backport to 4.13.

Would  you mind doing it, please?

Thank you,
Breno

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

Title:
  powerpc/powernv: Flush console before platform error reboot

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  == SRU Justification ==
  IBM unrecovered MCE and HMI errors are sent through a special restart OPAL
  call to log the platform error. The downside is that they don't go
  through normal Linux crash paths, so they don't give much information
  to the Linux console.

  IBM is requesting to have the commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514
  in the Zesty kernel.

  Commit b746e3e01e70d2 is in mainline as of 4.14-rc1.

  Breno Leitao from IBM did a backport of this commit.

  == Fix ==
  commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514
  Author: Nicholas Piggin 
  Date:   Wed Jul 19 16:59:10 2017 +1000

  powerpc/powernv: Flush console before platform error reboot

  == Regression Potential ==
  This patch is specific to powerpc, and it has been backported, reviewed and 
  tested by IBM.

  == 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.

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

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


[Kernel-packages] [Bug 1747463] Re: kernel crashes unless IOMMU is disabled on Ryzen 1800X

2018-02-05 Thread Peridot
** 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/1747463

Title:
  kernel crashes unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  Lots of AMD-Vi logged events and I get irq crashes or acpi hangups
  with a normal boot. How I it to work is to disable IOMMU in the BIOS
  and add "iommu=soft" to the kernel booting options in grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085

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

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


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

2018-02-05 Thread bugproxy
--- Comment From bren...@br.ibm.com 2018-02-05 12:40 EDT---
(In reply to comment #9)
> I built an Artful test kernel with commit 371b80447ff33dd.  The test kernel
> can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1736145
>
> Can you test this kernel and see if it resolves this bug?

Yes. I just installed it here and I can't see the problem:

$  uname -a
Linux 1604 4.13.0-32-generic #35~lp1736145 SMP Mon Feb 5 17:01:30 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

Thanks!

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

Title:
  Ubuntu16.04.03: ISAv3 initialize MMU registers before setting
  partition table

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-12-04 05:50:27 ==
  kexec can leave MMU registers set, PIDR in particular, when booting the
  new kernel. The boot sequence does not zero PIDR ever, and it only gets
  changed as CPUs first switch to userspace processes. This can leave a
  window where speculative accesses from a CPU to quadrant 0 can pick up
  translations in the partition table that may be set up for processes
  running on other CPUs. These cached translations will not be involved in
  the invalidation protocol, so we can end with stable TLB and PWC.

  
  We need to have this patch included in Ubuntu kernel.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html

  We do not have commit id, but once we have, I will post here. There is
  no need to include the patch prior to upstream acceptance.

  == Comment: #2 - VIPIN K. PARASHAR  - 2017-12-04 
06:57:52 ==
  (In reply to comment #0)
  > 
  > We need to have this patch included in Ubuntu kernel.
  > https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html
  > 
  > We do not have commit id, but once we have, I will post here. There is no
  > need to include the patch prior to upstream acceptance.
  >

  .. Patch subject reads as follows:

  [PATCH] powerpc/64s: ISAv3 initialize MMU registers before setting
  partition table

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

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


[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

2018-02-05 Thread Joseph Salisbury
I'm still working on bisecting the issue down.  I should have another
update in a day or two.

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  In Progress
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in openvswitch source package in Bionic:
  Confirmed

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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


[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2018-02-05 Thread Rafael David Tinoco
Yep, soon kernel team will advise (here) about this patch been released
in a specific kernel version that is in -proposed and will call out for
testing/verification. I'll give all feedback here also and will mark, if
appropriate, case as "verification-done" so new kernel is marked as
solving this issue.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  Fix Committed
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  Fix Committed
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  Fix Committed
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  Fix Committed
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in shutdown 
 state.

   * any error in logic would only appear during shutdown and
 would not cause any harm to data.

  [Other Info]
   
   * ORIGINAL BUG DESCRIPTION

  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-05 Thread Joseph Salisbury
Thanks for testing.  I'll have to review some of the other config
differences between 4.13.0-10 and 4.12.0-13.

Another thing we could test is the latest Bionic kernel to see if a
config change was already made there to resolve this.  That kernel is
available from:

https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa2/+build/14223014

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1747273] Re: Can not control brightness on Thinkpad P51

2018-02-05 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Can not control brightness on Thinkpad P51

Status in linux package in Ubuntu:
  New

Bug description:
  I can not modify the screen brightness in Ubuntu 17.10. Controls
  aside, the classes in `proc` are either not available or non-
  functional depending on what arguments I provide in
  GRUB_CMDLINE_LINUX_DEFAULT.

  On a parallel installation (Ubuntu 16.04.3), brightness control works
  flawlessly.

  System Information
  --

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#3 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V 
(rev 31)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 
Mobile] (rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961
  04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

  # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux 
thinkpad-acpi.brightness_enable=1":
  $ grep . -R /sys/class/backlight/thinkpad_screen/*
  /sys/class/backlight/thinkpad_screen/actual_brightness:0
  /sys/class/backlight/thinkpad_screen/bl_power:0
  /sys/class/backlight/thinkpad_screen/brightness:11
  /sys/class/backlight/thinkpad_screen/max_brightness:15
  /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0
  /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0
  grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: 
Input/output error
  /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0
  /sys/class/backlight/thinkpad_screen/power/control:auto
  /sys/class/backlight/thinkpad_screen/power/async:disabled
  /sys/class/backlight/thinkpad_screen/power/runtime_usage:0
  /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported
  grep: warning: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: 
recursive directory loop
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0
  grep: 
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms:
 Input/output error
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported
  
/sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/max_brightness:15
  

  1   2   >